forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <d...@brondsema.net>
Subject Re: Future of skincon.xml
Date Mon, 02 Aug 2004 12:50:05 GMT
On Mon, 2 Aug 2004, thorsten wrote:

> Ross Gardler wrote:
> > thorsten wrote:
> >> I reckon we should introduce a cssconfig.xml/cssconfig-v01.dtd and use
> >> something like this:
> >> <css-elements>
> >>  <css name="menu" visible="false" position="default">
> >>   <color
> >>  </css>
> >> </css-elements>
> >
> >
> > I'm not sure about a separate config file, I feel it belongs in
> > skinconf.xml and there is already a mechanism in there for managing the
> > CSS files.
> >
>
> Yes, but I do not really like it! I think to add single elements to the
> skinconfig.xml will end up in an overkill of the file. Imaging I want
> all css be overriden, I will end up developing them and copy'n paste
> them to skinconfig! That is not *copyless*!

Are you familiar with FOR-144 and the thread leading up to it?


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org

Mime
View raw message