Preston Having not done this before (but maybe needing to soon...) the grid approach seems the best solution.
Actually this is not really a Django issue per se; more a "mismatch" between the "excel-type" view and the underlying database reality. Django is just the middle-man, translating "filled-in holes" to clean database records. I would think there must be a neat JQuery interface one could construct for the view? Derek On Nov 16, 1:01 am, Preston Holmes <pres...@ptone.com> wrote: > This is a cart/horse pattern I run now and then, and while I can think > of several sort of ugly ways to do it, I'm wondering if someone has a > clean solution in Django. > > I'm going to use a gradebook as an example. The goal is to present a > user with a grid of lets say students and assignments to enter > grades. The models would be > > - Students > > - Assignments > > - Grades (a M2M between students and assignments) > > Now on the grade entry form, with multiple students and assignments, > the grades don't yet exist for all students, and may not all be > entered. How does one generate the form for the possibilities, > without pre-creating all the empty grades. > > It would be nice to use modelform here, but it seems that that the > only way to do it is just with a form and then create objects for > grades that get filled out in the view. How do others solve this > problem of representing a "possible future" object in a form that is > then only optionally created if filled out. > > -Preston -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
