Hi Thomas, nice to hear from you so quickly! If you could really find the time to write something, we'd be glad!
> Mathias: Can you give me more information what you would like > to have in the documentation, and is there any time limit > for writing the documentation of AndroMDA 3.0? Well, first of all, I'd like to see all the chapters in it that we have on the website. This immediately brings up the question: How do we avoid to write everything twice? I wonder how the Hibernate people do that - they have everything on the website AND in the ref. manual... Maybe, you could contact them on their mailing list and ask this question... Next, the ref. manual should include documentation for the new cartridges we have: * Richard Kunze has written the new EJB cartridge, which lacks documentation completely. Richard, could you help Thomas with some basic material? * Wouter Zoons has contributed the new bpm4struts (bpm = business process modeling) cartridge. Wouter has already provided most of the documentation together with the sources (good work, Wouter!). Wouter and I still have to discuss some aspects but the main stuff is OK and can be moved into the ref. manual. * I have begun to write the new andromda-meta cartridge that generates metaclass decorators (see my other emails on this list for an explanation). Currently, it is completely undocumented, and I will have to provide some basic material for you. Next, some development process aspects should be documented: * I can provide you with a UML activity model that documents a possible iterative, incremental development process to be used with AndroMDA. Last, some misc. things: * Tony is creating a sandbox area within our CVS repository. In the sandbox, everyone can contribute source code that will be checked and potentially become part of the code base, later. The existence and the policies behind this sandbox (once they are clear and working) should also be documented in the ref. manual. * Regression testing: The regression test module allows to test if classes generated by a new version of AndroMDA have the same API as the classes generated by the old version. This should be documented, too. * Model validation: When metaclass decorators are in place, we can implement model validation at code generation time. Example: an <<Entity>> can check whether it has at least one <<PrimaryKey>>. A <<FinderMethod>> can check if it has a tagged value called @andromda.hibernate.query. All this should be documented in the chapter about "Writing AndroMDA cartridges" because cartridge writers should know how to write/generate their own metaclass decorators. You see, there is an awful lot to do. The only chance is that we do it together. However, I think we need someone to coordinate and edit all this so that the ref.manual gets a clear structure and becomes easily understandable. This may be you. :-) Cheers... Matthias > -----Original Message----- > From: Thomas Truskaller [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 12, 2003 9:07 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: AndroMDA case study at Bioinformatics Graz, Austria > > > Hi all! > > I'am happy that my work is usful for you. By the time I've > finished my > study and now I started working at a research center > (www.joanneum.at). > > I would be glad to join your team but everything is quite new > for me (at > work now) and I'll have to find out how much sparetime I'll have and > then decide if to write documentation for AndroMDA 3.0. > > I've subscribed the developers list now and will watch the process of > AndroMDA 3.0. > > I've had a look at the Hibernate project and it's > documentation - well > there is a lot of documentation ;). I think I could do > something like > the "Reference Documentation" but I really don't know how > long it would > take me to write it. > > Mathias: Can you give me more information what you would like > to have in > the documentation, and is there any time limit for writing the > documentation of AndroMDA 3.0? > > At the end I'd like to thank all who are involved in AndroMDA > for their > great work you did and hope I'll find some time to write the > documentation. > > I'm working on a tutorial for my coleauges at the bioinformatics > institute so that they can start easily using my cartridges. > Part one is > finished now and I'm working on part 2. The first one covers: Ant, > Velocity, developing process, cartridge mechanism. At the end of the > first part, my coleauges were writing their own cartridge report ;). > Part two will cover the design of the cartridge I've > developed during my > diploma work and shold be ready in one or two weeks and cover: > architecture and design of the ejb-layer and web-layer, list model > elements and their implementation. > > Soon as I'll have the time (be patient with me ;-), I'll put my > cartridges and tutorail documantation on the web site of the > bioinformatics group. > > Greetings, Thomas > > [EMAIL PROTECTED] wrote: > > >Hi folks, > >wanna read about AndroMDA "live in action"? > >Thomas Truskaller, an Andromda user in Austria, shares his > experience > >in detail! Read Thomas Truskaller's thesis on "Data > Integration into a > >Gene Expression Database" (Sept. 2003, 71 pages, English) at the > >following > >URL: > >http://genome.tugraz.at/Theses/Truskaller2003.pdf > >Thomas: Great work! Would you join us and write a user > manual for AndroMDA > >3.0, similar to the one that the Hibernate project has, > please? It seems > >as if you are a member of the rare species that enjoy writing clearly > >understandable documents! :-) > >Cheers... > >Matthias Bohlen > > > > > > > > ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
