I realize this wont get a lot of attention right now do to work on
1.1, but I figured I would mention it now so I can get opinions before
I start any actual work on the idea

The editable keyword in model fields as an administrative feature I
feel should not be defined in the model, it is still fine for
ModelForms.

What I propose is a static_fields list, similar to search_fields in
the Models Admin class. There would be one major diffrence between a
static_field and how editable=False acts now and that is the ability
to display the data in the admin UI. Right now a field with
editable=False cannot be part of the admin fields list, which is
rather anoying when you wish to see what the data is but dont want it
to be editable via the admin UI.

Any field (except FileFields) that is in the admin fieldset (weather
set directly set or by introspecting the model) and in static_fields
would render as a normal form field, but have the readonly attribute
set. FileFields would just provide the link to the file with the
target="_blank" attribute so the file could be downloaded or viewed
but not modified. This will allow field data to be viewed but not
modified and remove the only admin feature that remains in the Model
definition.

The only argument against this I can think of is that by relying on
the readonly attribute of a form field it would be possible for
someone to remove that attribute via a greasemonkey script or
something similar, thus allowing the data to actually be modified. But
if you think people you give administrative access to your site would
do that then maybe you shouldn't give them administrative access, and
it should be possible to ensure that when the form is submitted any
field that is in the static_fields list is just ignored when saving
the model.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to