What am I supposed to do if I want a Wizard?

[Martin Torre Castro]

Hello,

I was investigating about form wizards in Django, but I have seen that recently this has changed in the deprecation timeline doc:

"The form wizard has been refactored to use class-based views with pluggable backends in 1.4. The previous implementation will be removed."

I understand that the old form wizard is now part of the form-tools package and I must install it if I want to use it.

My question is if I should do it or maybe I should "use class based-views with pluggable backends", which I'm not sure of what means and sounds like doing all the classes and boilerplate for doing wizards all again on my own.

Please, could someone give me some advice. If I go with class based views, could someone pass me a link where I can find some example with a form wizard made in such way.

Thank you very much in advanced.

[Kristofer Pettijohn]

I sdid my own form wizard for a project I worked on.  For a good example, you can look at Oscar Ecommerce in github, and look at their checkout app within the code.  That may inspire you with some ideas on how to implement such a behavior.

---

From: "Martin Torre Castro" <mad...@gmail.com>
To: "Django users" <django...@googlegroups.com>
Sent: Wednesday, December 9, 2015 5:10:14 AM
Subject: What am I supposed to do if I want a Wizard?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ac8fecc6-baed-4b40-8f71-bfdc17a69ee7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Martín Torre Castro]

Thank you, Kristofer. It's interesting. I'm looking right now.

It seems complex, but I will investigate, although I would prefer a more generic way of doing this, because I suspect I will be using many wizards soon.

Any other suggestions?

You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/_8_lqJsiqkc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-users...@googlegroups.com.

To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2461989.1453939.1449698183679.JavaMail.zimbra%40cybernetik.net.

[Kristofer Pettijohn]

If you just want something simple, stick with Form Wizard.  If it doesn't do something you need, see if you can extend it by creating a new class and overriding methods that you need to change.  Otherwise if you need more functionality, I would roll your own.

---

From: "Martín Torre Castro" <martin.to...@gmail.com>
To: django...@googlegroups.com
Sent: Wednesday, December 9, 2015 4:30:08 PM
Subject: Re: What am I supposed to do if I want a Wizard?

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAKijOkywv9kv7nwbV8WQbL54%3Dv26ZYvEagwL78VRt62Wyn%2BztQ%40mail.gmail.com.