On Sat, 2009-05-02 at 08:29 -0700, ken keller wrote: [...] > I'm interested in hearing how you cope w/ the problem of specifying > ManyToMany relationships in an object creation view. Consider two > models M1 & M2 and a creation view/form for M1. A technique I'm using > is to specify M2 values as an unbound field in a ModelForm for M1. > When the form validates: > m1Form.save() > I convert m1Form['m2'] into ManyToMany relationship chgs. This works > but it defeats the purpose of ModelForm. > > I'm making use of a scrolling <div> of checkboxes instead of a shuttle > widget (takes up too much space) or a multi-select widget (easy to > mess up the selection). I'm considering creating a custom widget for > the MultipleChoiceField. Is this practical or a good idea?
The two questions here are probably best raised on the django-users list. This list (django-developers) is for internal Django development. Questions about using Django are the area of django-users and we try very hard to keep the two separate, as there's a vast difference in audience, volume and content. Thanks for you understanding on this. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
