Quick in-and-out from a lurker: yesterday as I was learning how to use Five with Plone, I thought to myself, wouldn't it be cool if there were two directives, cmf:installable and cmf:registerContentClass? This is from someone who's totally naive about zcml. Was this evil on my part? Because the debate seems to be about behaviors that are implicitly encouraged.
> Third-party packages which don't define new directives don't need their > own namespaces. If, for instance, Plone adds a "plone:view" directive > which is nothing more than a no-op wrapper around 'browser:view', that > would be a Bad Thing (TM). If, however, they add a 'plone:frobnatz' > directive which does something magical and outside the scope of the Zope > core, and document how to use it when setting up Plone, that would be a > Good Thing, especially if it kept people from changing "site policy" by > customizing software. -- -J. Method _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
