Jorge Godoy wrote:
> > I also don't feel comfortable to hack WidgetsList in this way since
> > it's meant to be just syntax sugar as Kevin said.
>
> I agree, but either it is syntactic sugar preserving the list behavior or we
> explicitly tell that besides it appearing to be a list it has some
> particularities that make it different than a list is.
>
> Anyway, my original question was: why it changes the order? Just because of
> its name? Does this name binds some position to the widget as well? As I've
> shown, a real list has no such problem.
>
I replied to your question in my first message, anyway as I said while
the first problem can be solved, there is still a problem with the
widget name that can behave somewhat strange, since we can't fix this
one (or we can if we always give always the precedence to the
WidgetsList declared name [1]) I would very much prefer to clearly
state a simple rule that you (not you Jorge, but all users) should
follow:
"Don't use nested WidgetsList"
This solves all problems, and again as I've said I can't see the
benefit of nesting them, looks ugly and somewhat harder to understand
to me. ;-)
Ciao
Michele
[1]
At the moment you can do:
class Fields(WidgetsList):
name = TextField(name="hello")
and the TextField's name is not "name" but "hello"
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
