Re: Using twForms with Pylons. Part 1

[Ben Bangert]

On Oct 30, 2007, at 6:38 AM, Alberto Valverde wrote:

I do believe that this is because FE's UnicodeString.from_python returns

a str instead of unicode. I'm not too sure of the rationale behind this

but, given that most template languages now expect unicode to be used
internally (only encoding when finally rendered), I think FE's
from_python should also return unicode. This came up some time ago in

archives I'm sure the thread will pop up.

FE's list, if you google for "toscawidgets" and "unicodestring" in it's

Might be my fault, I think I put the first version of the Unicode validator in FE, based on the TG one.

If he objects to python functions in templates like webhelpers' then I
don't think he'd like twForms at all either since fields are rendered
this way: ${display_child('name')}.

In  this scenario twForms might not be a good solution. twForms is a

flexibility is lost in exchange for simplicity.

higher-level layer on top of plain html. As with all abstractions, some

Cheers,
Ben

I thought widgets could have their templates overridden? Wasn't that one of the main uses for the Widget browser? Ie, to browse available widgets, their options, and see the templates they come with so you can customize them if needed.

smime.p7s
Description: S/MIME cryptographic signature