Am 03.12.2010, 11:51 Uhr, schrieb Malthe Borch <mborch@gmail.com>:
It's not always possible to control the order of execution. For instance, with z3c.autoinclude, the order of inclusion is somewhat random and although you can to some extend control the order via explicit dependency includes, it's hard to work around 3rd party packages that provide own overrides.
Sounds like a bug in autoinclude to me.
The problem with e.g. request layers as a means to prioritize is that views adapt on (context, request) which makes it unfit for the purpose if you have any views that specialize on the context interface.
I don't understand this sentence. Are you talking about layers as in the Zope 3 skin layer? Otherwise I've nothing but good experiences with views using interface subclassing for specialisation.
Instead, priorities on the configuration level would be an easy solution if you are trying to simply get a component to kick in.
As Marius has already noted, this sounds very much like adding more complexity to solve the apparent existing complexity: swallowing the spider to catch the fly. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226