-----BEGIN PGP SIGNED MESSAGE-----
> Hi Jens!
> Jens Vagelpohl wrote:
>> I'm coming up against the next item, which is "how to correctly refer
>> to a layer defined somewhere else". In CMFCalendar, I need to make
>> sure the skin layers for CMFDefault are also available. There seem to
>> be two routes I could choose:
>> - - define my own cmfcalendar skin and layer. Declare it as a
>> combination of layers cmfcalendar, cmf and default.
>> - - stick my views directly into layer "cmf" and don't worry about
>> defining my own layeer or skin.
> I think the second route is the Right Way to do it with Zope 3 style
> layers. I can't see a need to define an extra layer for CMFCalendar.
I still don't think that products should define the default layer, at
least not in the same ZCML file that is used to get all the "normal"
adapter / view registrations configured.
>> Both lead to errors like this:
>> ConfigurationError: ('Invalid value for', 'layer', "ImportError:
>> Couldn't import cmf, No module named cmf")
> I guess the problem is the order in which Five loads the configure.zcml
> files. But I have no idea what's the recommended way to make sure
> CMFDefault's configure.zcml is loaded first.
%include it into the "dependent" one.
Tres Seaver +1 202-558-7113 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests