Hi Ingrid,
Let me try an example with the chart to show the problem:
[snip]
There are many many other modules involved.
Hmmm. Just to keep the focus clear, do you also like to present this
type of information already? Or is this merely to illustrate that
creating a table as suggested by John is very hard to accomplish? I
think it should be possible to not focus too much on the connections
between the projects, but mainly on presenting the projects itself in a
much more structured manner. Of course this structure will probably
relate to how the projects relate to each other, but then from a
relative abstract point of view.
I could imagine e.g. having the blocks writer, calc, impress/draw, and
these packed in whatever project creates the basic architecture, which
also includes offering additional 'services' like chart functionality.
Above all blocks the ui project... etc. These kind of drawings are
pretty common right, in communicating basic software architecture?
Wouldn't that be an idea for the project page, and in addition add links
directly to the development page and/or end-user page? If draws it, and
tells me where the links should point to, I'm willing to turn it into
some friendly looking HTML.
Yours,
Maarten
--
Maarten Brouwers (murb)
http://www.murb.nl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
