[Zope-CMF] Re: Differences in CMF Expression contexts
Tres Seaver
tseaver at zope.com
Tue Mar 15 03:51:37 EST 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
yuppie wrote:
| Jens Vagelpohl wrote:
|
|> Suggestion: Standardize on either "object" or "content" in all of
|> them. This implies that URL strings that become part of the
|> expression context and point to the object in question get named
|> accordingly ("object_url"/"content_url"). This standardization
|> would include documentation updates and, where possible, noting the
|> available expression context members on the form that is used to
|> input the TAL expression.
|>
|> Question: Who would like to see standardization,
+1, give an appropriate deprecation period (i.e., add the new names,
note that the old ones are deprecated and will be removed in 1.7 or so).
| +1
|
|> and from those, what name should be chosen?
|
|
| Not sure.
|
| I guess 'object' is more widespread because that name is used in
| Actions.
|
| On the other hand 'object' is a built-in name in python.
True, but it isn't accessible to untrusted code (I think). I would
prefer 'object', as 'content' seems to imply a narrower range of use
than we already see (but either would work, actually).
Tres.
- --
===============================================================
Tres Seaver tseaver at zope.com
Zope Corporation "Zope Dealers" http://www.zope.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCNqIXGqWXf00rNCgRAuMwAJ91RFZaIUATJqfDP5KzDXhoWGewyACePXmJ
McbFAycnKapqpJdGzBoQdPc=
=OSVT
-----END PGP SIGNATURE-----
More information about the Zope-CMF
mailing list