When I read the developers site it seems to completely focus on developers wanting to build the Haiku kernel itself. What I am missing is the part for beginning developers that want to use Haiku as the development platform for applications, with items like
what libraries do I need to install
what do I have to type? (Someone informed me, that I needed to use setarch x86 for the newers compiler, but that would have been a item on the app developers site)
how do you configure your system, so that your compiler and tools, know where to find stuff etc.
Not all developers have the patience to dive in a system and break their teeth on quirks of an exotic operating system. They simply move on, if they dont understand the system or if it seems broken from their perspective.
Yes, we need better “getting started” documentation for developers. I’ve been meaning to work on that, but am not sure where to put it, and haven’t really had time to think about this or write it…
Writing documentation for users is boring I know
What helps are small examples that someone can copy/paste/compile and only explain the special things.
There are enough C++ tutorials on the internet, so you shouldn’t focus on that.
When I was 6 I learned to program by rewriting functioning programs until they didnt work anymore. Then Wirth came along, Kerningham and Ritchie and than Stroustrup. Their legacy can be found all over the net.
An interesting thing will be: does Haiku continue with the native widget set, does it go for Gtk or will it gravitate towards Qt? These toolkits have their own way of handling events.
yes exactly, the time I was trying to learn C++ was very confusing with Haiku…
It was much easier in the BeOs days… BEIDE was just working.
When you just not develop (you just try it only) in c++ why you asking for a better ide?
If you have c++ knowledge, use it to make this ide for haiku by your self, because some one who have enough expierience can do that only.
(so much people only asking… why not working on it? I have done 3 ides for development languages for haiku and i wish to make some for c++, but my knwledge on it is too low.)
Creating an IDE that’s actually useful is quite a big project. There have been several attempts in the past - waddlesplash’s Heidi, KapiX’ Koder, Duggan’s CodePal - but none have progressed over the minimal features of Paladin so far, I think.
Currently, it’s just about as easy to use Pe as editor, an open Tracker window with your project folder (and Tracker with activated type-ahead-filtering), a Terminal and use the makefile from the makefile_engine.
Ooooh, I did not know that. Does it work with jam?
I use the Sisong IDE for some of my projects. It is available on Clasqm’s repo. It has build scripts so you can make, make catkeys, run other scripts, launch the built app and whatever you want all with one key command. Otherwise I just use Pe to edit and the terminal to build like Humdinger says. I find using the makefile engine easier for my own third party apps and there are lots of examples out there of make files for you to figure out what libraries to include, etc.
Sure, works with anything that ouputs a path (with a colon-separated line number ).
Any path or URL opens like this when ALT-clicking it, parts of it when holding SHIFT as well, see Userguide’s Terminal topic.