commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Pugh" <>
Subject RE: Change Commons Nav to Collapsed?
Date Sun, 15 Feb 2004 14:33:22 GMT
I see..  I thought doing this would solve the problem:
<item name="Commons" href="commons.html" collapse="true">

But it just makes a collapsed menu option, you can't uncollapse it, I guess
because of the way we import the shared xml file.  The locally created
"commons.html" doesn't know/isn't generated with the collapse being false.
I assume because of crossing project boundaries?

Something that might work well at least in the short term is to ditch all
the items under each menu item, and instead have the menu just link to a
page on the main site.  That would
reduce it down to 8 hotlinks, and not require every subproject to have lots
of complex shared XML files that import the shared entities..  I'm thinking
this really might help cleanup the various Sandbox websites that often
become old/out of date because keeping their project documenation files up
to date is hard..

We could use the existing Maven commons/xdocs file to host the subproject
pages that are linked to..  so we would have /commons.xml, /download.xml, or
/xdocs/commons/index.xml, /xdocs/download/index.xml,
/xdocs/viewcvs/index.xml, /xdocs/community/index.xml that would link to all
the seperate pages.

And maybe at this point update the commons main site to be just Maven l&F?


> -----Original Message-----
> From: robert burrell donkin
> []
> Sent: Sunday, February 15, 2004 2:35 PM
> To: Jakarta Commons Developers List
> Subject: Re: Change Commons Nav to Collapsed?
> hi eric
> this has been discussed before and the consensus was that the
> collapsable menus would be the best solution. the issue is that some
> maven work is needed to make them work. (just setting them to
> collapsable does nothing useful since the collapsable feature is
> designed to work with maven generated documentation.)
> one suggestion was to create (or amend) a maven plugin so that these
> would be generated automagically. dIon volunteered to take a look at
> this a while ago but he's busy and AFAIK there's no results from that
> as yet.
> i happened to be chatting with trygve about this (on maven
> IRC) and he
> has come up with a new plan (which sounds easier than the
> original). we
> create shared xml files and add them into the documentation builds.
> this sounds like it should make the collapsable thing work
> but someone
> needs to step up and create the files and (probably) do a
> little jelly
> magic. ATM i'm busy working on piping betwixt into JaxME (the apache
> JAXB implementation) so i don't have the time to do it right now. i
> hope to find time sometime sooner rather than later but there's a lot
> of stuff stacked up for me right now. so i'd be glad if a volunteer
> stepped up to give this plan a go.
> - robert
> On 15 Feb 2004, at 13:15, Eric Pugh wrote:
> > Hi all,
> >
> > I am noticing that the very long list of commons components
> and commons
> > sandbox components makes the left nav for the Maven enabled
> projects
> > quite
> > difficult to read..  The key information about the
> component gets lost
> > in
> > the Menu.
> >
> > What do you think of using the collapse="true" attribute or
> removing
> > it and
> > providing a link in the top menu to Components and Sandbox?
> >
> > Eric
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message