Leo, Missing a FAQ. Our biggest problem concerns people confusing 'Avalon (project)' with Avalon-Framework, Avalon-Ecalibur etc.
- Paul >I propose we re-organise documentation a bit. > >I'll start with the framework documentation. > >Suggestion: > >- Essentials > - Overview > - Features > (new) > - Getting Started > (new) > - Downloads > >- Guide > - OOP best practices > (modified reuse-standards.html) > - What are Patterns? > (modified from patterns.html) > - Patterns in Avalon > (modified from "Patterns and Design") > - What is COP? > (modified from "The Api") > - COP in Avalon > (modified from "The Api") > - Where to go from here > (link to "Developing with Avalon") > >- Reference > - Api Docs > - Diagrams Docs > - The Lifecycle > (new) > >- For Developers > - Changes > - Coding standards > - Project structure > - CVS > - Mailing Lists > >After your comments are integrated into this, >and there are no -1s, I will make all the >required changes as soon as I have time. > >- Leo > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
