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

[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 some boolean or quick-transformation (ensuring a
potential iterator/generator is a list and has length) that needs to
be done out in this phantom land.

As I mentioned above, I really believe that Viewlets and Viewlet
Managers will help with these big complex templates which provide the
look and feel of the front page or the basic template. But I know that
sometimes, when putting those pages together from a designers input on
a tight deadline with multiple browsers to test, the quick math and
other small expressions we can squeeze into those spots have been a
life-saver, even in recent weeks.

On 12/28/05, Rocky Burt <rocky at serverzen.com> wrote:
> Hi all,
>
> Please don't mistake this as a proposal or anything of the sort but I
> was just curious what the rest of the zope3 community thought on this
> particular topic.  (Please forgive me if this topic has been exhaused to
> death already)
>
> 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*
> python: portions are dangerous to touch (and shouldn't be touched by the
> HTML designer).
>
> What do you all think?
>
> Regards,
> Rocky
>
>
> --
> Rocky Burt
> ServerZen Software -- http://www.serverzen.com
> ServerZen Hosting -- http://www.serverzenhosting.net
> News About The Server -- http://www.serverzen.net
>
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> Unsub: http://mail.zope.org/mailman/options/zope3-dev/eucci.group%40gmail.com
>
>