RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
> -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, February 21, 2005 2:50 PM > To: 'Maven Developers List' > Subject: RE: svn commit: r154533 - in > maven/maven-1/plugins/trunk/xdoc: > pr oject.properties project.xml src/plugin-resources/site.jsl > xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml > > > > Michal, I am not criticizing your work, quite the opposite > actually. I think > the breadcrumb is a very nice thing. I'm just saying that we > need to find a > solution for putting the "doc for" information in a visible > place (as it > was). NP. I never felt that you are criticizing me :) For me this new improved navigation is just much more important feature than dates, versions etc. I find it rather unacceptable then when you are viewing maven generated sites for modules like this one: http://geronimo.apache.org/modules/jetty/index.html you have no information about the context in which this module emerged and you cannot easily navigate to sibling/parent modules. I am all for including version/date etc in visible place if somebody finds it useful :) We just need to find the right place for them... Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
> -Original Message- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: lundi 21 février 2005 14:38 > To: 'Maven Developers List' > Subject: RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr > oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . > xml xdocs/index.xml xdocs/navigation.xml [snip] > > I think they're worse in that regards :-) I personally think > > that the doc > > for is important. I use it all the time when I view Maven web sites. > > > > It is quite subjective judment :) It is. Which is why all committers and users need to voice their opinion and the reason I'm voicing mine :-) [snip] > Say I am still using m1 1.0.0 and version 1.0.2 was already released. I > have > absolutely no clue what's the version of > each and particular plugin which I am currently using (and I am quite > close > to the source ;) ) Just type "maven -i" or go look into your MAVENHOME/plugins directory (but I'm sure you know this already ;-)). > and if the information available at the website is at all relevant for me. > I really don't care what's the current version of any of those plugins > (and > there is too many of them to rememebr any versions) > - this is something only important for developers not for end users. It is if you're considering Maven as a package but we've been trying to decouple the plugins from the core and thus each plugins has to be considered as having his own release lifecycle. I still maintain the "doc for" is a useful piece of information that should be made visible rather than hidden. > > For plugins it would make more sense to somehow document changes in time > so > user of older versions of maven will be still be > able to find information relevant for them only if they know which version > of maven they are using. That's a different topic which is orthogonal to our discussion. Michal, I am not criticizing your work, quite the opposite actually. I think the breadcrumb is a very nice thing. I'm just saying that we need to find a solution for putting the "doc for" information in a visible place (as it was). Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
> -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, February 21, 2005 2:01 PM > To: 'Maven Developers List' > Subject: RE: svn commit: r154533 - in > maven/maven-1/plugins/trunk/xdoc: > pr oject.properties project.xml src/plugin-resources/site.jsl > xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml > > > Hi Michal, > > > -Original Message- > > From: Maczka Michal [mailto:[EMAIL PROTECTED] > > Sent: lundi 21 février 2005 12:50 > > To: 'Maven Developers List' > > Subject: RE: svn commit: r154533 - in > maven/maven-1/plugins/trunk/xdoc: pr > > oject.properties project.xml src/plugin-resources/site.jsl > xdocs/changes . > > xml xdocs/index.xml xdocs/navigation.xml > > [snip] > > > I personally don't find "doc for" to be that important for > the website > > > > E.g. websites for codehaus projects: > > > > http://drools.codehaus.org/ > > http://picocontainer.codehaus.org/ > > Here are some other web sites: > > http://jakarta.apache.org/cactus > http://cargo.codehaus.org > > :-) > > > > > don't have this piece of information and I don't think that > they are any > > worst then maven generated sites. > > I think they're worse in that regards :-) I personally think > that the doc > for is important. I use it all the time when I view Maven web sites. > It is quite subjective judment :) For example for standard maven plugins what is important is not a version of particular plugin as it is really meaningless for end user but the information with which version of maven this plugin was distributed or more precisly when it was modified for the last time. Say I am still using m1 1.0.0 and version 1.0.2 was already released. I have absolutely no clue what's the version of each and particular plugin which I am currently using (and I am quite close to the source ;) ) and if the information available at the website is at all relevant for me. I really don't care what's the current version of any of those plugins (and there is too many of them to rememebr any versions) - this is something only important for developers not for end users. For plugins it would make more sense to somehow document changes in time so user of older versions of maven will be still be able to find information relevant for them only if they know which version of maven they are using. Other type of situation we have in plexus: http://cvs.plexus.codehaus.org/plexus/ the web site is kept in separate module and the version which is used for it has really nothing to do with any other module - the website has its own lifecycle (much slower the anything else but this is a different story :) ) Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
Hi Michal, > -Original Message- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: lundi 21 février 2005 12:50 > To: 'Maven Developers List' > Subject: RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr > oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . > xml xdocs/index.xml xdocs/navigation.xml [snip] > I personally don't find "doc for" to be that important for the website > > E.g. websites for codehaus projects: > > http://drools.codehaus.org/ > http://picocontainer.codehaus.org/ Here are some other web sites: http://jakarta.apache.org/cactus http://cargo.codehaus.org :-) > > don't have this piece of information and I don't think that they are any > worst then maven generated sites. I think they're worse in that regards :-) I personally think that the doc for is important. I use it all the time when I view Maven web sites. [snip] Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
Hi Michal, Good work! I like a lot the breadCrumb navigation idea:o) I have two remarks on it: - First, links support, eg: Maven (linked)>Maven Plugins(linked)> Maven XDoc Plug-in (NOT linked)> About The websites examples that you have sent provide a link for the last section. - Second point, the website examples dont repeat information: Projects > javatools > javacc jacacc is not present in the navigation bar In your example, http://codehaus.org/~michal/docs/: "About" item is present in the breadcrumb and is highlighted and bold in the navigation bar. Please, feel free to give me any feedback. Cheers, Vincent On Mon, 21 Feb 2005 12:49:53 +0100, Maczka Michal <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Monday, February 21, 2005 12:27 PM > > To: Maven Developers List > > Subject: Re: svn commit: r154533 - in > > maven/maven-1/plugins/trunk/xdoc: > > pr oject.properties project.xml src/plugin-resources/site.jsl > > xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml > > > > > > Why not leave it where it was and put the breadcrumbs some where else, > > like at the top of the body? > > > > eg: http://smh.com.au/articles/2005/02/14/1108229893506.html > > > > > I used http://style.tigris.org/nonav/docs/sampler_inst.html as the reference > as this is where "our" style was born. > Somehow what you are proposing is not matching the spirit of the original > work. > I am not big fan of that layout and look & feel but imo it makes sense to > use it in the way which was previewed by its authors. > But if you have better alternative I definitely won't be against it! > > I personally don't find "doc for" to be that important for the website > > E.g. websites for codehaus projects: > > http://drools.codehaus.org/ > http://picocontainer.codehaus.org/ > > don't have this piece of information and I don't think that they are any > worst then maven generated sites. > Simply site is living longer then particular version of the the project and > it is not happening often > that historical versions of sites are available. So people are naturaly > making an assumption > that the site which they are viewing is always for the latest version of the > project. > And the info what's the latest version can be given somewhere on "welcome" > page (drools provide nice example of that approch) > > Note also that for maven we have praticaly the same website since beta > versions. > > > Michal > > - > 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]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
Hi folks, Maczka Michal wrote on Monday, February 21, 2005 12:50 PM: [snip] > I personally don't find "doc for" to be that important for the website > > E.g. websites for codehaus projects: > > http://drools.codehaus.org/ > http://picocontainer.codehaus.org/ > > don't have this piece of information and I don't think that > they are any worst then maven generated sites. Simply site is > living longer then particular version of the the project and > it is not happening often > that historical versions of sites are available. I just have to correct this slighty. For Pico we *do* offer historical docs online. Not for the complete site though, but for Maven generated stuff: http://picocontainer.codehaus.org/Download [snip] - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Monday, February 21, 2005 12:27 PM > To: Maven Developers List > Subject: Re: svn commit: r154533 - in > maven/maven-1/plugins/trunk/xdoc: > pr oject.properties project.xml src/plugin-resources/site.jsl > xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml > > > Why not leave it where it was and put the breadcrumbs some where else, > like at the top of the body? > > eg: http://smh.com.au/articles/2005/02/14/1108229893506.html > > I used http://style.tigris.org/nonav/docs/sampler_inst.html as the reference as this is where "our" style was born. Somehow what you are proposing is not matching the spirit of the original work. I am not big fan of that layout and look & feel but imo it makes sense to use it in the way which was previewed by its authors. But if you have better alternative I definitely won't be against it! I personally don't find "doc for" to be that important for the website E.g. websites for codehaus projects: http://drools.codehaus.org/ http://picocontainer.codehaus.org/ don't have this piece of information and I don't think that they are any worst then maven generated sites. Simply site is living longer then particular version of the the project and it is not happening often that historical versions of sites are available. So people are naturaly making an assumption that the site which they are viewing is always for the latest version of the project. And the info what's the latest version can be given somewhere on "welcome" page (drools provide nice example of that approch) Note also that for maven we have praticaly the same website since beta versions. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
+1 for me Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
Why not leave it where it was and put the breadcrumbs some where else, like at the top of the body? eg: http://smh.com.au/articles/2005/02/14/1108229893506.html Arnaud HERITIER wrote: >It will be to difficult to understand. In this case why not : >Maven 1.0.2 > Maven Plugins > Maven XDoc Plug-in 1.9-SNAPSHOT > About > >We can add it in the top of the menu ? > >Arnaud > >- >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]
Re: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
It will be to difficult to understand. In this case why not : Maven 1.0.2 > Maven Plugins > Maven XDoc Plug-in 1.9-SNAPSHOT > About We can add it in the top of the menu ? Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes . xml xdocs/index.xml xdocs/navigation.xml
> -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: Monday, February 21, 2005 12:03 PM > To: Maven Developers List > Subject: Re: svn commit: r154533 - in > maven/maven-1/plugins/trunk/xdoc: > pr oject.properties project.xml src/plugin-resources/site.jsl > xdocs/changes. xml xdocs/index.xml xdocs/navigation.xml > > > > > > > > > > - I don't like the date and the release in the bottom left. > > > Can't we put them anywhere else ? > > > > Sure. Just propose where :) > > It's the problem ;-) > > > > > For sites which I am preparing for my daytime work and I > think that also for > > maven website the date when site was last published > > is not very important piece of information and I don't > think that it must be > > very visible as this is something "internal" > > for web site maintainer. > > I agree for the date but we must keep visible the "Doc for" > One possibility is to incorporate "DOC for" into breadcrumps e.g:: Maven > Maven Plugins > Maven XDoc Plug-in 1.9-SNAPSHOT > About But I somehow feel that this is not that good idea. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes. xml xdocs/index.xml xdocs/navigation.xml
> > > > > - I don't like the date and the release in the bottom left. > > Can't we put them anywhere else ? > > Sure. Just propose where :) It's the problem ;-) > > For sites which I am preparing for my daytime work and I think that also for > maven website the date when site was last published > is not very important piece of information and I don't think that it must be > very visible as this is something "internal" > for web site maintainer. I agree for the date but we must keep visible the "Doc for" Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r154533 - in maven/maven-1/plugins/trunk/xdoc: pr oject.properties project.xml src/plugin-resources/site.jsl xdocs/changes. xml xdocs/index.xml xdocs/navigation.xml
> -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 20, 2005 8:29 PM > To: 'Maven Developers List' > Subject: RE: svn commit: r154533 - in > maven/maven-1/plugins/trunk/xdoc: > project.properties project.xml src/plugin-resources/site.jsl > xdocs/changes.xml xdocs/index.xml xdocs/navigation.xml > > > 2 remarks : > > - spaces between crumbs and separators aren't equals (no > spaces between maven and maven plugins) : > > Maven>Maven Plugins> Maven XDoc Plug-in > About > > Is it normal ? No. It looks quite bad. I am using css style "separator" > to separate entries in breadcrumbs. I think that style should define the spacing between entries. I can try to increase and make it look better. Other thing which looks very bad are link in left nav menu. They are way too "dense". This is not something, which I changed but I can try to improve it a bit. > > - I don't like the date and the release in the bottom left. > Can't we put them anywhere else ? Sure. Just propose where :) For sites which I am preparing for my daytime work and I think that also for maven website the date when site was last published is not very important piece of information and I don't think that it must be very visible as this is something "internal" for web site maintainer. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
