On 4/6/06, Michele Cella <[EMAIL PROTECTED]> wrote: > I would like to remove this evil isinstance and replace it with > something that checks the presence of a callable validate method, this > will let other home-grown widget system to take advantage of the > validate decorator and AFAIK we are already doing the same for > retrieve_css and retrieve_javascript.
+1 > 2) In ticket #531: > > http://trac.turbogears.org/turbogears/ticket/531 > > we committed a patch that adds support for SQLObject functionality to > the SelectionField, as I said on the ticket this is not something we > should support IMHO since the selection field is just meant to work by > providing a list of (id, description) tuples without assumption of > specific hacks to support SQLObject, is there a use case for this that > I'm missing (for example FastData) or just a wrong use? should we > remove it? This hack is not as bad as I thought since it doesn't directly reference SQLObject (something that would've made me most unhappy). But, I'd still say "+1" on ditching the hack. If we want some SQLObject friendly widgets, they should be separate. >3) I would like to remove two (I think) useless widgets since I can't > see any use case fot them: > > Label (unused by TG core and by no one IMHO) > ImageButton (any example of using this as a widget) It sounds like Label has a use, and ImageButton seems almost useful. Let's keep them for now. We need a ticket to make sure all of the standard widgets include WidgetDescriptions. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
