Nan, Regarding class-based views, I'm definitely in favor of it. Since Django 1.3 is just out, I haven't spent a lot of time figuring out how we would use them but I do agree that the concept makes a lot of sense for an app like Satchmo.
-Chris On Fri, Mar 25, 2011 at 11:53 AM, Nan <[email protected]> wrote: > I need to add some fields to PaymentContactInfoForm and also run some > extra validation on them. > > The fields can be added fairly easily with > signals_ahoy.signals.form_init, and saved with > signals_ahoy.signals.form_postsave; but the extra validation isn't so > simple. > > Is the only option to monkey-patch new clean() and [fieldname]_clean > methods into the form in the form_init listener? > > *** > > Just as an aside, I'm finding a lot of places where it would be handy > to be able to use custom forms and additional context in customizing > Satchmo. Is there any intention in the long run to move to a class- > based-views format, where we could subclass the views to use custom > form classes and extend context? I'd be very glad to contribute to > such an effort. > > cheers, > -Nan > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" 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/satchmo-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
