[Zope-CMF] centralize skins for multiple cmf sites on same server

[Adrian Hungate]

> Tres Seaver wrote:
> > Just in case it isn't clear:  skins extend acquisition, by making the
> > name lookup machinery search additional folders before propagating "up"
> > from the CMFSite.  You *can* have TTW editing of shared objects;  e.g.,
> > put two CMF sites in a folder, along with a PageTemplate
> > 'foo_template';  both sites will be able to use 'foo_template' ad lib.
> > What you *can't* do this way is override a name
> > (e.g. 'main_template') supplied in the "subsites".
>
> Actually, what if skin layers could be paths rather than just names?
>
> Then you could have a shared ZODB-based layer, which would rock IMHO :-)

In theory, you could add a folder that is not a skinfolder to a skin list -
Would the skins_tool prevent this?

For example, a parent containing skinA, CMFa and CMFb objects, where skinA
is a Zope folder with some skin stuff in it.

If you add skinA to the front of the basic skin in the CMFa and CMFb
skins_tools will the CMF shout this is invalid or will it acquire the
folder?

> If someone can give em a nod or shake of head as to whether this is a good
idea
> or not, I might have a look at implementing something this afternoon...
>
> cheers,
>
> Chris

Adrian...

--
Adrian Hungate
EMail: adrian@haqa.co.uk
Web: http://www.haqa.co.uk