forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <>
Subject partial skin overriding
Date Sat, 27 Dec 2003 18:05:24 GMT

There was some discussion of this a week or so ago.  Summary, IIRC: partial skin
overriding is bad because things break when stylesheets change.  The 'common'
directory is required as a peer to any custom skins (solvable by using a Catalog
Entity Resolver or packaging the custom skin and fetching it into the main
forrest skin dir).

I still agree that in most cases partially overriding a skin is bad.  But here
is a good use-case:

Since many skins now use CSS (a *good* thing), it would be ideal for users to
modify just the css file(s) to tweak the appearance of a standard skin.  

Could this be solved with a matcher that looked in the project's skin directory
for the requested file and if not found, then looked in the standard skin
directory?  This would still prevent a custom skin from overriding stylesheets
because the xsl:import would only look for files relative to itself.

Dave Brondsema - personal - programming - student org 

View raw message