[Zope-dev] zope.app.publication dependencies (volunteersneeded!)

Stephan Richter srichter at cosmos.phy.tufts.edu
Tue May 19 09:42:19 EDT 2009

On Tuesday 19 May 2009, Martijn Faassen wrote:
> * the registration of the zope:view and zope:resource directives. I'm
> not sure what these are for, as we have browser:view and
> browser:resource. Perhaps these can be safely lifted into
> zope.app.publisher, which defines the browser:* varieties

Yes. The zope:* variants are used to allow registration of non-browser views 
and resources. I am pretty sure it is still used, so we should keep them, but 
the move to zope.app.publisher makes sense.

> * the code in zope.app.component vocabularies. This is support code to
> create vocabularies for utilities. It depends on zope.interface,
> zope.component and zope.schema, and zope.app.interface.
> It might be sensible to move this vocabulary stuff (along with the one
> in zope.app.interface that we depend on) into a package called
> zope.componentvocabulary. We can jettison zope.app.component then.
> zope.componentvocabulary would depend on zope.schema, zope.component,
> zope.interface and zope.security only.
> We can then make zope.app.publisher depend on zope.componentvocabulary
> and lose the zope.formlib dependency, along with the zope.app.security
> dependency.

I agree.

Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"

More information about the Zope-Dev mailing list