After some investigation, reading the HowTos and experimenting I managed to create a somewhat usable Haiku development environment. However, there are still things unanswered, resulting from the fact that I come from the big VisualStudio-spoiled Windows-Island. (These questions fit probably any other Unix-based system I think.) 1. How do I setup my partitions to be able to conveniently experiment with code and build my nightlies to be up to date (It's inconventient to burn CDs and install.). 2. Which applications do the experienced developers use for coding? PE, VIM, etc.? 3. Why are those apps used? 4. How can I debug my code? The first question was answered by Stippi(some days ago) suggesting three partitions. Well, what I did was to create three partitions and to install on two of them the second Alpha of Haiku (One "Nightly" and one "Daily" :) ). I was then able to compile the recent SVN source using the "HAIKU_INSTALL_DIR=/HaikuNightly jam -q install-haiku" command, which seemed to produce a runable version of a bootable Haiku system. In order to attract and keep developers in the project it would be very helpful to read such things without inspecting Haikus website. I propose a Developer's Handbook installed alongside with the "Userguide" and "Welcome" docs on the desktop, which explains these introductory setup things. Furthermore I would suggest to narrow all possible installation configurations to "one single and common" configuration which is described step-by-step, such that, following these steps I get a development system, where I can start to code Haiku apps or even drivers (skills provided :) ). Three or more exemplary projects (may it be on the desktop) to experience the compilation process, for analysis and to look things up would dramatically flatten the introduction threshold for Windows- developers unfamuliar with GNU build tools, Jam, etc. What do you think? Cheers, Juergen