[Zope-CMF] Implementation identifiers within the REQUEST

[Ausum Studio]

There are a lot of situations where it would be encouraged that skins with a
same name behaves differently depending on what implementation they're being
used at. The main reason for me at this moment is that I can be sure that
the product I'm writing could be installed with a single installer, avoiding
by all means the need to write one for every CMF implementation, existing or
future.

I'll take your idea regarding the use of a special cookie, but in its turn,
who or what (and when) tells Zope to create that cookie, in a reliable way?
One of the workarounds I've used is to rely on the portal object name, or
even (cleaner) on a special property of that same object, but that isn't
suitable for an installer.   (The portal object's meta-type is 'CMF-site',
in both cases).

That's why I turn my eyes to the REQUEST object.


Ausum




----- Original Message -----
From: "alan runyan" <runyaga@runyaga.com>
To: "Ausum Studio" <ausum_studio@hotmail.com>; <zope-cmf@zope.org>
Sent: Friday, October 25, 2002 4:30 PM
Subject: Re: [Zope-CMF] Implementation identifiers within the REQUEST


> there is the skin name...
> maybe we could use that as part of our convention ?
> you can ask the skin tool whats the cookie name.
>
> then you could do skinname.beginswith('plone') or beginswith('cmf')
> or beginswith('mmmanager') and just say if you are going to pick
> a skin name it has to be prefixed by the name of the skin you are using.
>
> mmmanager_customer_skin could be a name of a cookie name.
> that would trigger it to use that skin.
>
> but why are you having to do this?  what is so special about plone?
> that you need to treat things differently?
>
>
> ~runyaga
>
> ----- Original Message -----
> From: "Ausum Studio" <ausum_studio@hotmail.com>
> To: <zope-cmf@zope.org>
> Sent: Friday, October 25, 2002 3:13 PM
> Subject: [Zope-CMF] Implementation identifiers within the REQUEST
>
>
> > As part of my current need to enable a product to work within Plone, my
> > skins need to know what CMF implementation they are being used at. Is it
> > possible that in the future, generally speaking, every implementation
stamp
> > its identifier within the REQUEST object, as an environment variable?
> >
> >
> >
> > Ausum
> >
> > _______________________________________________
> > Zope-CMF maillist  -  Zope-CMF@zope.org
> > http://lists.zope.org/mailman/listinfo/zope-cmf
> >
> > See http://collector.zope.org/CMF for bug reports and feature requests
> >
>