Opened 19 years ago
Closed 18 years ago
#1567 closed enhancement (wontfix)
Admin interface fields should be customizable
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | contrib.admin | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
While radio_admin is useful, this should be more general. If someone wants a custom date field, it shouldn't require tinkering with the source code. Personally, I want to use it for ForeignKey fields when the reference table has over 1000 entries.
An example of how I see it.
class Album(meta.Model): title = meta.CharField(maxlength=30) artist = meta.ForeignKey(Artist, admin_interface = 'app/my_artist_template') format = meta.CharField(maxlength=4, choices = CD_OR_LP, admin_interface = django.whatever.radio_admin)
I create a small template (that gets used again in the public interface) that creates just the code for the field. Somewhere there's an example template that's just perfect for radio choice fields.
Change History (3)
comment:1 by , 19 years ago
comment:2 by , 18 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:3 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This is one of the design goals in the NewformsAdminBranch. However it won't be changed in the current admin branch.
ha ha, radio fields for your music admin, that's wonderful :)