Chris McDonough wrote:
>> Maybe there's some potential to create a set of core ZCML registration 
>> handlers
>> for utility, adapter, subscriber, and interace that are not actually part of
>> BFG, but on which BFG and other non-Zope apps could depend.  I suspect this 
>> is
>> the only realistic way to go forward: I don't think it's reasonable to tell 
>> the
>> people who have Zope apps in production which use these declarations that 
>> they
>> won't be able to use untrusted code or permission declarations, or the global
>> registry.
> 
> In that spirit, here is the first cut at some documentation for a package I'm
> now working on.  Comments appreciated...

That package is now done...

http://static.repoze.org/zcmldocs

and

http://pypi.python.org/pypi/repoze.zcml/0.1

I've adjusted the trunk of bfg and the trunk of chameleon.zpt to use ZCML
declaration implementations from this rather than using the "stock"
implementations from zope.component.  We will thus wind up shedding these
dependencies in the next release of BFG:

zope.security
zope.location
zope.publisher
zope.traversing

We can't shed the i18n-related packages as chameleon still legitimately depends
on them.

- C

_______________________________________________
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Reply via email to