Would have to look at how FormPreview's work, but I agree. So far what I've done with the wizard is remove all of the data from the session as much as possible. It calculates cleaned_data at the very end and only stores the POST values (still need to solve a potential exploit). One thing I didn't like was storing the base_forms in the session (in order to dynamically change the forms based on what has happened. The way this is done it would severely bloat the Form version, or make it not possible. Anyone have suggestions on a way to handle this? We could calculate the list of forms based on the data stored each time, but not really sure.
On Dec 4, 5:23 am, "Hanne Moa" <[EMAIL PROTECTED]> wrote: > On Thu, Dec 4, 2008 at 03:34, David Cramer <[EMAIL PROTECTED]> wrote: > > When the done() method is called, the session is also cleared unless > > done(). Maybe this should only happen if say a ValidationError isn't > > raised? Maybe a setting that makes this not happen? In all of my > > situations it makes sense to erase it when it's complete, and not have > > to call methods manual. Let's decide which is more common. > > How about making it easier to have a preview also? As per today, > FormWizard and FormPreview aren't really combinable. Should probably > be it's own ticket... > > HM --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
