You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Eric Pugh <ep...@upstate.com> on 2004/02/15 14:15:05 UTC
Change Commons Nav to Collapsed?
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
To move the Site Documentation up you need to upgrade your xdoc plugin
to the latest (version 1.5), caution, this also changes the css style of
the site.
the command to upgrade the xdoc plugin is:
%maven -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.5
plugin:download
-Mark
Mark R. Diggory wrote:
> It looks like this feature is pretty new to the xdoc plugin cvs and not
> currently in this release candidate. I suspect it will be in the next,
> otherwise I can recommend that we upgrade all our xdoc plugin tot eh
> latest release.
>
> I'll test this further later today.
>
> -Mark
>
> Stephen Colebourne wrote:
>
>> From: "robert burrell donkin" <ro...@blueyonder.co.uk>
>>
>>> i like this sounds of this (regardless of whether we find a way to make
>>> the menus collapse or not.
>>
>>
>>
>> +0. I still think we should add explicit links in the top section for
>> each
>> project.
>>
>> I was thinking that maybe the Sandbox projects should _not_ be linked
>> on the
>> side of every page. These projects are not released, and can move and
>> vary
>> more over time. Perhaps the best combination is for links for each
>> commons
>> proper project, and a single link for the sandbox. I would like to demote
>> the sandbox a bit - it might have the effect of pushing some projects to
>> promote ;-)
>>
>> Stephen
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Martin Cooper wrote:
>
>>-----Original Message-----
>>From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
>>Sent: Sunday, February 15, 2004 5:15 PM
>>To: Jakarta Commons Developers List
>>Subject: Re: Move Commons projects below "Project Documentation" in
>>Navigation
>>
>>
>>
>>
>>Martin Cooper wrote:
>>
>>
>>>>It looks like this feature is pretty new to the xdoc plugin cvs and not
>>>>currently in this release candidate. I suspect it will be in the next,
>>>>otherwise I can recommend that we upgrade all our xdoc plugin tot eh
>>>>latest release.
>>>
>>>
>>>It seems to me that this is, at least in part, why Maven has not even
>>>reached a 1.0 release, after it's been around, and been used,
>>
>>for so long.
>>
>>>If they're adding new features in a release candidate, I don't have much
>>>confidence that there ever will be a 1.0 final release. ;-(
>>>
>>>--
>>>Martin Cooper
>>>
>>
>>Hmm, but Maven itself hasn't changed, its the natural evolution of the
>>plugins alone. the xdoc and site plugins are naturally going to advance
>>in feature as more users provide input.
>>
>>You can "upgrade" the plugins very easily in Maven, if anything this
>>flexibility makes Maven even stronger. I disagree with the comment about
>>a 1.0 release, the features in a specific plugin arn't going to define
>>or limit the release of Maven itself.
>
>
> That's all very nice, but it doesn't matter to me as a regular Maven user
> any more than whether it's a standard plugin or the core itself that's
> broken when I have a problem with Eclipse. From my perspective, if I
> download Maven and something isn't working, Maven is broken, regardless of
> whether it's a plugin or the core. (For example, as far as I'm concerned,
> Maven RC1 is broken because it generates incorrect Ant build files, where
> prior versions worked. It doesn't matter to me if that's because of a plugin
> bug, it's still broken.)
>
> --
> Martin Cooper
>
Sigh...
Every situation can be viewed from anywhere within a continuum of
negative to positive perspectives. How often we are quick to levy blame
when what is really needed is a helping hand.
I'd rather see my discussions stay on topic. This one no longer is...
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: Move Commons projects below "Project Documentation" in Navigation
Posted by Martin Cooper <ma...@apache.org>.
> -----Original Message-----
> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
> Sent: Sunday, February 15, 2004 5:15 PM
> To: Jakarta Commons Developers List
> Subject: Re: Move Commons projects below "Project Documentation" in
> Navigation
>
>
>
>
> Martin Cooper wrote:
>
> >>
> >>It looks like this feature is pretty new to the xdoc plugin cvs and not
> >>currently in this release candidate. I suspect it will be in the next,
> >>otherwise I can recommend that we upgrade all our xdoc plugin tot eh
> >>latest release.
> >
> >
> > It seems to me that this is, at least in part, why Maven has not even
> > reached a 1.0 release, after it's been around, and been used,
> for so long.
> > If they're adding new features in a release candidate, I don't have much
> > confidence that there ever will be a 1.0 final release. ;-(
> >
> > --
> > Martin Cooper
> >
>
> Hmm, but Maven itself hasn't changed, its the natural evolution of the
> plugins alone. the xdoc and site plugins are naturally going to advance
> in feature as more users provide input.
>
> You can "upgrade" the plugins very easily in Maven, if anything this
> flexibility makes Maven even stronger. I disagree with the comment about
> a 1.0 release, the features in a specific plugin arn't going to define
> or limit the release of Maven itself.
That's all very nice, but it doesn't matter to me as a regular Maven user
any more than whether it's a standard plugin or the core itself that's
broken when I have a problem with Eclipse. From my perspective, if I
download Maven and something isn't working, Maven is broken, regardless of
whether it's a plugin or the core. (For example, as far as I'm concerned,
Maven RC1 is broken because it generates incorrect Ant build files, where
prior versions worked. It doesn't matter to me if that's because of a plugin
bug, it's still broken.)
--
Martin Cooper
>
> See my other post concerning how to upgrade the xdoc plugin with one
> command line option.
>
> -Mark
>
> --
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Martin Cooper wrote:
>>
>>It looks like this feature is pretty new to the xdoc plugin cvs and not
>>currently in this release candidate. I suspect it will be in the next,
>>otherwise I can recommend that we upgrade all our xdoc plugin tot eh
>>latest release.
>
>
> It seems to me that this is, at least in part, why Maven has not even
> reached a 1.0 release, after it's been around, and been used, for so long.
> If they're adding new features in a release candidate, I don't have much
> confidence that there ever will be a 1.0 final release. ;-(
>
> --
> Martin Cooper
>
Hmm, but Maven itself hasn't changed, its the natural evolution of the
plugins alone. the xdoc and site plugins are naturally going to advance
in feature as more users provide input.
You can "upgrade" the plugins very easily in Maven, if anything this
flexibility makes Maven even stronger. I disagree with the comment about
a 1.0 release, the features in a specific plugin arn't going to define
or limit the release of Maven itself.
See my other post concerning how to upgrade the xdoc plugin with one
command line option.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: Move Commons projects below "Project Documentation" in Navigation
Posted by Martin Cooper <ma...@apache.org>.
> -----Original Message-----
> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
> Sent: Sunday, February 15, 2004 9:50 AM
> To: Jakarta Commons Developers List
> Subject: Re: Move Commons projects below "Project Documentation" in
> Navigation
>
>
> It looks like this feature is pretty new to the xdoc plugin cvs and not
> currently in this release candidate. I suspect it will be in the next,
> otherwise I can recommend that we upgrade all our xdoc plugin tot eh
> latest release.
It seems to me that this is, at least in part, why Maven has not even
reached a 1.0 release, after it's been around, and been used, for so long.
If they're adding new features in a release candidate, I don't have much
confidence that there ever will be a 1.0 final release. ;-(
--
Martin Cooper
>
> I'll test this further later today.
>
> -Mark
>
> Stephen Colebourne wrote:
>
> > From: "robert burrell donkin" <ro...@blueyonder.co.uk>
> >
> >>i like this sounds of this (regardless of whether we find a way to make
> >>the menus collapse or not.
> >
> >
> > +0. I still think we should add explicit links in the top
> section for each
> > project.
> >
> > I was thinking that maybe the Sandbox projects should _not_ be
> linked on the
> > side of every page. These projects are not released, and can
> move and vary
> > more over time. Perhaps the best combination is for links for
> each commons
> > proper project, and a single link for the sandbox. I would like
> to demote
> > the sandbox a bit - it might have the effect of pushing some projects to
> > promote ;-)
> >
> > Stephen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
> --
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
It looks like this feature is pretty new to the xdoc plugin cvs and not
currently in this release candidate. I suspect it will be in the next,
otherwise I can recommend that we upgrade all our xdoc plugin tot eh
latest release.
I'll test this further later today.
-Mark
Stephen Colebourne wrote:
> From: "robert burrell donkin" <ro...@blueyonder.co.uk>
>
>>i like this sounds of this (regardless of whether we find a way to make
>>the menus collapse or not.
>
>
> +0. I still think we should add explicit links in the top section for each
> project.
>
> I was thinking that maybe the Sandbox projects should _not_ be linked on the
> side of every page. These projects are not released, and can move and vary
> more over time. Perhaps the best combination is for links for each commons
> proper project, and a single link for the sandbox. I would like to demote
> the sandbox a bit - it might have the effect of pushing some projects to
> promote ;-)
>
> Stephen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "Martin Cooper" <ma...@apache.org>
> > From: Stephen Colebourne [mailto:scolebourne@btopenworld.com]
> > I was thinking that maybe the Sandbox projects should _not_ be
> > linked on the
> > side of every page. These projects are not released, and can move and
vary
> > more over time. Perhaps the best combination is for links for each
commons
> > proper project, and a single link for the sandbox. I would like to
demote
> > the sandbox a bit - it might have the effect of pushing some projects to
> > promote ;-)
>
> I strongly disagree with decreasing the visibility of sandbox components.
> One of the reasons they are in the sandbox is often because they still
need
> to form a community around themselves. The chances of that happening are
> going to be lower if people don't even know the components exist. Recall
> that quite recently we had a long discussion about many sandbox components
> not having a web presence, and the concensus was to create a web presence
> for them so as to *increase* their visibility.
I am happy for links to sandbox components from the commons home page. I am
just questioning whether they need/should be linked from every commons
proper page. Its a balance.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: Move Commons projects below "Project Documentation" in Navigation
Posted by Martin Cooper <ma...@apache.org>.
> -----Original Message-----
> From: Stephen Colebourne [mailto:scolebourne@btopenworld.com]
> Sent: Sunday, February 15, 2004 9:00 AM
> To: Jakarta Commons Developers List
> Subject: Re: Move Commons projects below "Project Documentation" in
> Navigation
>
>
> From: "robert burrell donkin" <ro...@blueyonder.co.uk>
> > i like this sounds of this (regardless of whether we find a way to make
> > the menus collapse or not.
>
> +0. I still think we should add explicit links in the top section for each
> project.
>
> I was thinking that maybe the Sandbox projects should _not_ be
> linked on the
> side of every page. These projects are not released, and can move and vary
> more over time. Perhaps the best combination is for links for each commons
> proper project, and a single link for the sandbox. I would like to demote
> the sandbox a bit - it might have the effect of pushing some projects to
> promote ;-)
I strongly disagree with decreasing the visibility of sandbox components.
One of the reasons they are in the sandbox is often because they still need
to form a community around themselves. The chances of that happening are
going to be lower if people don't even know the components exist. Recall
that quite recently we had a long discussion about many sandbox components
not having a web presence, and the concensus was to create a web presence
for them so as to *increase* their visibility.
--
Martin Cooper
>
> Stephen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "robert burrell donkin" <ro...@blueyonder.co.uk>
> i like this sounds of this (regardless of whether we find a way to make
> the menus collapse or not.
+0. I still think we should add explicit links in the top section for each
project.
I was thinking that maybe the Sandbox projects should _not_ be linked on the
side of every page. These projects are not released, and can move and vary
more over time. Perhaps the best combination is for links for each commons
proper project, and a single link for the sandbox. I would like to demote
the sandbox a bit - it might have the effect of pushing some projects to
promote ;-)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Move Commons projects below "Project Documentation" in Navigation
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
i like this sounds of this (regardless of whether we find a way to make
the menus collapse or not.
- robert
On 15 Feb 2004, at 16:08, Mark R. Diggory wrote:
> This idea has been proposed before, only people thought it not
> possible. However, after some digging, I found out it is.
>
> <j:if test="${date == 'navigation-top'}">
> <div id="lastPublished">Last published:
> ${build.date}</div>
> </j:if>
> <x:if select="$nav">
> <jsl:applyTemplates select="$nav/body/menu[not(@type) |
> @type='header'] | $nav/body/search"/>
> </x:if>
> <jsl:applyTemplates select="$projectNav/body/menu"/>
> <!-- allows user to put menu items after standard reports
> -->
> <x:if select="$nav">
> <jsl:applyTemplates
> select="$nav/body/menu[@type='footer']"/>
> </x:if>
>
> http://cvs.apache.org/viewcvs.cgi/maven-plugins/xdoc/src/plugin-
> resources/site.jsl
>
> in the site.jsl when processing the navigation, if the following
> 'type="footer" attribute is added to any menu tag, then the navigation
> menu shows up "after" the Project Documentation.
>
> This should solve alot of the complaints about showing all the Commons
> Project in the navigation, because everyone is really trying to get to
> the Project Doc.
>
> -Mark
>
> --
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Move Commons projects below "Project Documentation" in Navigation
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
This idea has been proposed before, only people thought it not possible.
However, after some digging, I found out it is.
<j:if test="${date == 'navigation-top'}">
<div id="lastPublished">Last published: ${build.date}</div>
</j:if>
<x:if select="$nav">
<jsl:applyTemplates select="$nav/body/menu[not(@type) |
@type='header'] | $nav/body/search"/>
</x:if>
<jsl:applyTemplates select="$projectNav/body/menu"/>
<!-- allows user to put menu items after standard reports -->
<x:if select="$nav">
<jsl:applyTemplates select="$nav/body/menu[@type='footer']"/>
</x:if>
http://cvs.apache.org/viewcvs.cgi/maven-plugins/xdoc/src/plugin-resources/site.jsl
in the site.jsl when processing the navigation, if the following
'type="footer" attribute is added to any menu tag, then the navigation
menu shows up "after" the Project Documentation.
This should solve alot of the complaints about showing all the Commons
Project in the navigation, because everyone is really trying to get to
the Project Doc.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Change Commons Nav to Collapsed?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
I'm -0 to hiding the commons proper links. I think that they are a key part
of letting us and users navigate around the commons site, and are part of
keeping it one community. Also, the maven collapsable stuff is slow and
clunky and I basically hate it. (the sandbox is different for other reasons)
I would prefer to try reversing the order of project docs and commons links
before any talk of collapsable.
Stephen
----- Original Message -----
From: "robert burrell donkin" <ro...@blueyonder.co.uk>
> <snip>
>
> > 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 http://jakarta.apache.org/commons/ 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.
>
> i think that the major part of the work involved with making the menus
> collapsable would be the creation of the documents you suggest. once
> that's done, we could then use some jelly magic to use them as the
> navigation place holders that the collapsable menus need to work.
>
> - robert
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Change Commons Nav to Collapsed?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On 15 Feb 2004, at 14:33, Eric Pugh wrote:
<snip>
> 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 http://jakarta.apache.org/commons/ 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.
i think that the major part of the work involved with making the menus
collapsable would be the creation of the documents you suggest. once
that's done, we could then use some jelly magic to use them as the
navigation place holders that the collapsable menus need to work.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Change Commons Nav to Collapsed?
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I've been a little aggressive this morning in terms of cleaning up the
maven xdoc and build files. Be warned I removed
/jakarta-commons/xdocs
/jakarta-commons/maven.xml
/jakarta-commons/project.xml
/jakarta-commons/incl_nav.xml
/jakarta-commons/navigation.xml
/jakarta-commons/project.properties
and the new copies have been located for about a week at
/jakarta-commons/commons-build/xdocs
/jakarta-commons/commons-build/maven.xml
/jakarta-commons/commons-build/project.xml
/jakarta-commons/commons-build/incl_nav.xml
/jakarta-commons/commons-build/navigation.xml
/jakarta-commons/commons-build/project.properties
I've adjusted the /jakarta-commons/<project>/xdoc/navigation.xml files
that had the navigation included to point at this new location. I've
adjusted the /jakarta-commons/<project>/project.xml that previously
extended ../project.xml to extend ../commons-build/project.xml
please let me know if anyone encounters any difficulty.
-Mark
robert burrell donkin wrote:
> On 15 Feb 2004, at 14:33, Eric Pugh wrote:
>
> <snip>
>
>> And maybe at this point update the commons main site to be just Maven
>> l&F?
>
>
> we're still a little way off being able to think about doing this. we
> need all the components sites switching to the mavenized documentation
> build first. we need volunteers to convert (or at least ensure that the
> mavenized build is current and linked) for discovery, el, jexl, and
> modeler. any volunteers to take these on?
>
> - robert
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Change Commons Nav to Collapsed?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On 15 Feb 2004, at 14:33, Eric Pugh wrote:
<snip>
> And maybe at this point update the commons main site to be just Maven
> l&F?
we're still a little way off being able to think about doing this. we
need all the components sites switching to the mavenized documentation
build first. we need volunteers to convert (or at least ensure that
the mavenized build is current and linked) for discovery, el, jexl, and
modeler. any volunteers to take these on?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: Change Commons Nav to Collapsed?
Posted by Eric Pugh <ep...@upstate.com>.
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 http://jakarta.apache.org/commons/ 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?
Eric
> -----Original Message-----
> From: robert burrell donkin
> [mailto:robertburrelldonkin@blueyonder.co.uk]
> 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: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Change Commons Nav to Collapsed?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org