Hi @mtnhiker. I ran into very similar problems and spent weeks dealing with a View class based on Django-1.4's django.contrib.formtools.wizard.views.SessionWizardView. It was so much customization that some things started to go wrong and debugging was awful.
I came up with this solution: https://gist.github.com/3098817 and https://gist.github.com/3080251 Let me know if it works for you. PS: Related question in stackoverflow.com<http://stackoverflow.com/a/11455183/556413> . On Saturday, August 4, 2012 12:01:25 AM UTC-4, mtnhiker wrote: > > Answering my own question... > > I debugged my brain a bit and got something working with branching. > Here's my interpretation of my brain bug. > > First a "step" is not something attached to a particular form. Its the > index in a sequence. The same form might be step 2 with one branching > structure but step 3 for another. > > Second, the "condition_dict" keyword to wizard.as_view() should be thought > only as "use or don't use" a form. For me, this mean I had to stop thinking > of how to make the wizard go from one node to another in a flow chart. Its > as if all nodes in a flow chart are possible and the condition_dict is used > to look up-stream in the flow-chart to decide if a particular node (form) > should be used. > > I still would like to be able to design a wizard as a flow chart wtih > branches that switch based upon field values. I'd like to do this very > directly. Perhaps I will write a django contrib that effectively tales > input as a directed-graph that represents the flow chart, and generates the > right condition_dict to make it happen. (but first I have an app to build) > > On Friday, August 3, 2012 7:27:03 PM UTC-7, mtnhiker wrote: >> >> I think I must be missing something. To me a wizard should provide >> questions and branch according to the answers (otherwise why not just put >> it all in one form?). I've searched the docs and web and source, but I >> don't find anything that lets me branch. I thought the "condition_dict" of >> the wizard view would do the trick. Seems not. >> >> Using the condition_dict can say when a step should be skipped. But this >> isn't the same as jumping to a specific step. >> >> What I really want is to (somewhere!) check the values of a form right >> after the user hit "submit". Based on those values, jump to the next >> appropriate form. >> >> What is broken in my thinking about this? Are people actually writing >> wizards with 1.4 that use the form wizard and do branching? >> >> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/LU9vMm8Pa-gJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
