On 26/11/14 10:17, Bryce Harrington wrote:
On Wed, Nov 26, 2014 at 10:04:52AM +0100, Diederik van Lierop wrote:
http://wiki.inkscape.org/wiki/index.php/Architectural_overview http://wiki.inkscape.org/wiki/index.php/SubsystemRearchitecture http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/download/head:/arch...
Thanks for the input, and you're right. This ought to be a lot better. What we do have came years ago after a complaint quite similar to what you're making today, and likely is a bit obsolescent now. It seems that once someone understands the codebase architecture well enough to document it, they lose the need for (and thus interest in writing) said documentation! :-)
I'm trying to add at least doxygen comments to everything I need to figure out while implementing the "flatten vectors" feature I need.
Can you pose some architectural questions that we could use to help guide documentation writing?
- How are objects stored? How can they be accessed / modified / how can I find out if they are clipped etc. - How is object storage related to SVG? e.g. SPDocument->SPRoot <--> <svg>, to me that was non-obvious - Is every Object (except SPDocument->SPRoot) guaranteed to have a parent object?
Alexander