Am 01.12.2008 um 16:49 schrieb Tres Seaver:
'context' is the canonical name for the object through which a
script or
templated was acquired (its aq_parent, in fact); 'here' is a
long-deprecated alias for 'context'. 'context' is like the 'self'
binding of a normal Python method.
Action
Hi!
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
Ross Patterson wrote at 2008-11-30 11:25 -0800:
...
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
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
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
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
