> Betreff: [Zope3-dev] Re: AW: Re: The elevator speech for Zope 3
> Grok *aims* to support reusing bits of it. It hasn't reached
> this goal yet as we focused on making it work first, but has
> been an explicit seocndary goal from the beginning last year.
> We need to do some things to make this possible:
> * Done: Grok's mechanism of scanning for classes and
> instances in modules and issuing some form of configuration
> has been factored out into the martian library.
> * as Philipp mentioned, emit configuration actions instead of
> component registrations directly. This is underway, started
> at the sprint last week by Godefroid Chapelle.
> * split up Grok into separate components that are
> independently reusable, without having to pull in the whole
> of Grok to use this.
> Philipp wanted to start this work but I'm not sure about its status.
> * related to this, Grok turns off some of Zope 3's security
> infrastructure (for content objects, not for views). The Grok
> core should continue doing this for the forseeable future,
> but of course if you want to reuse other bits of Grok
> standalone this shouldn't come along.
> So, this is slowly but surely coming nearer. We want Grok to
> be a unified story for most users, so this is not our
> *primary* goal, but we do want Grok's work to be reusable in
> other Zope 3 projects as well.
Cool, sounds promising
> Zope3-dev mailing list
Zope3-dev mailing list