Saikat Chakrabarti wrote:
> I agree. I started refactoring at least the whole form widget class > hierarchy to have an underlying form class that is essentially like a > quickform, and building the thing that dataform is supposed to be on > top of that (always seemed weird to me to have the larger class - > dataform - be the base class for quickform). To elaborate on my position regarding forms (my earlier comments were mostly about the table widget hierarchy): The current dataform is too rigid and bloated indeed. There are many types of forms so it would make sense to have a lean base class. Not necessarily quickform though. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
