Re: Keeping state in the FormWizard: instance attributes considered harmful?

yes this is very similiar to what I am working on right now. Being a
newbie it seems much harder than it should be. I ended up setting a
state variable within self.extra_context. It is set by overriding the
process_step function in the FormWizard class based on the results of
the previous forms values. This state variable is also used in the
get_template function(also overridden) to control which template is
displayed.

In my case I have 10 forms/sections and the quickest way through will
show 6 of them and the longest will show 9 forms.

When you say " Form2 (must be dynamically set based on the submitted
values in Form1)" do you mean which form or which fields within that
form?

I am currently struggling with the display of pending changes and if
the user does not like them allowing them to go back and change them
so any ideas or solutions would be appreciated.

txranger

On Nov 3, 1:30 pm, "Mark L." <mark.l...@gmail.com> wrote:

> Just to sparkle your imagination, the desired workflow of aFormWizard
> I am trying to implement is as follows: Form1 -> Form2 (must be
> dynamically set based on the submitted values in Form1) -> Form3 (show
> a preview of pending changes to the user) -> done() (apply the
> changes). I know, it sounds a bit complicated, but that is the way it
> *has* to be.
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---