Re: Priority CMF skins vs. Five views?

yuppie wrote:
> Andreas Jung wrote:
> > --On 8. April 2006 12:38:09 +0200 yuppie <y.2006_@xxxxxxxxxxxxxxxx> 
> > wrote:
> > > The lookup order fix is also in Five 1.2.2 and higher, so upgrading from
> > > Five 1.2.1 explains the changed behavior.
> >
> > Waahh...it was _extremely_ convenient to override skin methods this way.
> > Is there any way to achieve that now with Five 1.2.3?

this change broke a bunch of my code too.

> You'll find some discussion about this change in the z3-five list 
> archives. The old behavior was not in sync with the Zope3 behavior and 
> made masked objects inaccessible.

the latter fact was quite useful, allowing for straight forward 
replacement of UI elements without invasive surgery.

> If you don't want to customize traversal the only option I see is using 
> Method Aliases. CMF 2.0 hooks up browser views that way. As I already 
> mentioned in my first reply mapping 'foo' explicitly to the view with 
> '@@foo' will dispatch to the view and not look up the skin method.

which is all well and good if it is a content-type specific template.

otherwhise, for global templates, you have to invade calling templates 
and change paths simply to have an prefix of @@. For systems with tons 
of templates, this can be a PITA.

there seems to be a bigger problem here of having views sensibly 
interact with the existing architecture here. something akin to 
frostbite, a persistent wrapper around viewmapper placed in 
portal_skins, might be a way around this...

then at least, one could be declarative about the precedence of views.

-w