That's the idea! And while we're at it... It seems to me that we could also be a little better about putting id and class attributes on the elements generated by widgets, to allow better and more fine-grained control of appearances via CSS. For example, I was thinking about adding a 'form_id' parameter to DataController, similar to 'form_list' or 'form_template'. This 'form_id' would act as a prefix for an id attribute put on the generated form, where the rest of the id attribute would be something like '_create' for a create form, and '_update' for an update form.
So, for example, you could give a DataController used for entering user info a 'form_id' parameter of 'my_user', and when the DataController generated an input form for creating a new user, the form would get an id attribute of 'my_user_create'. This would allow you to specify CSS to tailor the appearance of that particular form, which might be a different appearance of a 'my_user_update' form. What do you think? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
