Yeah form.branch_name displayed but the values are not the tuples - this is the primary reason why I'm seeking for help.
I have dabbled into the modelForm (widgets) as an option, obviously no luck there. At the moment, I'm building a new model that maps the db table that contains the values, build a class that returns the model values, pass it's values to render_to_response and have it printed as form select values in the template. I will post here if this works. Thanks for the heads up. On Mon, Aug 8, 2011 at 1:15 PM, Thomas Orozco <g.orozco.tho...@gmail.com>wrote: > Like they do in the admin, right ? > > You might want to check Django's source for the admin forms and templates > to get some inspiration then. > > Hard coding the choices is never a satisfactory solution but I suggest you > retrieve them from your models file so you stay DRY compliant and then it's > pretty OK. > > As you put the widget in your field I think you just need to put > form.branch_name to get it to display. > Le 8 août 2011 14:07, "Kayode Odeyemi" <drey...@gmail.com> a écrit : > > -- > 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. > -- Odeyemi 'Kayode O. http://www.sinati.com. t: @charyorde -- 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.
