Em Sexta 28 Abril 2006 10:47, Michele Cella escreveu: > > Yep, that was an other option I haven't proposed that will work well > and it's pretty clear, if you really don't want to subclass just use a > function that returns a *new* instance at every call, not the same like > a WidgetsList does.
I'm fine with subclassing... It puts things almost in the same "level" of organization (all widgets are classes, for example). > 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. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
