Hi! See my inlined comments.
For those of you curious about the XDoclet GUI, please see my separate posting to the devel list. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Ara > Abrahamian > Sent: 24. januar 2002 17:56 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: [Xdoclet-user] Documentation > > > > I think Ara made an attempt to set up an FAQ on jguru.com. How's that > > going Ara? > > Still waiting! The guy should be very busy :o) > Can you bugger him? > > The xtags subproject will describe the tags in one or more xml files. > > These xml files will be used to generate documentation (among other > > things). > > Ah xtags! Yeah! Now that I finished implementing the new config system I > can put a lot of time on it. I've seen Konstantin's stuff, any chance I I haven't had time to see it yet. I'm looking forward to it. > can see what you've done Aslak? We'll first unify the two efforts (we I just checked in a ton of code. XDoclet GUI and more xjavadoc. > need a new branch), refactor them probably and move on to complete it. > Please send me the xml/dtd/reader/xbean parts of what you've done. It's in xdocletgui > Remember we should provide backward-compatibility too, so new system > should not dictate the existence of the tag definitions in xml. That's > what I see missing in what Konstantain did, and is very important. > I'm not sure if I understand what you mean by backward-compatibility and how it could be compromised by tag definitions in xml. Can you elaborate? > > Perhaps you have some tips about what you'd like to see in the Howto? > - > > I mean, it's not always obvious to us developers what is > not-so-obvious > > to ordinary users. We'd like to hear your suggestions. How about this: > > > > 1) Setting up your Ant build script > > 2) Writing a simple EJB > > 3) Building the EJB > > 4) Deploying the EJB > > 5) Testing the EJB > > > > Basically everything is in the docs/examples, but I agree with you > that > > there is no clear description of the process (what steps to follow in > > what order). > > An ejbdoclet/webdoclet/etc tutor. Plus each subtask should have an > example section, showing how you use it and what it generates. > > What do you think about a set of project templates? I mean not a .j > template but simply an empty project (say > ejb-project/web-project/j2ee-project/etc), with a predefined directory > structure like the one in samples and ready and commented build.xml file > (<!--uncomment it if you want to have local intf-->) and some readme > files in each directory (put your java beans here/etc). I think it'll be > beneficial, because many ppl waste their time struggling with wrong > classpathrefs and paths. What do you think? > Agree. About classpathrefs: I usually put everything on the Ant classpath in my bat scripts (see how it's done in xjavadoc and xdocletgui. This way there is no need to pass classpath to the tagdef. > Ara. > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
