That's perfect. Gather all the information somewhere and then organize
and polish it and put it in regular webpages or pdf or whatever.
For what it is worth, I would be glad to volunteer to help improve (and pdf) documentation if it is in at least a rough form. Espessially tutorials, help docs etc. It is the "Gather all the information somewhere" that I am not up to trying right now... wading through the archives to organize the documentation (and deciding what info is correct) is not feasable for me at this time.
I'm thinking about a kicking off a process of a formal avalon specification. This would encompass the APIs on framework, composition, meta, repository and logging. My presumption is that this would be a classic specification (i.e. along the lines of a formal standard spec.) - sources in Word, publication via PDF. If your interested in collaboration this please let me know.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
