Re: [Zope3-dev] Re: RFC: Local Component Management Simplification
On Tuesday 07 February 2006 00:31, suresh wrote: No it is not. Explicit is better then implicit. declareSite creates a new site in the sites mapping. We use this pattern for layers and skins already. Can you have site... directives without a corresponding declareSite...? What would that achieve? Probably not. In this case the site name=foo directive would raise an exception saying that no site with name foo exists. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: Local Component Management Simplification
Stephan Richter wrote: On Tuesday 07 February 2006 00:31, suresh wrote: No it is not. Explicit is better then implicit. declareSite creates a new site in the sites mapping. We use this pattern for layers and skins already. Can you have site... directives without a corresponding declareSite...? What would that achieve? Probably not. In this case the site name=foo directive would raise an exception saying that no site with name foo exists. In which case I tend to agree with Dieter that declareSite ... is redundant and ZCML ceremony that we can without! If that pattern is being used elsewhere, may be we can eliminate it everywhere in one refactoring :) Suresh ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: RFC: Local Component Management Simplification
On Tuesday 07 February 2006 07:08, suresh wrote: Probably not. In this case the site name=foo directive would raise an exception saying that no site with name foo exists. In which case I tend to agree with Dieter that declareSite ... is redundant and ZCML ceremony that we can without! If that pattern is being used elsewhere, may be we can eliminate it everywhere in one refactoring :) It is definitely not redundant. It creates a site. We do not want to implicitly create sites. To repeat myself again: EXPLICIT IS BETTER THAN IMPLICIT! Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: Local Component Management Simplification
Stephan Richter wrote: On Friday 03 February 2006 17:23, Dieter Maurer wrote: Stephan Richter wrote at 2006-2-3 12:45 -0500: ... declareSite name=mysite / site name=mysite / !-- normal directives here. -- /site The declareSite looks redundant. I see at the site name='mysite' element that a site with name mysite is declared... No it is not. Explicit is better then implicit. declareSite creates a new site in the sites mapping. We use this pattern for layers and skins already. Can you have site... directives without a corresponding declareSite...? What would that achieve? Suresh ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: Local Component Management Simplification
Stephan Richter wrote: Overall, I agree with Jim that the CA can be extended in the the outlined, but I do like several features of the current way. And the way you interact on the registration level is one of them, though I admit writing different registration objects becomes old quickly, as we figured out this week working on WebDev. Not that I have a lot to contribute to this entire conversation (it all looks good to me), but I do second Stephan's comment about writing different registration objects getting old quickly :) - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com ServerZen Hosting -- http://www.serverzenhosting.net News About The Server -- http://www.serverzen.net ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
