J. Wolfgang Kaltz wrote:
I'm curious whether you believe UML diagrams can be helpful for - documenting Lenya internals (and if so, do we want to do that) - discussing architectural changes
yes as long as they are kept current, which is easily possible with eclipse UML plugins. maybe we can have a build target for these?
the problem i have found is that a UML diagram of all of lenya is rather large, and needs to be decomposed to be useful.
but even if they are slightly out of date, they still help enormously to get the big picture (one of the main concerns of many first-time lenya users)
I started drawing a couple for my own benefit, first metadata, now document creation because I found it too difficult to remember how the code works otherwise :) Regarding documents, I created a Wiki page as an experiment, to see if such diagrams can help us.
But, the obvious objection is "the truth is in the source code", and when a diagram is drawn it is likely to become out of date, especially in an evolving code structure such as trunk. Another problem is that it is not only Java classes that are involved, but also Cocoon configuration files (sitemaps), Lenya configuration files, flowscript, ... I don't know how these would fit in in UML diagrams.
that is true, and is a concern for eclipe lepido, the upcoming cooon editor for eclipse which attempts to have a metamodel of cocoon that can describe not just java code, but also these config files.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
