Re: [Zope-CMF] adding 'context' as an alias for 'object' in action expressions
Wichert Akkerman wrote: > Previously Laurence Rowe wrote: >> yuppie wrote: >>> David Glick wrote: Does anyone have an objection to me adding 'context' as an alias for 'object' in the expression context that is built when executing CMF action expressions (in getExprContext in CMFCore/Expression.py)? This would remove one common source of minor confusion for beginning CMF/Plone developers (namely, having to use object in action expressions when you use context everywhere else). >>> -1 >>> >>> "There should be one-- and preferably only one --obvious way to do it." >>> >>> 'context' is deprecated for this kind of expressions, CMF uses 'object' >>> everywhere. Supporting 'object' *and* 'context' or switching from >>> 'object' to 'context' will cause even more confusion. >>> >>> Please see this thread >>> http://mail.zope.org/pipermail/zope-cmf/2005-March/021990.html >>> with this result >>> http://mail.zope.org/pipermail/zope-cmf/2005-March/021999.html >> That thread refers to 'content' rather than 'context'. >> >> Page templates have already made 'context' available as an alternative >> to 'here'. I don't see why 'object' should be treated any differently. >> >> "There should be one-- and preferably only one --obvious way to do it." > > Amen. > > +1 on making 'context' available. +1 as well. I could never understand why page templates used 'here', scripts and views used 'context' (or self.context for views) and expressions used 'object'. We have moved away from 'here' in page templates, and settled on 'context', so why keep the inconsistency in TALES expressions? I get it wrong nearly every time I write one. :) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] adding 'context' as an alias for 'object' in action expressions
Previously Laurence Rowe wrote: > yuppie wrote: > > David Glick wrote: > >> Does anyone have an objection to me adding 'context' as an alias for > >> 'object' in the expression context that is built when executing CMF > >> action expressions (in getExprContext in CMFCore/Expression.py)? This > >> would remove one common source of minor confusion for beginning > >> CMF/Plone developers (namely, having to use object in action expressions > >> when you use context everywhere else). > > > > -1 > > > > "There should be one-- and preferably only one --obvious way to do it." > > > > 'context' is deprecated for this kind of expressions, CMF uses 'object' > > everywhere. Supporting 'object' *and* 'context' or switching from > > 'object' to 'context' will cause even more confusion. > > > > Please see this thread > > http://mail.zope.org/pipermail/zope-cmf/2005-March/021990.html > > with this result > > http://mail.zope.org/pipermail/zope-cmf/2005-March/021999.html > > That thread refers to 'content' rather than 'context'. > > Page templates have already made 'context' available as an alternative > to 'here'. I don't see why 'object' should be treated any differently. > > "There should be one-- and preferably only one --obvious way to do it." Amen. +1 on making 'context' available. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] adding 'context' as an alias for 'object' in action expressions
yuppie <[EMAIL PROTECTED]> writes: > David Glick wrote: >> Does anyone have an objection to me adding 'context' as an alias for >> 'object' in the expression context that is built when executing CMF >> action expressions (in getExprContext in CMFCore/Expression.py)? This >> would remove one common source of minor confusion for beginning >> CMF/Plone developers (namely, having to use object in action expressions >> when you use context everywhere else). > > -1 > > "There should be one-- and preferably only one --obvious way to do it." > > 'context' is deprecated for this kind of expressions, CMF uses 'object' > everywhere. Supporting 'object' *and* 'context' or switching from > 'object' to 'context' will cause even more confusion. > > Please see this thread > http://mail.zope.org/pipermail/zope-cmf/2005-March/021990.htmlwith this result > http://mail.zope.org/pipermail/zope-cmf/2005-March/021999.html +1 I'm not really up on the historical considerations, but I'm definitely in favor of "context" and definitely opposed to "object". "object" is too generic, the request is an object after all, everything is an object. "context" reads more like what it is. Ross ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] adding 'context' as an alias for 'object' in action expressions
yuppie wrote: > David Glick wrote: >> Does anyone have an objection to me adding 'context' as an alias for >> 'object' in the expression context that is built when executing CMF >> action expressions (in getExprContext in CMFCore/Expression.py)? This >> would remove one common source of minor confusion for beginning >> CMF/Plone developers (namely, having to use object in action expressions >> when you use context everywhere else). > > -1 > > "There should be one-- and preferably only one --obvious way to do it." > > 'context' is deprecated for this kind of expressions, CMF uses 'object' > everywhere. Supporting 'object' *and* 'context' or switching from > 'object' to 'context' will cause even more confusion. > > Please see this thread > http://mail.zope.org/pipermail/zope-cmf/2005-March/021990.html > with this result > http://mail.zope.org/pipermail/zope-cmf/2005-March/021999.html That thread refers to 'content' rather than 'context'. Page templates have already made 'context' available as an alternative to 'here'. I don't see why 'object' should be treated any differently. "There should be one-- and preferably only one --obvious way to do it." ;-) Laurence ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] CMF Tests: 6 OK
Summary of messages to the cmf-tests list. Period Sat Nov 29 12:00:00 2008 UTC to Sun Nov 30 12:00:00 2008 UTC. There were 6 messages: 6 from CMF Tests. Tests passed OK --- Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.5 : Linux From: CMF Tests Date: Sat Nov 29 20:59:39 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-November/010471.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.5 : Linux From: CMF Tests Date: Sat Nov 29 21:01:09 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-November/010472.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.5 : Linux From: CMF Tests Date: Sat Nov 29 21:02:39 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-November/010473.html Subject: OK : CMF-trunk Zope-2.11 Python-2.4.5 : Linux From: CMF Tests Date: Sat Nov 29 21:04:09 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-November/010474.html Subject: OK : CMF-trunk Zope-trunk Python-2.4.5 : Linux From: CMF Tests Date: Sat Nov 29 21:05:39 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-November/010475.html Subject: OK : CMF-trunk Zope-trunk Python-2.5.2 : Linux From: CMF Tests Date: Sat Nov 29 21:07:09 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-November/010476.html ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
