Alberto Valverde wrote: > > +1 on this too, but I like "widget_args" better. Makes clearer we're > talking about widgets IMO. No extra magic attribute please, > widget_args (or whatever) will then mean: "any argument you can > override when subclassing, initializing and display". (instead of > only template arguments) >
Yep, your definition is perfect (I'm saving it for later reuse). ;-) What about widget_params? @Simon: - tg_args, I don't think we really need the tg prefix here since we aren't popping this thing into a generic (usually user-defined) context like a controller method where we indeed need tg_errors and so on... - Yep, I haven't used the word protocol since it seemed "too much" but that's exactly what we are talking about and again your definition is perfect, an informal protocol and I agree that we should extend the same thing to other TG places where applicable. 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 -~----------~----~----~----~------~----~------~--~---
