> * decoupled from data -- base class `form-widget' stores intermediate > and parsed values in field widgets instead of mandatory underlying > data objects. A subclass that works with underlying data objects will > be provided. >
That's really cool. There were several instances where the current form-widget did not properly model user expectations when they hit cancel. * new slim layout that doesn't use lists and gets away from the focus on gridedit child forms. Likewise, this was a major UI pattern, and having generalized 1st-class alternatives will be great. cheers, Nandan -- 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.
