Jason Chu wrote: > > I use update_options in update_data. It's essentially what you > explained with css_classes, except that it works for any attribute > on any widget. It's a way to add/edit tg_options when all you have > is a widget and something you want passed to the widget at display time. >
Yes, that could be helpful... > > I'll give it a shot today. > > I thought tg_options was a good name. Because options aren't > necesarrily for the member_widgets, things like method and action are > options for the form. > I changed it to member_widgets_options in svn the reason is that even if method and action endup to be there aren't take into account when searching for options (options_for) to pass to a member widgets so that's exactly what they are, member_widgets_options to make it more clear I could even remove anything that's not a dict from there but this is not worth IMHO. 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 -~----------~----~----~----~------~----~------~--~---
