On 01/02/2009 06:23 AM, J.B.C.Engelen@...1578... wrote:
All the class diagrams, code organization, etc, I think it is hardly
ever used or read.
Well, I think most of us have read that at least once. At least I did.
It can at least serve as a primer, and if it's kept up-to-date then it
can even be a reference
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
The code base itself is obviously the ultimate reference, but it's
essential for new devs to have a wiki that explains the what a SPView /
SPNamedView / SPDesktop / SPDocument etc. are. That will give you the
big picture much faster.
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.
Refactoring isn't always fun either, is it? Motivation
can surely be
found for such a thing, otherwise we would have never gotten our
excellent Inkscape book and guide.
To answer Alexander's questions:
1) yes, I think it's sufficient. We need a primer, not a complete
reference (although that would be great to have too)
2-4) we need some feedback from our most experience devs here, most part
of it I cannot judge