> -----Original Message----- > From: Leo Simons [mailto:[EMAIL PROTECTED]] > > > > - color variations (and all other l&f changes) should be > > > part of the original look-and-feel design. Giving > > > programmers free reign to do this spells disaster. > > > It would be best to have the original designer of a > > > look and feel work this out. Very strictly. > > > > :( > > > > Seriously, I don't dig the big blue background. > > that is something we agree on =) While we're at it, I > think the entire header should be smaller. The jakarta > logo is just too big. I'm not volunteering though... > I'm no photoshop biggie.
I a GIMPer myself... > > With > > projects like Batik, we can generate images that fit > > with any background color. > > really? How well does that work? Does it work on bitmaps? As long as the original bitmap supports alpha blending, all is well (i.e. PNG). It's text you have to worry about.... > > The color customization whould be in the project header. > > note that all jakarta subproject logos currently are meant > to work with a white background. The Avalon logo would > probably look terrible against something else (as it has > little color). Yet the maven design falls apart if you make > the header white (doesn't really fit in). We can fiddle with the design until we have something we like. > > > > - the navigation setup we currently have sucks. The > > > one used by turbine right now is slightly better, > > > but only slightly. We need arbitrarily deep levels. > > > The best option is a breadcrumb trail. > > > > Yes and no. The Breadcrumb trail + the Maven approach > > would be ideal. It is easier to get a grip on what > > is available without having to go back to the parent > > level each time. You should at least see all peers. > > I agree. In general, I would not recommend it, but most > of the peer pages on jakarta have a tight enough > relationship that is warranted. Is it true for all > pages, though? Maybe a peer list should dissapear at > a certain depth. This deserves more thought. When you have a group of related sub-projects, it is very much warranted. The maven layout kicks butt to display all sub project info, and allow you to jump from one sub-project to another easily. I don't think we will be going that much deeper than what you see in maven... But at that point it is really beyond the scope of Jakarta guidelines. > > (...) > > > And I have designed several web applications, and also am > well versed > > in site design and color customization. > > Then you will agree that changing of the header color should > also mean changing of the color of all the section headers. > And that, if you change the header to white (as would be > required for some subproject logos), you should change the > section headers to a black background. Which is equivalent to > shouting. Hence I'm scared of "free reign". ?!? Section headers currently match the main header color. So if the main header color becomes black on white, the section headers become black on white. The result is subdued if anything. > > > jakarta.apache.org > avalon > excalibur > > CLI Collection Command Concurrent .... > > > > And the right hand navigation like on the maven site? > > I would probably not have the breadcrumb and peer lists > directly below each other in the current maven layout. This > deserves more thought. > > > > anyone feel like throwing stones at me yet? :) > > > > Sure, but let me get my aim just right.... :P > > You seen braveheart? :) > Oh, yeah (I own it) "I've come to peck a fight" -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
