Heres one thats a little better: fixed table colours, got rid of the rounded corners, and replaced the menu dashes with a black diamond (this only works in moz, I used css2. It would be better to fix this one simply by changing the image from 'strich.gif'). The menu fonts look right, and apart from the 'last published'/'related projects' bit below the logos, this is pretty recognizably the jakarta look on all the pages I tried.

I adjusted a few colours in maven_ns4_only.css too - I don't have ns4 handy, but I expect most of this will work except for the 'margin' stuff.

Both of these suffer from flashing when you roll your mouse over a h3/h4, but I reckon the real problem here is the html maven is generating (IIRC someone reported this as a bug already?) - it should do <a name="xxx"></a>xxx not <a name"xxx">xxx</a> for anchors.

NB I can't /quite/ do all this by setting properties for the xdoc plugin, there's points where I need to add in extra style info. I think the plugin could be patched, though, to support a few extra properties, and it would work. Theres no way I could get away with just css changes for the forrest look though (too many extra little images are being inserted, for the rounded tabs).

-Baz

Brian Ewins wrote:
Hacked maven.css attached, looks a bit more 'jakarta-esque'. I just tried it on a project I had lying around, so I havent exercised all of the styles. When we're developing stylesheets, we usually have a 'style guide' page which uses all of the styles - is there a page like that for the tigris/maven stuff? If there is one, I'll finish this stylesheet properly.

Whats still wrong:
- looking at this in Moz, it seems the 'medium' font size I went for[1] is slightly too small. Looking at it in IE6, it looks too big. Plus ca change....
- the dash and indentation of the navbar is wrong. I couldn't see where this dash was being added or I'd have replaced it with a &middot; (a bit closer to whats on jakarta) using insert-before. Anyone know whats going on?
- if you don't have an image in the top right, the link is appearing in /white/. I didn't spot where this was being done (searched for #fff in tigris.css)
- I didn't bother removing the rounded corners on h3/h4 yet; those boxes are a little too large as well.
- the navbar is wider than it is on jakarta.

Anyway, a starting point for playing...

-Baz
[1] the text on jakarta is /un/styled, but I don't know how to remove styling in a cascade; some properties (like font-family) have undefined defaults so I can't just reset them all. Normally I'd use icky XXpx sizes in order to make things look identical on all browsers (crap but necessary; theres a Zeldman column on this) but I went with 'medium' since tigris uses 'small' for all its fonts and I didn't want jarring differences in any styles I missed.

Jason van Zyl wrote:

On Sun, 2003-01-26 at 05:29, Glen Stampoultzis wrote:

What about the possibility of starting a bit smaller and unifying the Jakarta skin?

Centipede (which Poi uses) lets you easily switch skins. I imagine altering the skin in Maven wouldn't necessarily be that hard. Altering the jakarta-site stuff shouldn't be too hard either.


No it wouldn't. If someone wanted to go about creating a set of
stylesheets that were to be used as a skin they might do this:

Unify the use of the same set of stylesheets across the board for
reports. This would involve using the:
pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.xdoc.stylesheets')

syntax to nab a specified directory of stylesheets from the xdoc plugin.
I believe the only two plugins that need aligning are the JXR plugin and
the JavaDoc plugin. They currently have their own CSS property.

So we point at a directory where the stylesheets are contained. Within
the directory, along with the stylesheets could be little snippets of
XML that could be <j:import/>'d into the JSL transformation so the
stylesheets would be applied correctly. For the style we currently use
cascades a maven specific, stylesheet over the tigris one, and there are
instructions for print versions. So whatever is specific to a set of
stylesheets and their use would be in this little snippet of XML that
gets transferred into every document transformed by JSL.

I don't think this would take too long at all if someone wants to give
it a bash.


The best be would be for someone to come up with a skin that most people can agree on and put it to a vote. Not an easy task but worth a shot.

Regards,

Glen Stampoultzis


At 03:21 PM 25/01/2003 +1100, you wrote:

On Fri, Jan 24, 2003 at 10:05:54AM -0500, Kurt Schrader wrote:

On Fri, 24 Jan 2003, Henri Yandell wrote:


This is fine. The problem for Jakarta is that the Maven generated

websites

do not fit the existing L&F. Downloads, sibling projects, general

info are

all missing or setup in different ways.

The problem for Jakarta is that there is no existing look and feel.
Compare:
http://jakarta.apache.org/
http://jakarta.apache.org/turbine/
http://jakarta.apache.org/poi/


If all of Jakarta were to be mandated to be built in the same way etc,
Forrest would be the way to go.

That seems kind of arbitrary to me. The current Maven document generator
produces a website that has a consistent look and feel, as well as a
standard way of organizing the important project information. On every
Maven generated site, for instance, I always know exactly where to go to
get to the CVS repo information. Until Forrest has at least reached that
point, I don't see why we would want to use it.

Aint gonna happen..

When Forrest started a year ago, the goal was to create really
impressive, integrated, consistent-L&F, better-than-Sourceforge project
'portals', through which xml.apache.org projects could be managed, and
real-time info (eg mailing-list stats) obtained. Gump was to be central
(hence the name 'Forrest').

Forrest evolved at snail-pace for 7 months. I tried to use it, flamed
the project in a blog[1], then got on board and started to help. Since
then we've completely reoriented the project. Focus is on single-project
users, not xml.apache.org. Low 'startup cost' is paramount. Need to
generate docs for a project? 1) Type 'forrest seed' to generate a
skeleton site, 2) edit the XML content, 3) type 'forrest site' to render.
The goal is to combine the power of Cocoon with the simplicity and
usability of Anakia. No grand vision, just a tool that does one thing
(XML -> websites) well. 0.3 release coming soon :)


