I don't have a use case that interesting, but I have made use of
changeSkin with and wished there was a way to easily find out which
skin I've ended up with for debugging and testing purposes. So I'm +1
on the feature idea, don't really care how it's implemented.
On 11/3/05, Florent Guillaume <[E
Laurence Rowe wrote:
The basic use case is to have sections of the site with different skins.
I implement this with a call to changeSkin in
__before_publishing_traverse__ of a folderish type. As these folders may
be nested changeSkin could be called several times during the request.
The corre
The correct resource url in my last post would actually be:
///
eg:
site/portal_css/blueskin/mystyle.css
Laurence
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for
The basic use case is to have sections of the site with different skins.
I implement this with a call to changeSkin in
__before_publishing_traverse__ of a folderish type. As these folders may
be nested changeSkin could be called several times during the request.
The correct skin is that specif
Could you expand a bit on the use case ? I'm not sure I get what you
want do to, do you change skins several times in the middle of the
request ? In what way is this skin needed afterward, at what point ?
What's a "correct" skin ?
Florent
Laurence Rowe wrote:
In Plone ResourceRegistries (1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Limi wrote:
> Can anybody from the CMF team give some guidance to Laurence here?
>
> -- Alexander
>
> On Fri, 28 Oct 2005 06:31:42 -0700, Laurence Rowe <[EMAIL PROTECTED]> wrote:
>
>> In Plone ResourceRegistries (1.1 branch) I need to get
Can anybody from the CMF team give some guidance to Laurence here?
-- Alexander
On Fri, 28 Oct 2005 06:31:42 -0700, Laurence Rowe <[EMAIL PROTECTED]> wrote:
In Plone ResourceRegistries (1.1 branch) I need to get the current skin
name so that the resource (a css or js file) is fetched from the
