Hi Michele,
How about "child_widgets" or something that makes obvious we're
dealing with child widgets. widget_vars sounds more like variables
('vars') sent to the widget, like "variables sent to the template"
which is what template_vars stands for,
Just an opinion,
Adeu
Alberto
On 21/03/2006, at 23:46, Michele Cella wrote:
>
> I will commit some small refinements (always backward compatibles) and
> improve the base CompoundWidget to provide again value_for and
> options_for.
>
> There is one thing people using CompoundWidget and running svn should
> take into account:
>
> widgets becomes widgets_vars
>
> that's to avoid conflicts when you import for example:
>
> from turbogears import widgets
>
> (just experienced this)
>
> and is also more in line with template_vars.
>
> Don't ask me why I haven't made it in this way since the beginning...
> :-(
>
> Ciao
> Michele
>
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk
-~----------~----~----~----~------~----~------~--~---
