[Zope-CMF] Re: Directory-based skin layers?

[Kapil Thangavelu]

On Thu, 2004-04-15 at 01:13, Tres Seaver wrote:
> Ricardo Newbery wrote:
> > 
> > Hi all,
> > 
> > I'm returning to experimenting with CMF after a bit of detour and am 
> > trying to catch up with all the changes.
> > 
> > Something occurred to me that would be very useful for a site I would 
> > like to convert but the idea seems so obvious that I figured, before I 
> > started burning brain cells on it, I would ask this group for some 
> > feedback in case someone else has already done it (and wouldn't mind 
> > sharing), or in case it shouldn't be done for some reason.
> > 
> > This idea is this.  I would like to enable directory-based skin layers 
> > which would take higher precedence than the layers defined in 
> > portal_skins.  I figure it would probably take some hacking of the 
> > skinning machinery.  I'm not talking about an access rule that would 
> > reset the skin name but rather a mechanism that would acquire any skin 
> > layer folders in the current directory and its parents and prepend them 
> > to the portal_skin layer list.
> > 
> > I haven't researched this yet but I'm guessing that CMF makes a 
> > dictionary from the portal_skin layers in order to overwrite references 
> > to "lower" layer objects with references to "higher" layer objects with 
> > the same id.  I figure it should be possible to hack it so that it can 
> > do the same with the directory-based layers.
> 
> The "normal" process is a search path;  the skins tool looks through the 
> layers in order for a given name.  There is no machanism which computes 
> a fully populated / "flattened" namespace, although a number of 
> proposals have kicked around for caching the results of such searching.
> 

SpeedPack in the collective does this to good effect. it adds cache
information for dv ob resolution.

http://cvs.sourceforge.net/viewcvs.py/collective/SpeedPack/

-kapil