#15015: Mixing read-only with ability to add new instances using a FormSet
---------------------------------------------+------------------------------
          Reporter:  coleifer                |         Owner:  nobody 
            Status:  new                     |     Milestone:         
         Component:  Forms                   |       Version:  1.2    
        Resolution:                          |      Keywords:  formset
             Stage:  Design decision needed  |     Has_patch:  0      
        Needs_docs:  0                       |   Needs_tests:  0      
Needs_better_patch:  0                       |  
---------------------------------------------+------------------------------
Comment (by coleifer):

 Replying to [comment:1 russellm]:
 > The complication here is that *forms* have no concept of readonly fields
 -- that's an admin-specific feature. By extension, formsets don't have any
 knowledge of readonly fields either. This is by design; we added readonly
 fields as a specific admin feature, not as a general feature of the forms
 library.


 Totally, I'd propose moving the readonly behavior into the forms API and
 converting the admin from a special-case to a general one.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/15015#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en.

Reply via email to