update_object generic view should take manipulator?

2 views
Skip to first unread message

shredwheat

unread,
Apr 6, 2006, 9:46:31 PM4/6/06
to Django users
I'm still somewhat new to django, so I'm trying to figure out if this
is a good idea, or a warning that I'm headed in the wrong direction.

It would seem highly useful to me if the update_object and
create_opject generic views could also take an additional keyword
argument for the manipulator class to use.

I end up making a lot of custom manipulators for my different forms,
but I must make a custom view to handle this. It seems like almost
every case I could just use the generic views for this, if I could feed
in my own manipulator class.

Do other people find this situation common? Or have I entered into some
strange style of development that is not usual? I would happily submit
the patch for this if it is the type of thing that would get reviewed.

Michael Radziej

unread,
Apr 7, 2006, 4:34:03 AM4/7/06
to django...@googlegroups.com
shredwheat schrieb:

> It would seem highly useful to me if the update_object and
> create_opject generic views could also take an additional keyword
> argument for the manipulator class to use.

I share your opinion; perhaps I'll write a wiki entry about this style. See

http://code.djangoproject.com/ticket/1563

There's also a patch (for magic-removal). You can also simply copy the
generic views into your project, if you don't want to patch django.

Michael

Reply all
Reply to author
Forward
0 new messages