Benji York wrote:
Gary Poster wrote:
What if we still deprecated browser:layer but kept a redefined
version of browser:skin? Then your zcml--
interface
interface=.interfaces.ShanghaiSkin
type=zope.publisher.interfaces.browser.IBrowserSkinType
/
Fred Drake wrote:
I would prefer not. We've used resourceDirectory to support things
like webcams. The image(s) uploaded by the cams might not always be
there, but the containing path is. It's nice not having Zope start
Good point.
If it was sugar for a set of resource directives, this
On Fri, Feb 17, 2006 at 01:17:22AM +0100, Philipp von Weitershausen wrote:
Either way, resource definitions are not quite the goal of my proposal
so I'll leave it out of there. Perhaps Paul or whoever has the need for
it would like to implement a resourcesFromDirectory directive...
I'll see if
On 2/16/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
Either way, resource definitions are not quite the goal of my proposal
so I'll leave it out of there. Perhaps Paul or whoever has the need for
it would like to implement a resourcesFromDirectory directive...
Right; this should
Dear Tonico,
thanks for your input.
In CMF things are very easy to understand, because a layer is simply a
folder. I can explain that in five minutes to a template programmer.
Why does the template programmer need to know about layers?
Maybe this sounds a bit NAIVE, but would it be possible
Philipp von Weitershausen wrote:
In CMF things are very easy to understand, because a layer is simply a
folder. I can explain that in five minutes to a template programmer.
Why does the template programmer need to know about layers?
Because in CMF, if you want to customize or create a skin,
Tonico Strasser wrote:
In CMF things are very easy to understand, because a layer is simply a
folder. I can explain that in five minutes to a template programmer.
Why does the template programmer need to know about layers?
Because in CMF, if you want to customize or create a skin, you need
Tonico Strasser wrote:
Philipp von Weitershausen wrote:
[snip]
See, now I even explained this to a template programmer, though I
don't think he'd care.
Maybe I mean something different. I just want a folder in which I can
drop all the files I want to customize (I love to customize),
On Wed, Feb 15, 2006 at 03:39:02PM +0100, Philipp von Weitershausen wrote:
Maybe I mean something different. I just want a folder in which I can
drop all the files I want to customize (I love to customize), without
registering something.
That's not how it works in Zope 3, at least not
Paul Winkler wrote:
I have to explicitly register every one of my skin's 35 resources?
If the 35 resources (files) are in the same directory you can use the
resource directory ZCML directive. Or am I missing something?
--
Benji York
Senior Software Engineer
Zope Corporation
On Wed, Feb 15, 2006 at 12:44:36PM -0500, Benji York wrote:
Paul Winkler wrote:
I have to explicitly register every one of my skin's 35 resources?
If the 35 resources (files) are in the same directory you can use the
resource directory ZCML directive. Or am I missing something?
Only that
On 2/15/06, Paul Winkler [EMAIL PROTECTED] wrote:
Only that I have the same question Martijn does:
Can I then override one of those resources and keep the other 34?
Perhaps the resourceDirectory directive should just be sugar for a set
of resource directives, one for each file in the directory?
On 2/15/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
I find Zope 3's approach much simpler and much easier to explain than
the CMF's approach. In Zope 3 (especially with my proposed changes in
place), a layer is simply a label (read: marker interface) on the
request. When we now look
On 2/15/06, Jeff Shell [EMAIL PROTECTED] wrote:
I would prefer not. We've used resourceDirectory to support things
like webcams. The image(s) uploaded by the cams might not always be
there, but the containing path is. It's nice not having Zope start
Good point.
If it was sugar for a set of
Jeff Shell wrote:
I find Zope 3's approach much simpler and much easier to explain than
the CMF's approach. In Zope 3 (especially with my proposed changes in
place), a layer is simply a label (read: marker interface) on the
request. When we now look up pages and resources (e.g. images), we
15 matches
Mail list logo
