There is a problem with: http://code.djangoproject.com/ticket/3247 http://groups.google.com/group/django-developers/browse_thread/thread/50150b61aca46a7e
I've made a first working version but my implementation reverses the changes described in the above ticket/discussion. Here's a summary of what I did: - cancel filtering of editable=False fields when creating forms for instances and models (ie the fields are in the form, hence the above remark) - added an editable (default value True) field in newforms.Field - added a DisplayWidget, and made Field use it when editable = False Please tell if that is acceptable. Again, there seem to be an issue with naming. Maybe there should be a name for fields that can be created by the user but only seen afterwards, and purely internal fields which are not even displayed. Maybe those options could be spread out between the model and the admin class ? The current semantics of editable make sense for models, but what I'm doing would be relevant only for the admin. Adrian: I've cc'd you so because you seem to be working on newforms- admin. The context of this message is at http://groups.google.com/group/django-developers/browse_thread/thread/1d7d8cb0662181c6 Regards, Philippe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
