[Zope3-dev] Re: Moving more stuff to zope.products

[Jim Fulton]

Philipp von Weitershausen wrote:
> Philipp von Weitershausen wrote:
> 
>> Hi there,
>>
>> in the currently ongoing process of reorganizing Zope3's package 
>> structure and gutting out zope.app, I think the main packages that 
>> have yet to be moved are:
>>
>> - zope.app.workflow
>> - zope.app.content
> 
> 
> I have started moving zope.app.content to zope.products.content and 
> zope.products.codecontent, respectively in a branch, 
> 'philikon-movecontent-branch'. Here's a small status report:
> 
>   - zope.app.content is a simple module now containg the ContentType
>     machinery

cool

>   - Folder could not be moved out of zope.app, mainly because it is
>     needed widely by the Zope core for its root folder functionality,
>     e.g. in the bootstrap process. It it is now in zope.app.folder,
>     since zope.app.content is a simple module now.

I like the fact that this is now zope.app.folder.

Hm.

(I'm sorry it couldn't be moved out.  This could be fixed, but I think
  that this isn't important enough now.)

...

> Comments are appreciated, as well as help chasing down the last test 
> failures and fixing the modulealias.

As I mentioend earlier, I don't want zope.products.content and
zope.products.codecontent.  Please split these into top-level packages
in zope.products:

   zope.products.zptpage,
   zope.products.dtmlpage,
   zope.products,sqlscript,
   zope.products,file,
   zope.products.i18nfile
   zope.products,image,
   zope.products.i18nimage

but ,,,,

Before we have you do much more work, I think it would be
a good idea to step back and work out the new treee as we did for
namegeddon.

I suggest doing this on a wiki page.

I suggest we coordinate this with the switch to ZODB 3 so that we can
have a conversion script that adjusts class references in pickles.

Finally, I'd like to consider a simplification of the source layout as follows.
I'd like us to reorganize whatever is left in app so that app is much flatter.
Further, the division of application, view, and interface code should happen
within the subfolders of app, rather than in app. So, for example, we'd get rid of
app.interfaces and app.browser.  The folder package, zope.app.folder would
have interfaces.py, and browser.py.

The problem with this is that it largely undoes the separation of presentation
code we created in namegeddon.  I have to admit, though, that this separation
wasn't very popular, except, possibly with the people it was done for. :)

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org