Howdy, I like it ;) Except there's a "Betwixt" section and a "Project Documentation" section, which I think could be the same section no? It is the Betwixt project page after all ;) Regardless, I want to see Project Documentation above the general commons menus. But I imagine that would be a simple matter of which order the entities were included right?
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: robert burrell donkin [mailto:[EMAIL PROTECTED] >Sent: Monday, August 18, 2003 6:28 PM >To: Jakarta Commons Developers List >Subject: Re: [docs] extra menus for mavenised components > >i've committed the factoring out the main menu's into entity's. i've added >some commons menus into betwixt (http://jakarta.apache.org/commons/betwixt/ >index.html) if you want to take a look. > >probably needs some more tweaks before it's really right (i'd like to be >able to separate out the commons menus) but it shows the basic idea ok. > >- robert > >On Saturday, August 16, 2003, at 07:12 PM, Henri Yandell wrote: > >> >> +1 for this. >> >> Do you have a url example of what change we can expect to see to a >> mavenised project? >> >> Hen >> >> On Sat, 16 Aug 2003, robert burrell donkin wrote: >> >>> one of the problems with the current commons website is that most >>> mavenized components do not carry links back into jakarta-commons. i >>> think >>> that a major reason for this is that these have to maintained separately >>> for each component and can easily become out-of-date. >>> >>> i've been playing around today and would like to offer a (partial) >>> solution. it's possible to declare the menu entries as entities in a >DTD. >>> this DTD can include these from xml fragment files. the information >would >>> be moved from the project.xml into fragments and referenced from a DTD. >>> >>> (yes, i know that XInclude's are much better but it would involve extra >>> overhead and extra learning for people. this way means that the existing >>> process can be retained.) >>> >>> anyway, in practice this means that by adding a DTD definition to the >top >>> of a navigation.xml, mavenized components will be able to choose to >>> include menus from the jakarta commons main menu. ever time that the >>> documentation is rebuilt, the most up to date versions will be grabbed >>> and >>> used - zero maintenance for the component. >>> >>> unless some folks come up with some good reasons not to do this, i'll >>> move >>> the menus from the project.xml into xml fragment files sometime soon. >>> >>> - robert >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
