On 11.05.2011, at 20:35, David Durham wrote:
> On Mon, Apr 25, 2011 at 11:09 AM, Stephan Jäkel wrote:
>> Hi everybody,
>>
>> I want to continue the discussion on the replacement of
>> django.contrib.formtools.wizard (previous discussions can be found here:
>> http://bit.ly/eI5ZT5 and http://bit.
On Mon, Apr 25, 2011 at 11:09 AM, Stephan Jäkel wrote:
> Hi everybody,
>
> I want to continue the discussion on the replacement of
> django.contrib.formtools.wizard (previous discussions can be found here:
> http://bit.ly/eI5ZT5 and http://bit.ly/gVTRtr).
I keep seeing some maintenance type of a
As I said before I'm +1 for this. I have to tests latest code against Django
1.3 to see
if it handles browser's back button correctly. But django-formwizard is a
great app, far
better and more complete than current contrib's wizard.
I have to apologize for not collaborating in building the docs fo
Jacob Kaplan-Moss wrote:
I'm +1 in theory. I need to spend some time going through your code,
and I'll need to see some documentation on porting existing wizards to
the new code (unless it's truly 100% backwards compatible). But in
general I think it's a fine idea and something I'd love to target
On Mon, Apr 25, 2011 at 11:09 AM, Stephan Jäkel wrote:
> Are there any doubts integrating django-formwizard into Django?
I'm +1 in theory. I need to spend some time going through your code,
and I'll need to see some documentation on porting existing wizards to
the new code (unless it's truly 100%
Hi everybody,
I want to continue the discussion on the replacement of
django.contrib.formtools.wizard (previous discussions can be found here:
http://bit.ly/eI5ZT5 and http://bit.ly/gVTRtr).
I worked on moving the currently external django-formwizard to use class
based views. The repository/
