I like your idea because it doesn't add a new option to the admin class. I went for the simplest possible implementation while this would require modifying a bit newforms to allow editable=False fields to be forced in. On the other hand, one might want to have some editable=True fields as readonly in a specific admin interface (newforms-admin now makes it possible to have multiple admin sites AFAIK) so your solution wouldn't cover as many use cases.
Ultimately it's up to the core devs to decide whichever makes more sense. Regards, Philippe On Apr 10, 6:30 pm, "James Stembridge" <[EMAIL PROTECTED]> wrote: > > Perhaps a simpler way of handling things: > 1. Leave the current behaviour of "editable=False" as is, i.e. if set > the field will not by default appear in the admin interface. > 2. Allow "editable=False" fields to be included in the "fields" Admin > option to override the default behaviour and display whatever they > contain. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
