Re: [skin / doxia] escaping issue with menu items
looks like http://jira.codehaus.org/browse/MSITE-333 The problem is certainly in Doxia, not velocity. -Lukas On 10/17/2011 08:55 PM, Robert Scholte wrote: I've just discovered there's an escaping issue with the menu items (both fluido and current maven skin). The ampersand of 'Maven 2 3' is not escaped. The question is: which of the following is responsible for escaping: the doxia model decorator or the velocity template? If it's the latter I'd like to fix it with DOXIA-450[1] The fix itself isn't that hard, but I'd like to confirm it with an IT first, which seems a bit harder. There are no such tests yet. -Robert [1] http://jira.codehaus.org/browse/DOXIA-450 [2] http://velocity.apache.org/tools/devel/standalone.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[skin][fluido] APT vs XDOC
Hi, One problem with using APT for writing docs is that code can only be included within the +-- tags. This is rendeder as two nested elements div class=sourcepre Then you add the prettpyrint class by javascript to all pre elements within code elements. This does not allow for non-prettified pre blocks and makes some pages look pretty weird, e.g.: http://people.apache.org/~olamy/maven/site/license.html The only reasonable alternative i discovered is using XDOC and specifying your own blocks as either: a) pre b) pre class=prettyprint c) pre class=prettyprint linenums This allows for much more flexibility, but requires usage of XDOC format to have code prettification. APT +-- syntax always produces plain pre blocks. Again, the problem is that maven transforms pre class=prettyprint to div class=prettyprintpre (why o why?) but this can also be fixed by javascript. To conclude, I'm migrating most of log4php docs to XDOC format because of this and some other APT limitations. It is a bit more difficult to write, but it is more flexible. If you like the solution I can transfer it to the sandbox. Regards, Ivan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [skin][fluido] APT vs XDOC
I recently did a bit of work with the markdown module, which is a good alternative to APT. I'd be interested in exploring supporting GitHub Flavored Markdown so that you can mark up blocks a bit more: ```java ``` etc. - Brett On 18/10/2011, at 5:28 PM, Ivan Habunek wrote: Hi, One problem with using APT for writing docs is that code can only be included within the +-- tags. This is rendeder as two nested elements div class=sourcepre Then you add the prettpyrint class by javascript to all pre elements within code elements. This does not allow for non-prettified pre blocks and makes some pages look pretty weird, e.g.: http://people.apache.org/~olamy/maven/site/license.html The only reasonable alternative i discovered is using XDOC and specifying your own blocks as either: a) pre b) pre class=prettyprint c) pre class=prettyprint linenums This allows for much more flexibility, but requires usage of XDOC format to have code prettification. APT +-- syntax always produces plain pre blocks. Again, the problem is that maven transforms pre class=prettyprint to div class=prettyprintpre (why o why?) but this can also be fixed by javascript. To conclude, I'm migrating most of log4php docs to XDOC format because of this and some other APT limitations. It is a bit more difficult to write, but it is more flexible. If you like the solution I can transfer it to the sandbox. Regards, Ivan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
help on Unable to update index for central|http://repo1.maven.org/maven2
Hi, I am using Eclipse Helios, when i am trying to open eclipse, in the console i am getting the error (Unable to update index for central| http://repo1.maven.org/maven2) i search for this URL http://repo1.maven.org/maven2 and it is redirected to search.maven.org . please help me how to fix the above issue. where to modify the settings maven version 2.2.1 eclipse version 2.0 Java 1.6 -- Thanks Regards Mallikarjuna Reddy.
Re: [skin][fluido] APT vs XDOC
Hi Ivan! the License page doesn't look good indeed in this way, we have to do something. As you noticed, applying the `prettyprint` class to div class=sourcepre elements, would warrant that feature even to formats where classes cannot be set (due to some limitations of the language). Suggesting our users to port their existing sites to xdoc to have the prettification feature wouldn't be so nice - the maven site itself is written in APT and is a lot of documentation! - so what I suggest is trying to understand when is not appropriate applying the current document modification. Maybe the License page - and few other cases that I don't know - are just exceptions. My 2 cents, Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ 2011/10/18 Ivan Habunek ivan.habu...@gmail.com: Hi, One problem with using APT for writing docs is that code can only be included within the +-- tags. This is rendeder as two nested elements div class=sourcepre Then you add the prettpyrint class by javascript to all pre elements within code elements. This does not allow for non-prettified pre blocks and makes some pages look pretty weird, e.g.: http://people.apache.org/~olamy/maven/site/license.html The only reasonable alternative i discovered is using XDOC and specifying your own blocks as either: a) pre b) pre class=prettyprint c) pre class=prettyprint linenums This allows for much more flexibility, but requires usage of XDOC format to have code prettification. APT +-- syntax always produces plain pre blocks. Again, the problem is that maven transforms pre class=prettyprint to div class=prettyprintpre (why o why?) but this can also be fixed by javascript. To conclude, I'm migrating most of log4php docs to XDOC format because of this and some other APT limitations. It is a bit more difficult to write, but it is more flexible. If you like the solution I can transfer it to the sandbox. Regards, Ivan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Fluido skin Maven site
Hi Barrie!
thanks for sharing your opinions, much more than appreciated!
Please read my replies inline, you wrote a long email I could make confusion :)
All the best, have a nice day!
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
Having larger fonts is making my reading experience better.
I think in general it is an improvement.
Here are some nitpicks (I'm no web site designer) - feel free to
nitpick them too.
I'm no web site designer too ;) that is why we started developing the
new skin on top of Twitter's Bootstrap (twitter.github.com/bootstrap/)
that allows developers playing the role of a designer :P
Jokes a part, color palette, the style, etc etc are all the default
one that comes from Bootstrap.
Users can anyway declare the skin in the site.xml and declare the
overrides/additional classes - as I did in the Maven site PoC - that
is something users are already used to.
I'm not convinced about the drop down menus, I tend to visually ignore
them, but that may just be me.
Ivan is not convinced too, I think/hope is a matter of taste, Olivier,
Christian and I like it, I proposed to keep it because is less work
users should do to have it.. :P
On http://people.apache.org/~simonetripodi/maven/site/plugins/index.html
some links do not have the blue hyperlink underlining but instead have
a yellow halo.
That is because in the APT page, table elements are declared as
{{{/plugins/maven-clean-plugin/} clean}}
That will be rendered as Monospaced, and that's the default Bootstrap's style.
That could be easily modified by overriding the class as described before...
Looking around some more at
http://people.apache.org/~simonetripodi/maven/site/download.html the
yellow halo appears to be the style of apt Monospaced and
must be rendered using a monospaced, typewriter-like font.
yes I understand, the reason is the one before, we can change anyway
the font by overriding, that is something we already did
The halo is drawing my attention to these fields but they aren't
visually that important. Generally used for configuration values and
what you type etc.
default Bootstrap style...
Grey text makes me think of disabled text, and this is the style
applied to numbered lists.
The Installation Instructions section of
http://people.apache.org/~simonetripodi/maven/site/download.html is a
good example of what I'm talking about.
Visually it looks like I should ignore the text (since its grey) with
large amounts of text I should pay attention too (because they are
haloed).
again default Bootstrap style...
One of my gripes with Confluence is its lack of indentation of
heading/subheadings (I've yet to look into whether I can fix that).
The old site http://maven.apache.org/what-is-maven.html does have
indentation even if the sub headings dont look that great.
Whereas the new version
http://people.apache.org/~simonetripodi/maven/site/what-is-maven.html
just has smaller heading styles.
Googling about web design seems to indicate to keep headings to two
levels so maybe this is just my problem again :)
that sounds something we can add (I'll add as soon as I get home), can
you point me to what you found on Google? Just a matter of filling the
gap of my lack of design, thanks in advance!!!
All the best,
Simo
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Fluido skin Maven site
On Wed, Oct 19, 2011 at 3:01 AM, Simone Tripodi
simonetrip...@apache.org wrote:
I'm no web site designer too ;) that is why we started developing the
new skin on top of Twitter's Bootstrap (twitter.github.com/bootstrap/)
http://twitter.github.com/bootstrap/
That page looks good and contains advice - something I can make use of
at my company.
Now we need to work out the peculiarities of the Maven site to why it
doesn't look as good.
I'm not convinced about the drop down menus, I tend to visually ignore
them, but that may just be me.
Ivan is not convinced too, I think/hope is a matter of taste, Olivier,
Christian and I like it, I proposed to keep it because is less work
users should do to have it.. :P
Consider my vote +0 :)
On http://people.apache.org/~simonetripodi/maven/site/plugins/index.html
some links do not have the blue hyperlink underlining but instead have
a yellow halo.
That is because in the APT page, table elements are declared as
{{{/plugins/maven-clean-plugin/} clean}}
That will be rendered as Monospaced, and that's the default Bootstrap's style.
That could be easily modified by overriding the class as described before...
Looking around some more at
http://people.apache.org/~simonetripodi/maven/site/download.html the
yellow halo appears to be the style of apt Monospaced and
must be rendered using a monospaced, typewriter-like font.
yes I understand, the reason is the one before, we can change anyway
the font by overriding, that is something we already did
The halo is drawing my attention to these fields but they aren't
visually that important. Generally used for configuration values and
what you type etc.
default Bootstrap style...
As noted above http://twitter.github.com/bootstrap/ looks good.
The halo is not drawing my attention away like in on our version of the pages.
I think because their text is black and ours are inside lists which
makes the text grey.
One of my gripes with Confluence is its lack of indentation of
heading/subheadings (I've yet to look into whether I can fix that).
The old site http://maven.apache.org/what-is-maven.html does have
indentation even if the sub headings dont look that great.
Whereas the new version
http://people.apache.org/~simonetripodi/maven/site/what-is-maven.html
just has smaller heading styles.
Googling about web design seems to indicate to keep headings to two
levels so maybe this is just my problem again :)
that sounds something we can add (I'll add as soon as I get home), can
you point me to what you found on Google? Just a matter of filling the
gap of my lack of design, thanks in advance!!!
I think I just googled
http://www.google.com/search?q=website+design+heading+subheading
And browsed to
* http://www.high-forest.co.uk/web-page-headings.php (this page has
indentation of headings and paragraphs - but so few sites I was
looking at for examples do)
* http://www.kerryr.net/webwriting/techniques_headings.htm
* http://www.vanseodesign.com/web-design/headlines-subheadings/
* http://nichcy.org/dissemination/tools/webwriting/headings
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
plugin-testing branches reorg
plugin-testing support for maven 3.0 is available on plugin-testing-mvn-3.x branch [1] for couple of years now, while current trunk still works for maven 2.x only. Any objections I move 2.x support to a branch and make plugin-testing-mvn-3.x the new trunk? I plan to propose plugin-testing 2.0 release in near future and branches reorganization seems like a logical preparation steps for this. [1] https://svn.apache.org/repos/asf/maven/plugin-testing/branches/plugin-testing-mvn-3.x/ -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
