#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:3 russellm]:
> And I'm saying that ain't gonna happen. Leaving out readonly widgets
from the forms library was a very *specific* design decision. Check the
archives for the discussions on the topic.
Fair enough. I think my initial use case is still valid, basically
allowing read_only fields to be specified for admin inlines, but having
those read_only fields not affect adding new rows (i.e. you can't edit
existing inline items but can add new ones). This jives a lot with the
"can_add" vs "can_edit" permission workflow.
--
Ticket URL: <http://code.djangoproject.com/ticket/15015#comment:4>
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.
