[Zope-dev] Dependencies and future of zope 3

Martijn Faassen faassen at startifact.com
Thu Sep 4 06:36:22 EDT 2008


Hi there,

On Wed, Sep 3, 2008 at 7:55 PM, Philipp von Weitershausen
<philipp at weitershausen.de> wrote:
> Benji York wrote:
[snip]
>> Maybe we should create a new namespace package for "browser" code.
>>
>> How about "zope.browser"?
>
> My general sentiment is against creating more structure than we already
> have. Flat is better than nested. IMHO it's perfectly ok to have the Python
> APIs in zope.foo and browser code in zope.app.foo. I think sooner than later
> people won't want to the zope.app.* stuff anyway.

Yeah, I'm leaning towards this approach as well. It's less to move
around. We should not be afraid to move stuff from zope.app.* into
zope.* though if it's clear it's "browser-related" but still not a UI.
Say, absolute URL generation. Otherwise we'll never get rid of some of
the zope.app.* stuff.

Regards,

Martijn


More information about the Zope-Dev mailing list