Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
Baiju M wrote: On 10/9/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > Then, can we move up zope.app.component.interfaces.ISite to > zope.component.interfaces.ISite or any other place? Perhaps zope.site. I just tried this in my checkout, it only took 30 minutes. That's nice. Note that zope.site should perhaps also contain more stuff, such as the whole sitemanager-in-a-thread-local stuff, and possibly a local site manager implementation that can be used in Zope 2 and 3 (much of what LocalSiteManager does currently). So, in the end, zope.site would more or less contain what zope.app.component currently contains. The move might not be worth it. All tests passed except src/zope/app/component/tests/test_registration.py which make use src/zope/app/component/tests/gen3.fs How can I regenerate this file ? Dunno. Perhaps you should write another evolvement script? The patch against current trunk is here: http://zissue.berlios.de/z3/zope-site.diff Now I wonder whether I should go for a formal proposal. Any chance to get +1 Dunno, try it :). Though I would suggest bringing up this whole issue on [EMAIL PROTECTED] We oughta discuss the whole package-dependency-and-move-around issue sooner or later anyways. Jim recently suggested that perhaps we make zope.app a namespace package in which case zope.app.component could perhaps be distributed individually. Then zope.location would only depend on zope.app.component, not all of zope.app. This is required for complete eggification of Zope 3. Not really. It would just make things easier to reuse. Zope 3 could easily be eggified as it is, zope.app would probably just have to be a big monolithic egg. For smaller and more reusable eggs, it looks like we have the following two scenarios: a) we continue to move reusable stuff out of zope.app OR b) we dig through zope.app and make the reusable stuff less dependent on the rest of zope.app. Then, those things can become their own eggs, after having made zope.app a namespace package. Philipp ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
On 10/9/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > Then, can we move up zope.app.component.interfaces.ISite to > zope.component.interfaces.ISite or any other place? Perhaps zope.site. I just tried this in my checkout, it only took 30 minutes. All tests passed except src/zope/app/component/tests/test_registration.py which make use src/zope/app/component/tests/gen3.fs How can I regenerate this file ? The patch against current trunk is here: http://zissue.berlios.de/z3/zope-site.diff Now I wonder whether I should go for a formal proposal. Any chance to get +1 Jim recently suggested that perhaps we make zope.app a namespace package in which case zope.app.component could perhaps be distributed individually. Then zope.location would only depend on zope.app.component, not all of zope.app. This is required for complete eggification of Zope 3. Regards, Baiju M ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
Baiju M wrote: On 9/28/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Lennart Regebro wrote: > On 9/28/06, Tom Dossis <[EMAIL PROTECTED]> wrote: >> I've noticed the following changes in the zope 3.3 ZMI >> >> Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). >> Zope 3.2 - Can only add utilities to a Site Mgmt Folder > > You can see it like this: The difference between a folder and a site > has lessened. > Folders are no more or less content space than sites. Any thing you > can browse too is content. ;-) No, Lennart, this is wrong. A site is still very much a site (ISite determines "site-ness", nothing else). They're still regular folders that contain content. The only difference between sites and folders is that sites are a palce where you can make local component registrations. This is still the same in Zope 3.3, only the constraint *where* these components live has changed. So, the concept of 'site' is part of component architecture and not specific to application server? It is specific to the application server. The Component Architecture only knows IComponentRegistry + IComponentLookup = IComponents. Then, can we move up zope.app.component.interfaces.ISite to zope.component.interfaces.ISite or any other place? Perhaps zope.site. Jim recently suggested that perhaps we make zope.app a namespace package in which case zope.app.component could perhaps be distributed individually. Then zope.location would only depend on zope.app.component, not all of zope.app. If we can do like this, the zope.location's dependency on zope.app can be removed. Yes. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
On 9/28/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Lennart Regebro wrote: > On 9/28/06, Tom Dossis <[EMAIL PROTECTED]> wrote: >> I've noticed the following changes in the zope 3.3 ZMI >> >> Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). >> Zope 3.2 - Can only add utilities to a Site Mgmt Folder > > You can see it like this: The difference between a folder and a site > has lessened. > Folders are no more or less content space than sites. Any thing you > can browse too is content. ;-) No, Lennart, this is wrong. A site is still very much a site (ISite determines "site-ness", nothing else). They're still regular folders that contain content. The only difference between sites and folders is that sites are a palce where you can make local component registrations. This is still the same in Zope 3.3, only the constraint *where* these components live has changed. So, the concept of 'site' is part of component architecture and not specific to application server? Then, can we move up zope.app.component.interfaces.ISite to zope.component.interfaces.ISite or any other place? If we can do like this, the zope.location's dependency on zope.app can be removed. We are implementing 'IPhysicallyLocatable' in zope.location.traversing.LocationPhysicallyLocatable And there is 'getNearestSite' site method, which actually get the 'ISite.providedBy' object. Here is the code snip: def getNearestSite(self): """return the nearest site, see IPhysicallyLocatable""" if ISite.providedBy(self.context): return self.context for parent in getParents(self.context): if ISite.providedBy(parent): return parent return self.getRoot() Regards, Baiju M ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
On 9/28/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Lennart Regebro wrote: > On 9/28/06, Tom Dossis <[EMAIL PROTECTED]> wrote: >> I've noticed the following changes in the zope 3.3 ZMI >> >> Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). >> Zope 3.2 - Can only add utilities to a Site Mgmt Folder > > You can see it like this: The difference between a folder and a site > has lessened. > Folders are no more or less content space than sites. Any thing you > can browse too is content. ;-) No, Lennart, this is wrong. A site is still very much a site (ISite determines "site-ness", nothing else). They're still regular folders that contain content. The only difference between sites and folders is that sites are a palce where you can make local component registrations. This is still the same in Zope 3.3, only the constraint *where* these components live has changed. Yes, I realized what he meant after I posted, and hoped nobody would notice my mistake. :-) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
Lennart Regebro wrote: On 9/28/06, Tom Dossis <[EMAIL PROTECTED]> wrote: I've noticed the following changes in the zope 3.3 ZMI Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). Zope 3.2 - Can only add utilities to a Site Mgmt Folder You can see it like this: The difference between a folder and a site has lessened. Folders are no more or less content space than sites. Any thing you can browse too is content. ;-) No, Lennart, this is wrong. A site is still very much a site (ISite determines "site-ness", nothing else). They're still regular folders that contain content. The only difference between sites and folders is that sites are a palce where you can make local component registrations. This is still the same in Zope 3.3, only the constraint *where* these components live has changed. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
On 9/28/06, Tom Dossis <[EMAIL PROTECTED]> wrote: I've noticed the following changes in the zope 3.3 ZMI Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). Zope 3.2 - Can only add utilities to a Site Mgmt Folder You can see it like this: The difference between a folder and a site has lessened. Folders are no more or less content space than sites. Any thing you can browse too is content. ;-) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
Tom Dossis wrote: Philipp von Weitershausen wrote: On behalf of the Zope 3 development team I'm proud to announce the final Zope 3.3.0 release. There were no changes since the 3.3.0 release candidate. I've noticed the following changes in the zope 3.3 ZMI Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). Zope 3.2 - Can only add utilities to a Site Mgmt Folder Zope 3.3 - All Objects have a ZMI Registration Tab Zope 3.2 - Only ILocalUtility? objects have a reg. tab Is this intentional? Yes, because it's much simpler this way. I seem to recall an objective of zope3 was to remove 'tools' from content space? The current situation gives you more flexibility. You can still choose to separate components from content, but you no longer have to. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Zope 3.3.0 - Adding Utilities to Content Space
Philipp von Weitershausen wrote: > On behalf of the Zope 3 development team I'm proud to announce the final > Zope 3.3.0 release. There were no changes since the 3.3.0 release > candidate. > I've noticed the following changes in the zope 3.3 ZMI Zope 3.3 - Can add utilities anywhere, e.g. to Folders (content space). Zope 3.2 - Can only add utilities to a Site Mgmt Folder Zope 3.3 - All Objects have a ZMI Registration Tab Zope 3.2 - Only ILocalUtility? objects have a reg. tab Is this intentional? I seem to recall an objective of zope3 was to remove 'tools' from content space? Thanks -Tom ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
