[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ozoneUML
> Yeah, I did those a while ago with Together,
> I think Per had some out as well done the same way,
> I never really spread the word beyond the dev-list then as Falko said,
> (with good reason) that they may have a little too much detail for
> casual use.
Right, I put some UML class diagrams in the Hacking Howto but I'm not sure
this is a very good way of illustrating class dependencies and hierarchy for
this very reason. Seems to become too much or too little but seldom just
right when doing these diagrams -at least when they stand by themselves as
you point out below.
> I'm also not sure how up to date the package is, I did it of a CVS snap
> around febuary sometime, and I haven't really had time to look at the
> latest Ozone sources.
This is the problem with using together to generate it (by nature manually
initiated). If we had a tool that could be batched we could do a nightly
generation of class diagrams and javadoc from CVS and make it available
online and for download. Does anyone know of a tool that gives similar
functionality as together (in terms of generating UML that is) but is free
and batch-able?
> I could do another one sometime if enought people wanted one,
> however, as Falko said, I think this kind of thing should actually be
> bought under the discussed ODP (Ozoe Doc Project) and disscussed and
> planned properly, I currently do some work for the GNOME doc project,
> and I think it's a really good idea to have an Ozone Doc Project,
> http://www.docbook.org is a good place to start for any wanting to find
> out more about docbook, and I thing the GDP has a good white paper on
> contributing that makes good reading for any wanting to get involved in
> any kind of open-source doc effort.
> (http://developer.gnome.org/gdp)
The link seems to be broken (at least i cannot find a page there)
> As discussed a while ago, the UML needs more than just class diags, it
> also needs (IMHO) state diagrams and use cases, as this makes the whole
> thing alot clearer to people who may not have that much experience.,
> also to selectivly prune the amount of information into realistically
> sized chunks and do, say, a users' diagram pak, with the core API's and
> some basic state diagrams, and a developers pak, which has a more in
> depth series of diagrams and charts...
> comments?
Yes, i think that would be a wonderful idea. Would you have time to create
an initial draft?
Best regards,
Per