-----BEGIN PGP SIGNED MESSAGE-----
Jens Vagelpohl wrote:
> On 28 Mar 2006, at 21:46, Rob Miller wrote:
>>> assuming that you do actually have a similar "edit.html" browser:page
>>> declared, then maybe the problem is with the cmfcalendar layer not
>>> being included in your current skin?
> Thanks Rob, I think that was the key. CMFDefault declares the cmf skin
> as default. In order to make my cmfcalendar skin the default I edited
> CMFDefault/skin/configure.zcml and removed the browser:defaultSkin
> statement. Then I put one into my CMFCalendar/ skin/configure.zcml.
> There has to be a better way, right? People shouldn't have to edit both
> the CMFDefault and CMFCalendar skin/configure.zcml to pull in the
> CMFCalendar skin. I'm hoping there is a way to make this happen using
> my new CMFCalendar views profile for GenericSetup...
Really, *neither* product should have a 'browser:defaultSkin' directive
in its configure.zcml: that directive belongs only in the user's
site.zcml, or *maybe* in a slug in 'package-includes': it is "pure" policy.
Zope3 doesn't get this right either.
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