On Mon, 2009-05-11 at 10:59 -0700, eric.frederich wrote: > Hmm, thats almost what I need. I guess I didn't fully explain what I > need. > I do need to limit the number of fields that are shown, but I also > need to make some of them view only.
I don't think this "view only" feature exists. Google 'django read only'. Note that if you're going to allow creating new Enrollment s on this page the extra forms will have to allow User selection. > For example, this is on a relation table between an Offering object > and a User object called Enrollment. > I don't want them to be able to edit the Offering or the User (which > appear as combo boxes), only some of the other fields on the > Enrollment object like a status field and some boolean fields. > While editing the each Enrollment object they will need to be able to > see who the user is but they don't need to see the Offering (since > this view is all enrollments for a particular offering). The rest of this sounds like the functionality present in admin: http://docs.djangoproject.com/en/1.0/ref/contrib/admin/#working-with-many-to-many-intermediary-models Also check out inline formsets: http://docs.djangoproject.com/en/1.0/topics/forms/modelforms/#inline-formsets > Is this too specialized, will I need to re-invent the wheel here? Maybe customize the wheel a bit. Good luck. sdc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
