Pretty much any widget can have its template overwritten. They all accept a template= parameter when they are created, which can be a reference to a kid document the same as you see in @expose()
That said, a lot of the logic for some widgets happens in templates, so making changes to them is not for the faint of heart. Off the top of my head I remember the TableForm/ListForm widgets as not being something I would want to muck with on my own. My recommendation would be to leave as many templates as you can alone, you can get pretty far by passing attributes to a widget to handle things like CSS classes. I don't know of any documentation for this offhand, but the source code involved is pretty easy to comprehend. -Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
