On Tue, 2009-02-10 at 09:56 +0200, Sergey Koval wrote: > Hello, > > I read mentioned thread and still can't figure out how I can pass > arbitrary values to widgets. > OK, I'll rephrase question (it was "task" in the previous email): how > I can make widget that takes two values out of the model without > changing ModelForm behavior or doing separate query in the widget?
Your constraints are a bit arbitrary and, in fact, overly-restrictive. In particular the "without changing ModelForm" wish is just that: a hope, not something that falls out of the design as "it looks like this must be possible." A ModelForm is a form that maps each model field to a particular form field. That's all. It's not a prototype for arbitrary model -> form mappings. Rather, it implements one particular sort of (commonly useful) mapping. If you're wanting to do extra stuff, it's reasonable to think that you might have to make some changes to ModelForm. You've certainly moved a bit beyond that use-case in your example. You're wanting a form based on a model where each form field have potential access to the model instance (not each form field corresponding to a single model field), so you'll have to create a class that knows how to pass in that information when requested. I wouldn't be thinking about this from the widget level. Widgets are just the rendering side. The better question is how to construct a form class that allows you to specify form fields which can work with this information. You're asking how to create a particular sort of form field (Django-form field, not HTML-form field) here. The final rendering, via Django-form widgets, will almost certainly just use normal (existing) widgets. I haven't worked out an answer, in terms of code, to your problem yet, beyond thinking it didn't seem to hard. I'll try to find some time tonight to work out some specifics and post tomorrow if nobody else comes up with a passable solution. But, in the interests of understanding the issue properly, I would suggest you spend a bit more time thinking about this yourself, based on the lines I've written above, rather than hoping somebody might give you the answer outright in such a short space of time. > Probably it is bad mailing list to ask such questions, should I go to > devel instead? This is exactly the right mailing list for this type of question. Anything of the form "how do I ...?" is a django-users question: it's asking about using Django. The django-dev list is more appropriate for topics concerning developing Django (core) itself. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
