Jim Fulton wrote:
Given that, I still prefer context#dc to context/##dc.
+1, also in preference to /# and the other options I've seen.
Gary
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
Jim Fulton wrote:
Evan Simpson wrote:
Jim Fulton wrote:
IMO, if we take this route, we should think of the notation as
providing an alternate traversal operator. That is, there is
syntax that either modifies or replaces /, so of the examples
above, only:
context/*dc/title
In that case, I'd be
Jim Fulton wrote:
I've posted two proposals:
http://dev.zope.org/Zope3/TALESPathExpressionAdapters
Proposes a mechanism for easily using adapters in TALES expressions.
http://dev.zope.org/Zope3/ZPTVariableNamespaces
proposes a mechanism for qualifying names defined in TAL and used in
TALES
On Friday 21 May 2004 09:07, Jim Fulton wrote:
So far the cast syntax seems to be the most popular:
(adaptername)ob (dc)context/title
Why don't we use adaptername(ob)? Then it looks exactely like in Python! Less
to memorize.
Regards,
Stephan
--
Stephan Richter
CBU Physics Chemistry
On Friday 21 May 2004 09:07, Jim Fulton wrote:
tal:define=adapter dc modules/zope.app.dublincore/IZopeDublinCore
This looks very nice to me.
Regards,
Stephan
--
Stephan Richter
CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and
Stephan Richter wrote:
On Friday 21 May 2004 09:07, Jim Fulton wrote:
So far the cast syntax seems to be the most popular:
(adaptername)ob (dc)context/title
Why don't we use adaptername(ob)? Then it looks exactely like in Python! Less
to memorize.
Because that would be the top of a