--Jeff

[1] http://www.webweavertech.com/jefft/weblog/archives/000027.html



-Kurt

--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

------------------------------------------------------------------------



body {
background: #fff;
color: #000;
}

.h3 {
margin-left: 3em;
}

.app h3 {
color: #fff;
background-color: #525D76;
font-family: arial,helvetica,sanserif;
margin-left: -3em;
}


.app h3 a {
font-size: medium;
}

.app h4 {
color: #fff;
background-color: #828DA6;
font-family: arial,helvetica,sanserif;
}

.app h4 a {
font-size: medium;
}

.a td { background: #ddd;
color: #000;
}

.b td { background: #efefef;
color: #000;
}

.app th {
background-color: #bbb;
color: #fff;
}

div#banner {
border-top: none;
border-bottom: 1px solid #003;
}

#banner, #banner td { background: #fff;
color: #000;
}

#leftcol {
background: #fff;
color: #000;
border-right: none;
border-bottom: none;
border-top: none;
}

#navcolumn {
background: #fff;
color: #000;
border-right: none;
border-bottom: none;
border-top: none;
}

#breadcrumbs {
background-color: #fff;
color: #000;
border-top: none;
border-bottom: none;
}

#source {
background-color: #fff;
color: #000;
border-right: 1px solid #888; border-left: 1px solid #888; border-top: 1px solid #888; border-bottom: 1px solid #888; margin-right: 7px;
margin-left: 7px;
margin-top: 1em;
}

#source pre {
margin-right: 7px;
margin-left: 7px;
}

a:link, #breadcrumbs a:visited, #navcolumn a:visited, .app a:visited, .tasknav a:visited {
color: #525D76;
}

a:active, a:hover, #leftcol a:active, #leftcol a:hover {
color: #525D76 !important;
}

a:link.selfref, a:visited.selfref {
color: #525D76 !important;
}



h3, h4 {
margin-top: 1em;
margin-bottom: 0;
}

.tabs th {
background-color: #fff;
color: #000;
}

#navcolumn div strong {
font-size: medium;
font-family: times new roman, times, serif;
}

#navcolumn div a {
font-size: medium;
font-family: times new roman, times, serif;
text-decoration: underline;
}


------------------------------------------------------------------------

--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

body {
 background: #fff;
 color: #000;
 }

.h3 {
 margin-left: 3em;
 }

