#2360: user centric/object centric generic crud tools
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Generic views | Version:
Severity: normal | Resolution:
Keywords: |
--------------------------------------+-------------------------------------
Comment (by [EMAIL PROTECTED]):
Probably the best way to do this, and i was thinking about creating a
patch to do so, is to allow CRUD generic views to accept an especific
manipulator. The generic view will only show the fields related to that
manipulator, the other fields can be either filled with default values or,
as you said, pre-populated in a view that extends the generic view.
Allowing the generic view to accept the manipulator is not hard, the only
thing you need is your newly created manipulator to extend the right class
(the one that contains the objects needed by the GV. i.e. flatten_data() )
and adding some:
if extra_manipulator:
manipulator = extra_manipulator()
else:
model.AddManipulator(follow=follow)
to prepopulate field thats another story (ill probably post about that or
add a patch sometime soon) but im sure this two enhancements are just what
generic views are lacking (at least crud) and do not deviate from the
'django philosophy'
--
Ticket URL: <http://code.djangoproject.com/ticket/2360>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
