-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29 Mar 2006, at 17:23, Tres Seaver wrote:
- - 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:
<snip>
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.
I ended up including it in CMFCalendar/configure.zcml:
<!-- Load CMFDefault.skin first, we use the layer named "cmf" it
defines -->
<include package="Products.CMFDefault.skin"/>
<include package=".skin"/>
<include package=".browser"/>
... and it works as expected now. Thanks for the pointers!
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEKtHURAx5nvEhZLIRAjuuAKCGsm/eViWSUBGG6UOlyS7RQrF2WgCfdta/
FrVhb70+I2zDBD1gkY5tte4=
=m9/j
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
