Does it have KIOSlaves or is it too much Linux specific code?
KIOSlaves seem to be part of KIO package. Donāt think they are Linux specific, at least I see 5 of them in the package.
KDE Connect when /s
But seriously, great work to all the team porting all this stuff over.
Getting Trojita working has given me an IMAP client that isnāt horribly out of date.
If you need any specific apps that need testing, Iāll volunteer my netbook to help.
Would it be easy to port kDevelop? I havent been coding in BeOS nor haiku for over 10 years, but last time I used Pe and Makefiles, but it would be really nice to have an editor with auto completion. (There was an addon for BeIDE, but it was kind of buggy). āDont Worryā it was called, I think.
1 Like
Thereās Qt Creator already ported and in the x86_64 repo (and maybe the gcc2 hybrid repo too, but I havenāt checked). It has autocomplete, although the pop-up seems to disappear, but it is very usable - Iām coding a native Haiku project with it, using cmake.
Chris
4 Likes
IMHO the haiku debugger already covers the hardest parts of what an IDE needs to do. The rest is building a project and editing codeā¦
Hmmā¦ can the haiku debugger attach to a remote gdb session? I think I saw something about it somewhereā¦ that would be really cool.
Monkey Studio would be a possible alternative, however it does not seem to be in the repos yet. I think it should not be too hard to port.
Iām sticking with old-fashioned vim, however 
Nerd
I used VI and CC-tags on my first job, 15:ish years ago. Nowadays its Xcode all the way.
Just asking since accessing cd-rom content in dolphin as ogg files to simply copy paste around has been niceā¦ until they borked it and it stopped working.
If auto-completion would not totally fail if you need to have Obj-C wrappers for puny customersā¦
I just fixed Monkey Studio to work with the latest Qt5 and the package is already available in x86_64 repo.
9 Likes
I also just use vim, though I find it a bit lacking when it comes to debugging (I normally just use raw gdb for that). In haiku this isnāt so much of a problem, since the debugger is so good.
For debugging (outside Haiku) Iām quite happy with https://github.com/cyrus-and/gdb-dashboard . Makes gdb a lot quicker to navigate.
3 Likes
Speaking of vim, do you guys use the console or the gui version? which one is better? also iāve been trying to enable syntax coloring in haiku i coudnāt find how, i know how to do it in linux but i haiku.
Iāve added an initial recipe for KDevelop. It doesnāt build yet, but feel free to fix it. Hopefully, it shouldnāt be too hard.
Both work well.
Enabling the syntax works as usual, nothing special. The config file is in ~/config/settings/vim/vimrc. It is a good idea to start with āset nocpā because by default our vim emulates classic vi.
You can find my vimrc file and .vim directory (in Haiku install it at ~/config/settings/vim/vimfiles) at https://github.com/pulkomandy/.dotfiles . Note that this is mostly for my personal use and is not much commented. Ask if you have any questions about it. It may also not work out of the box on Haiku, depending on where I last hacked on my settings (probably at work where unfortunately I donāt run Haiku).
I donāt ever use gvim myself (meant to look into it for years but never have). But you can find my config file in an old post here. I do think it makes it a bit difficult for new users that a decent default vimrc isnāt included in the haiku package.
There are probably some things in my vimrc you donāt want (and these days I have even more stuff), and I think that the move to the new forums has mangled the spellchecking options in my post. The most important though are āset nocompatibleā and āsyntax onā.
Just a heads-up: Calligra Office suite is now available in x86_gcc2 repo.
8 Likes
Thanks guys for all the info, iāll take a look at all this once vim lands in the repos, i donāt have time to build it myself.
Thank you Diver! You are like a Santa Claus, giving us Haiku apps! 
2 Likes