On Thu, 2002-03-28 at 09:53, Berin Loritsch wrote: > > The only thing I would want to customize are: > > 1) Project Logo > 2) Project color-scheme
No problem :-) > That's it. I really don't think that is too much to ask. The > layout should remain constant without a doubt. We are in agreement then :-) Wow a new era for Avalon and Turbine developers ;-) We did you avalon in part to produce PDFs :-) > > > I'm not trying to stifle anyone's creative urges, I just feel > > that in the matter of project comprehension that it is > > pragmatic to have everything look the same. Some don't agree > > with me but what I'm really trying to avoid is the infinite > > configuration quagmire where everyone adds things to make > > things look the way they like and thus you loose all cross > > project cohesion. > > Everything should definitely feel the same. However, color is > a definite clue that you have changed contexts. By drilling > down a Project's heirarchy, it helps to have a visual clue that > you are not at the same level you used to be. > > Color customization is not just a cosmetic tool, it does help > to understand a project's hierarchy. Logo changes can be missed, > but a different background or header color is hard to ignore. I'm definitely flexible on the color thing. > As a side note, it would be cool if we could include the Jakarta > and project logos as a header in the printed documentation, but > that is a stylesheet change. > > > > > > I just wish I new about Maven a lot earlier--it delivers on > > a lot of > > > promises, and in my book that's golden. > > > > It's been in the works for a long time but really it's only > > been in the last 3-4 weeks that others have worked on it and > > it's taken off primarily because of the interest people have > > in making their develop lives easier. There is definitely an > > interest there because people would rather focus on their > > apps then fart around trying to get a build system to work > > and have it produce useful information. > > Absolutely. > > > So what did you think about the two line navigation approach for > Jakarta Site? I like the idea and I've thought about how to aggregate the content of many projects into an uber site but I haven't done much work on it as I've focused on the project level. But I'm definitely thinking of the aggregation of projects: for documentation and building. > > > I see the line with the sub-projects able to be two lines tall. The > > > first line would be the parent level, and the second line > > would be the > > > current line. That way we can have something like this at the root > > > level: > > > > > > Alexandria Avalon BCEL ... > > > > > > And at the sub-project level, we would be able to have > > something like > > > this: > > > > > > Jakarta| Theory Framework LogKit *Excalibur* Cornerstone > > Phoenix Apps > > > CLI Collections Concurrent .... > > > > > > That way we can easily navigate the site, and drill down quickly to > > > the actual information we need. > > > > > > ---- > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:general-> [EMAIL PROTECTED]> > > > For > > additional commands, > > e-mail: > > > <mailto:[EMAIL PROTECTED]> > > -- > > jvz. > > > > Jason van Zyl > > [EMAIL PROTECTED] > > > http://tambora.zenplex.org > > > -- > 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]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
