[Grok-dev] Re: RFC: Disable zope.app.rotterdam by default

Martijn Faassen faassen at startifact.com
Tue Mar 27 08:32:48 EDT 2007

Philipp von Weitershausen wrote:
> Philipp von Weitershausen wrote:
>> Martijn Faassen wrote:
>>> Philipp von Weitershausen wrote:
>>>> If Grok should at all come with a standard_macros-style skin, I 
>>>> don't think it should be Rotterdam. With its menus (especially the 
>>>> add menu) it alludes to a ZMI-like or even content management-y 
>>>> thing of which it is neither.
>>>> Per sprint consensus, we should look into making a good-looking but 
>>>> very limited admin UI and forget about the "ZMI" (whatever it is 
>>>> anyway).
>>>> If there are no objections, I will disable at least the 
>>>> zope.app.rotterdam package in grok and grokproject from now on.
>>> +1 from me.
>> Cool. I'll go ahead and do that.
> Sigh, I didn't realize zope.app.rotterdam was actually loaded by 
> zope.app/configure.zcml. Gah.

> I think this definitely should be fixed in Zope proper 
> (zope.app/configure.zcml should be minimal). We might also want to think 
> about doing our own site bootstrapping and forget about 
> zope.app/configure.zcml altogether. There's a lot more in 
> zope.app/configure.zcml that we can skip (which should make [re]starts 
> faster, for example).

> I'll investigate and report back.

Good initiative. This could also become an interesting effort touching 
on some current limitations of Zope 3.

Currently, many Zope 3 packages ship with browser views as well as 
non-browser configuration. The non-browser configuration we can 
typically use just fine, but the browser configuration we cannot (with 
some exceptions as widgets) and would prefer to be disabled completely. 
Whenever the non-browser configure.zcml does an include of 
browser/configure.zcml we have a problem.

We can always provide our own configure.zcml that copies all the ZCML. 
This however is a maintenance nightmare in the long run as the 
underlying Zope 3 code and its registrations can change. This might lead 
us in the direction that was discussed previously - selectively being 
able to turn off some registrations. Still, if you had to spell out all 
page registrations manually, we'd still have a new, different 
maintenance nightmare.

Changing the ZCML registrations in Zope 3 so that configure.zcml doesn't 
include browser/configure.zcml and so on will be quite a bit of an 
effort with risks for backwards compatibility.




More information about the Grok-dev mailing list