Hi, I just did a fresh checkout of the CVS tree and saw the IK Team document go by. I took the time to read it and was impressed :) I think this is the perfect base for our developer guidelines document that the website has a spot reserved for. I'm personally in favor of this plan of attack, but feel a few things should be added before posting it to the web. First of all, the cool addon for BeIDE, for creating the headers should be approved of. With that I mean the content of the headers, the add-on is cool already :) I mention this because I mentioned tools like doxygen before, and I feel we should let the openBeBook be generated from both some seperate documentation, but also straight from the source. This makes it easy for developers to update the BeBook while making changes to the code, and if I remember correctly, an outdated BeBook was one the big problems with Be, Inc. (Also the fact that most technical writers there turned developer ofcourse :) ). Please tell me what you all think about this and lets make this a top priority, before the CVS is full of different code and comments! Regards, Ithamar.