.app h3 {
 color: #fff;
 background-color: #525D76;
 font-family: arial,helvetica,sanserif;
 margin-left: -3em;
 }


.app h3 a {
 font-size: medium;
 }

.h4 {
 margin-left: 3em;
 }

.app h4 {
 color: #fff;
 background-color: #828DA6;
 font-family: arial,helvetica,sanserif;
 margin-left: -3em;
 }

.app h4 a {
 font-size: medium;
 }

.a td { 
 background: #a0ddf0;
 color: #000;
 }

.b td { 
 background: #a0ddf0;
 color: #000;
 }

.app th {
 background-color: #039acc;
 color: #fff;
 }

div#banner {
 border-top: none;
 border-bottom: 1px solid #003;
 }

#banner, #banner td { 
 background: #fff;
 color: #000;
 }

#leftcol {
 background: #fff;
 color: #000;
 border-right: none;
 border-bottom: none;
 border-top: none;
}

#navcolumn {
 background: #fff;
 color: #000;
 border-right: none;
 border-bottom: none;
 border-top: none;
 }

#breadcrumbs {
 background-color: #fff;
 color: #000;
 border-top: none;
 border-bottom: none;
 }

#source {
 background-color: #fff;
 color: #000;
 border-right: 1px solid #888; 
 border-left: 1px solid #888; 
 border-top: 1px solid #888; 
 border-bottom: 1px solid #888; 
 margin-right: 7px;
 margin-left: 7px;
 margin-top: 1em;
 }

#source pre {
 margin-right: 7px;
 margin-left: 7px;
 }

a:link, #breadcrumbs a:visited, #navcolumn a:visited, .app a:visited, .tasknav a:visited {
 color: #525D76;
 }

a:active, a:hover, #leftcol a:active, #leftcol a:hover {
 color: #525D76 !important;
 }

a:link.selfref, a:visited.selfref {
 color: #525D76 !important;
 }



h3, h4 {
 margin-top: 1em;
 margin-bottom: 0;
 }

.tabs th {
 background-color: #fff;
 color: #000;
 }

#navcolumn div strong {
 font-size: medium;
 font-family: serif;
 color: #000;
 }

#navcolumn div a {
 font-size: medium;
 font-family: serif;
 text-decoration: underline;
 }

.app h3, .app h4, .app th, .tabs td, .tabs th, .functnbar {
 background-image: none;
 background-repeat: no-repeat;
 }

/* FIXME: should just use a different image,css2 broken in IE */
#navcolumn div div:before, body.docs #toc li li:before  {
 content: "\2666\A0"
 }
#navcolumn div div, body.docs #toc li li  {
 background-image: none;
 }

#navcolumn div div {
 margin-left: 1em;
 }

body {
 background: #fff;
 color: #000;
 }

a:active, a:hover, #leftcol a:active, #leftcol a:hover {
 color: #525D76;
 }

#leftcol a:link, #leftcol a:visited {
 color: #525D76;
 }

.a td { 
 background: #a0ddf0;
 color: #000;
 }

.b td { 
 background: #a0ddf0;
 color: #000;
 }

body .app th {
 background-color: #039acc;
 color: #fff;
 }

#navcolumn div strong {
 background: #fff;
 color: #555;
 }

#banner, #banner td { 
 background: #fff;
 color: #000;
 }

/* selectors below added, may not work on ns4. */

#navcolumn div strong {
 font-size: medium;
 font-family: serif;
 }

#navcolumn div a {
 font-size: medium;
 font-family: serif;
 text-decoration: underline;
 }	

.h3 {
 margin-left: 3em;
 }

.app h3 {
 color: #fff;
 background-color: #525D76;
 font-family: arial,helvetica,sanserif;
 margin-left: -3em;
 }


.app h3 a {
 font-size: medium;
 }

.h4 {
 margin-left: 3em;
 }

.app h4 {
 color: #fff;
 background-color: #828DA6;
 font-family: arial,helvetica,sanserif;
 margin-left: -3em;
 }

.app h4 a {
 font-size: medium;
 }

.a td { 
 background: #a0ddf0;
 color: #000;
 }
--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to