If we did split it out, would you be interested in being a maintainer? On Monday, May 26, 2014 6:51:13 PM UTC-4, Gordon wrote: > > > > On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote: >> >> My observation is that not many core developers seem interested in >> contrib.formtools these days. It was added by Adrian in 2006, but as far as >> I can see from the commit history, it hasn't received much love lately. If >> would be a good candidate for deprecation from Django itself, in my opinion. >> >> On Monday, May 26, 2014 3:32:41 PM UTC-4, Gordon wrote: >>> >>> Hello, >>> >>> I have posted an implementation/proof of concept to ticket 21644 ( >>> https://code.djangoproject.com/ticket/21644). The implementation is >>> currently written as a mixin because I need to be able to use it now and I >>> don't like maintaining a custom fork of django for my projects. If changed >>> to update the base classes directly, the diff would be minimal. >>> >>> I am happy to work on FormWizard improvements because they are >>> particularly useful for some of my projects, but I haven't had much of a >>> response. Since this is a contrib app bundled with django, I am hesitant >>> to spend too much time on it without some sort of positive and/or >>> constructive feedback from someone who can accept the changes. >>> >>> On topic... the brief summary for #21644 is that this allows for >>> "confirmation" steps in a formwizard that have access to the data submitted >>> for previous steps. This is required for something like a checkout >>> confirmation or anything where the user needs to be presented with data >>> entered previously for acceptance to be meaningful. It was important to my >>> use case that the wizard supports multiple confirmation steps. I've used a >>> base class that confirmation forms should inherit from to detect when >>> confirmation logic should be used. This allows for a backwards >>> compatible opt-in approach. >>> >>> Thanks, >>> Gordon >>> >> > > > Fair enough and thanks for the reply. That is too bad though. I've seen > a good number of 3rd party apps that would benefit from using the > NamedUrlWizardView ( > https://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/#usage-of-namedurlwizardview > ). >
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c1e36882-082d-4f33-8b4b-57daf381e141%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
