On Jun 21, 2009, at 1:32 PM, Tres Seaver wrote: ...
Thoughts?
+1. I would also like to be able to break the current zope.app.publication dependencies within Zope2:
- ZPublisher.BaseRequest uses zope.app.publication for the EndRequestEvent class
- Products.Five.compuonent likewise uses it for 'IBeginReqeustEvent', 'IEndRequestEvent', and 'BeforeTraverseEvent'
Can we move those events and their interfaces out into a non-zope.app package?
+1
E.g., the as-yet-notional zope.publication package you mention for phase 3?
Maybe. Or maybe zope.publisher.
Or zope.traversing?
-1. I want to make zope.traversing be less about publishing.
There are dependendencies on zope.app.publisher as well:
- Products.Five.browser.adding uses 'getMenu'.
- Products.Five.browser's configure.zcm uses IMenuItemType, MenuAccessView, and IMenuAccessView.
- Products.Five.form.metaconfigure uses menuItemDirective.
- Produts.Five.viewlet.metaconfigure uses viewmeta.
- Products.Five.fivedirectives uses IBasicResourceInformation.
The first two may be the only real uses of the menu framework you discuss above.
I wouldn't be surprised if others used it too. (ZC might :) Jim -- Jim Fulton Zope Corporation