forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bert Van Kets <b...@vankets.com>
Subject Re: skinconf.xml evolution (Re: path trail)
Date Sat, 09 Nov 2002 13:52:30 GMT
At 00:14 10/11/2002 +1100, you wrote:
>On Sat, Nov 09, 2002 at 01:36:04PM +0100, Bert Van Kets wrote:
> > Doing the tests with Forrest I tried to disable the breadcrumbs by making
> > the attributes in the skinconf.xml file empty.  However the path is still
> > displayed.  I suppose this is a WIP.
>
>Actually the skinconf comment is misleading.. all that blanking those
>entries does is prevent the first few breadcumb links from appearing.
>All subdirectory breadcrumbs are shown.
>
>How about we add a <disable-breadcrumbs> entry to skinconf.xml, to match
><disable-search>?
>
>I wish I'd called it <enable-search>.. now the damage is done, we can
>either:
>  - break backwards-compat and reverse the logic
>  - follow the precedent and do a major overhaul sometime in the future
>
>I'd prefer the second option, because sooner or later I'd like to
>incorporate Peter's ideas of how to represent logos.  From
><200211041015.49602.peter@apache.org>:
>
><logo>
>   <name>ThinkTank</name>
>   <role>project</role>
>   <url>http://www.realityforge.org/thinktank</url>
>   <image>skin/images/thinktank-logo.gif</image>
>   <width>88</width>
>   <height>31</height>
></logo>
><logo>
>   <name>RealityForge</name>
>   <role>group</role>
>   <url>http://www.realityforge.org/</url>
>   <image>skin/images/rf.gif</image>
>   <width>88</width>
>   <height>31</height>
></logo>
><logo>
>   <name>Built with Cocoon</name>
>   <role>credit</role>
>   <url>http://xml.apache.org/cocoon/</url>
>   <image>skin/images/built-with-cocoon.gif</image>
>   <width>88</width>
>   <height>31</height>
></logo>
>
>
>I wasn't keen at first, but one excellent use-case for this system turned
>up: that of specifying equivalent images for different backgrounds.
>Currently the Forrest images are designed for a dark background, and look
>odd in the avalon-tigris skin.  With the system above, we could provide
>hints about the image's suitability:
>
><logo>
>   <name>Jakarta Logo</name>
>   <role>group</role>
>   <style>light</style>
>   <url>http://jakarta.apache.org</url>
>   <image>skin/images/jakarta-logo.gif</image>
>   <width>88</width>
>   <height>31</height>
></logo>
><logo>
>   <name>Jakarta Logo</name>
>   <role>group</role>
>   <style>maven-blue</style>
>   <url>http://jakarta.apache.org</url>
>   <image>skin/images/jakarta-logo-blue.gif</image>
>   <width>88</width>
>   <height>31</height>
></logo>
>
>and more generally, store any image metadata which the skins can make use
>of.
>
>This would require a backwards-incompatible break.  So I think we should
>store up all skinconf.xml niggles and fix'em all at once..
>
>
>--Jeff

+1 Bert



> > Bert
> >


Mime
View raw message