It's nice that you care about the report Alex. But I am somewhat pessimistic about improvements to the documentation. I think the single most important documentation for a floss project is how to get it built from scratch. And it must be easy to build, so the documentation is short and understandable. I ran away in desperation trying to build OpenOffice; Inkscape is very easy on windows luckily. Only thing left to do is remove the old and obsolete documentation and point to the correct wiki page. And then: get the people in our jabber or IRC channel, there's almost always people around to help with questions! All the class diagrams, code organization, etc, I think it is hardly ever used or read. It is just too much to try and read about how a big program like Inkscape works, without having looked at the code for a long time. And, once you know how a certain piece works, the documentation on the website has become almost useless, so motivation is lacking to document it. Sifting through code is much more precise and quicker. I use notepad++'s find-in-all-files certainly once every minute during development. I usually understand written code very quickly, so maybe it doesn't work as well for people that are newer to the language. In any case, I know little of Inkscape, and am still able to contribute. Some parts I know well, some parts I don't know anything about. It's not needed to know all :-), certainly not for all the "low hanging fruit" that we have. To new devs: join our chat channel! Cheers, Johan

2009/1/2 Diederik van Lierop <mail@...1689...>: I agree, although I spent a full summer working on Inkscape before I discovered this info in the wiki. Just like Johan I usually investigate code by looking at it, and often enough I find myself grepping through the whole code to understand how pieces of code are interconnected (no need for Notepad++, though :-P ). Still, every now and then I don't understand what the SPFooBar class is supposed to mean or how it relates to the things I see on my canvas and then I'm grateful if there is some piece of documentation on it. So I believe we definitely should have this material as as reference, but I feel it could be improved to help newbie developers better understand the class hierarchy. Unfortunately, I don't feel qualified/capable of doing this atm. :-( Max