On 26/04/2006, at 12:31, Michele Cella wrote:
> I can't see the problem with inheritance, there are no changes needed
> at meta.py.
Yep, there is... every parameter listed at params gets a descriptor
to access it to handle automatic calling, *at least* you would have
to make a check so these "params/member_widgets" don't get called
when passed to the template.
Regarding to inheritance:
class A(Widget):
params = ["a", "b", "c]
member_widgets = ["a", "b"]
class B(Widget):
params = ["b"]
Hmm, why is this B.b behaving in such a funky way? Let's look ate the
bases (fortunately there's only one)... oh, I see, it's also listed
at member_widgets there, better give it another name... My point is
that this is confusing, and can get even worst if the inheritance
tree is big enough...
As Kevin mentioned, member_widgets and params are completely
different things (the "flow" argument). No special case code should
be added IMO to check when a param is also a member_widget to treat
it in a different way. Just complicates things (implementation and
documentation) to bring them together IMO.
My .2€,
Alberto
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
