- LOGO: great idea, we should do this. - XLoadTree is already out (damn we're fast :)) so documentation will be usable offline as well as online. We should then also include a local SF logo (for offline docs). Maybe 2 documentation targets in the build file? Or a property in build.properties?
- XDoclet.ORG: I am willing to register it and forward to xdoclet.sf.net. Costs only 12 euro's per year at Gandi. >> Only changes needed would be if we wanted to change the package hierarchy >>to org.xdoclet.whatever... But I don't really feel this is needed. Who says we are not going to register xdoclet.org, xdoclet.info AND xdoclet.xxx ?? Cheers, Mathias -----Original Message----- From: Andrew Stevens [mailto:[EMAIL PROTECTED]] Sent: donderdag 16 mei 2002 14:04 To: [EMAIL PROTECTED] Subject: RE: [Xdoclet-devel] Strategies for doc generation >FROM: Mathias Bogaert >DATE: 05/16/2002 03:00:37 > >Here are my thoughts: > >1. Someone mentioned on the list that the current xtags.xml are not strong >enough to do the validation he required, and he proposed we should look >into >XML Schema to use for this. But offcourse, this is again more work. >I like the current way, the XSL renders the docs nicely. Well, I mentioned it the other day but I was only remarking on Konstantin's comments from when he originally put the bluestone stuff into xdoclet-tags.xml. I'm not saying we necessarily should switch to a schema, just wondering whether that would have helped with his problems defining some of the bluestone conditions. As for the docs, I've got a request. Originally, we just copied the docs from the dist onto SF's web server. Later, since they were hosting it, I added a link and the SF logo into the toc. The following release, because SF said they were only going to use the logo to track hits for the project activity stats, I added it a couple of other pages too. But in each case, I've just edited it by hand afterwards. Now that we're going to generate them with XSL, it would be nice if there was a second target in the build script I can use to generate the web site docs, with extra bits in its stylesheets to include the SF logo tags. It should include it at the bottom of all the toc-type left hand frames (use the same size we have at the moment) and maybe some of the others (e.g. Introduction, Resources and Who are We) as at present, plus (just to help boost our activity stats :-) ) include a 0x0 pixel copy at the end of every other page. That'll save me a load of editing in future releases. Oh yes, and IMO, the downloaded docs bundle should be totally standalone i.e. useable offline. Include a local copy of the SF logo if we want it anywhere in there, and if XLoadTree can't handle it let's modify it so it can or find something else to do the job. Lastly, there was talk a few weeks back about registering xdoclet.org. Is there still any interest/objections? We wouldn't need to start hosting it ourselves or move off SF or anything (the main objections last time IIRC), it could just have web forwarding/redirection to the current SF site set up. Only changes needed would be if we wanted to change the package hierarchy to org.xdoclet.whatever... Andrew. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
