On Dec 17, 2007, at 10:07 AM, Janko Hauser wrote:
This baffles me somewhat. At the moment I see skins/layers as the
only mechanism to let developers using an application to customize
it, possibly more than once in the same instance. I find them not
optimal, because they only allow customizing on the outer most
level. But overrides is a failure as I understand it.
How are overrides a failure?
Skins, after all do nothing but override views.
So what should be used or invented instead?
I use overrides.
As a usecase take a forum application which should be installed more
than once in an instance but needs different layouts and also
different subset of functionality.
I don't have this use case. I wonder how many people do.
We tend to think up complex use cases and then make the zope framework
more complicated to deal with them. Sometimes these are legitimate
use cases, but they are rarely common cases and their solutions should
generally not be inflicted on the masses.
WRT this use case, I strongly suspect it would be simpler and easier
to support defining multiple configurations in ZCML and a mechanism to
specify different configurations for different sites within an
instance. In fact, I think Stephan Richter added this a while ago.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -