Re: [Zope3-dev] RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Marius Gedminas
On Wed, Dec 28, 2005 at 12:26:13PM -0330, Rocky Burt wrote: > Its my personal opinion that anytime a page template requires logic > complicated enough to warrant using a 'python:' expression, that logic > should be re-thought and placed into a view class. I know that some > python: expressions are

Re: [Zope3-dev] RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread kit blake
-1, unless TAL is changed to support booleans and arguments. I agree with Igor: the majority of Python I see in ZPTs is performing tests. The most common use case is coloring table rows, but there are many more, too many for generic view code to cover. When an argument needs to be passed, it's an

[Zope3-dev] Re: RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Florent Guillaume
Rocky Burt wrote: Its my personal opinion that anytime a page template requires logic complicated enough to warrant using a 'python:' expression, that logic should be re-thought and placed into a view class. I know that some python: expressions are fairly simple, but for an HTML designer, *any*

Re: [Zope3-dev] RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Andreas Jung
--On 28. Dezember 2005 17:29:11 +0100 Andreas Jung <[EMAIL PROTECTED]> wrote: --On 28. Dezember 2005 11:04:09 -0500 Jim Fulton <[EMAIL PROTECTED]> wrote: What do you all think? +1 Views make it much easier to keep Python code in Python modules. python expressions should be strongly d

[Zope3-dev] Re: RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Rocky Burt
Andreas Jung wrote: > Another argument against removing python expressions: in Zope 2 > scripters could directly modify and test templates, script etc. (also > using the skins tool). In Z3 you have to restart the server at least for > view classes (but not for templates). Personally I would say i

Re: [Zope3-dev] Re: RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Andreas Jung
--On 29. Dezember 2005 10:08:03 -0330 Rocky Burt <[EMAIL PROTECTED]> wrote: Personally I would say implement logic that allows view classes to be reloadable rather than relying on zpt for exactly this reason if this is indeed something developers need/want (I would love for such a feature).

[Zope3-dev] Re: RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Philipp von Weitershausen
Chris McDonough wrote: > I'm +1 for deprecating python: expressions in the context of views. > But I'm not sure what "deprecate" would mean; I doubt they can go away > entirely given the body of code that exists which uses them. That doesn't mean they can't go away for sure. It would just mean

[Zope3-dev] Re: RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Philipp von Weitershausen
Igor Stroh wrote: > +/-0 > I'd give it a +1 if TAL would support boolean operators :) That's something we could give some thought. It might not be that hard to implement a BooleanExpression for TALES... > Another use case is the passing of arguments > to a method/function/whatever - you might hav

Re: [Zope3-dev] RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Gary Poster
On Dec 28, 2005, at 5:00 PM, Igor Stroh wrote: Rocky Burt wrote: ... Its my personal opinion that anytime a page template requires logic complicated enough to warrant using a 'python:' expression, that logic should be re-thought and placed into a view class. ... First, I have sympathy wi

Re: [Zope3-dev] RFC: abolishing python: expressions in ZPT TALES

2005-12-29 Thread Jeff Shell
-1. I use them very rarely, and expect to use them less with Viewlets now in the picture. But there are still little situations where Python expressions are handy, especially on big-macro templates where there's not a backing view. I'm not advocating programming in page templates, but there are so