Architecture diagrams

[James Gregory]

Guys,

I've just finished knocking up some architecture diagrams to help people get to grips with the structure of Docu; there's a key players overview and then a fairly detailed look at each phase. You can find it all on the wiki under ArchtiectureDiagrams, and they're also in the docs directory in the root of the project. All the diagrams were generated with either http://www.websequencediagrams.com or http://yuml.me , and for each diagram in the docs directory there's a corresponding txt file that contains the text needed to recreate the diagram; you're welcome to update the diagrams as needed.

James

[James Gregory]

FYI github appears to be clipping the images, but you can click on them to open up the source.

[Josh Flanagan]

This is great James, it will help a lot. Thanks for putting it together.
And thanks for introducing me to those 2 sites.

Once I get done with a few of the features/bug fixes I'm working on, I'd like to do code reorganization & ndepend analysis to make it align more clearly with this design. For example, we have a UI namespace, but the code is related to the output - which is much different than the UI component described in the diagram (which I think is more appropriate).

[James Gregory]

No worries, and yes, a re-org is in order. I also think we should decide on some proper names for the various classes that are involved in each stage. DocumentModel doesn't really say much, and then there's BaseDocumentElement and BaseDocumentMember which are both a little too close in naming.