Opened 19 years ago
Last modified 13 years ago
#13 closed New feature
Related objects interface should be tighter — at Version 2
Reported by: | Adrian Holovaty | Owned by: | Wilson Miner |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | nfa-someday nfa-changelist |
Cc: | cmlenz@…, gary.wilson@…, tom@…, django@…, brosner@…, tom85@…, dan.popovici@…, django@…, lnielsen@…, to, patrick.lauber@…, mpjung@…, django@…, remco@…, barbuzaster@…, flavio.curella@…, semente@…, stephane@…, Odin Hørthe Omdal, bas@…, mathijs@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
The admin interface for related objects and the ordering interface need some tighter integration.
Currently, anything that can be ordered goes in the right sidebar of the admin change form, with no relation to the actual input fields for those objects.
The adding, removing, editing and ordering of related objects should be tied together in one part of the form.
Specific areas for enhancement:
- Adding related objects should be easier. Now you have to "save and continue" to get an extra set of fields to add a new related object. You should be able to click "add new object" to add another set of blank fields inline on the page.
- Deleting related objects should be easier. Now you have to clear the "core fields" of a related object to delete it. You should be able to click "delete" to delete the object, or at least mark it for deletion when you click save on the main object.
- Ordering of related objects should be clearly tied to editing those objects. Now the ordering interface is completely separate. You should be use the same list of objects to set the order (by dragging) or select that object for editing or deleting (by clicking).
Change History (2)
comment:1 by , 19 years ago
Owner: | changed from | to
---|
comment:2 by , 19 years ago
Description: | modified (diff) |
---|
Note:
See TracTickets
for help on using tickets.