[Zope3-dev] attr name space (was: RFC: abolishing python: expressions)

2005-12-30 Thread Alexander Limi
On Thu, 29 Dec 2005 15:49:46 +0100, Philipp von Weitershausen [EMAIL PROTECTED] wrote: I think it would be quite possible to do explicit key or attribute lookup with TALES, e.g.: foo/attr:bar (for foo.bar) foo/key:bar (for foo['bar']) foo/item:1(for foo[1]) This reminds me of

Re: [Zope3-dev] attr name space (was: RFC: abolishing python: expressions)

2005-12-30 Thread Andreas Jung
--On 30. Dezember 2005 08:22:18 -0700 Jeff Shell [EMAIL PROTECTED] wrote: The same would probably be relevant for tal:defines, something like: div define:mammals=here/getMammals define:fish=here/getFish / - It looks nice! :) That's relative. It would call it: syntactic

Re: [Zope3-dev] attr name space (was: RFC: abolishing python: expressions)

2005-12-30 Thread Fred Drake
On 12/30/05, Jeff Shell [EMAIL PROTECTED] wrote: - the TAL namespace had a limited and proper list of attributes. A very limited set of names that could be (theoretically) validated with standard XML tools. This should probably remain a goal, but I don't think it's as big a deal as the

Re: [Zope3-dev] attr name space (was: RFC: abolishing python: expressions)

2005-12-30 Thread Dieter Maurer
Alexander Limi wrote at 2005-12-30 11:22 +0100: ... One of the ugliest and most error-prone parts of TAL is its handling of multiple attributes: a tal:attributes=href some/url; title some/title; / Why is this more ugly or error prone as your proposal? ... This provides

Re: [Zope3-dev] attr name space (was: RFC: abolishing python: expressions)

2005-12-30 Thread Marius Gedminas
On Fri, Dec 30, 2005 at 11:22:56AM +0100, Alexander Limi wrote: This reminds me of a thing Steve Alexander and myself talked about when working together on a project using Zope 3 a while back: One of the ugliest and most error-prone parts of TAL is its handling of multiple attributes: