[Grok-dev] ZTK and zopeapp

Jan-Wijbrand Kolman janwijbrand at gmail.com
Wed Dec 30 15:22:44 EST 2009

Martijn Faassen <faassen at startifact.com> wrote:
> Souheil CHELFOUH wrote:
>> What decision is needed ? What do we need to do ?
> Currently (but this is temporary) we have two version lists we can use:
> the ZTK list (on a branch for now):
> http://svn.zope.org/*checkout*/zopetoolkit/branches/faassen-smaller/ztk.cfg
> the zopeapp list (in a sandbox for now):
> http://svn.zope.org/*checkout*/Sandbox/faassen/zopeapp/trunk/zopeapp.cfg
> Ideally Grok should only use ztk.cfg (by copying it for now, otherwise 
> we'll get breakages and such), and not depend on anything on zopeapp.
> Of course it may be that we discover that certain zope.app packages are 
> really essential to the operation of Grok. One example of this I know 
> about is zope.app.form to support zope.formlib, both currently not 
> considered part of the ZTK. (and these in turn pull in other zope.app. 
> stuff at present, something we need to resolve)

I'm trying to get my head out of holiday-mode here, so I hope I understand 
what is going on here...

To me this really sounds like: Grok is "stuck" with depending on zope.app.* 
packages for the foreseeable future if only for the form widgets that we use. 
Reading your report on zope-dev just now on trying to factor out the widgets 
to zope.formlib, I get the impression Grok 1.1 should not wait for it.

My take on this:

Let Grok 1.1 depend on ztk.cfg *and* the zopeapp.cfg, for the remaining 
zope.app.* dependencies that we have. This could mean 1.1 still pulls in quite 
a lot of zope.app.* code that isn't really used. I can live with that, knowing 
that we did already clean up the grokcore.* family to rather great extend.

It also means, we do not have to invent backwards-compatibility packages just 

My two euro cents.

More information about the Grok-dev mailing list