I do have a widget attribute set on the field in the model but it is
rendered in the template as a <ul>. In which part of the model-view-template
do I specify how the radio (or checkbox) fields are rendered?
My model looks like this:
class ParticipantAttrForm(forms.Form):
# Dynamically creates a form to search participants attributes
def __init__(self, *args, **kwargs):
super(ParticipantAttrForm, self).__init__(*args, **kwargs)
for o in Subject.objects.all():
if o.e_type == 'TextInput':
self.fields['subject_%s' % o.id] =
forms.CharField(required=False,
label=o.e_question)
elif o.e_type == 'RadioSelect':
self.fields['subject_%s' % o.id] =
forms.ChoiceField(required=False,
label=o.e_question,
widget=forms.RadioSelect,
choices=o.get_e_choices())
elif o.e_type == 'CheckboxSelectMultiple':
self.fields['subject_%s' % o.id] =
forms.MultipleChoiceField(required=False,
label=o.e_question,
widget=forms.CheckboxSelectMultiple,
choices=o.get_e_choices())
elif o.e_type == 'Select':
self.fields['subject_%s' % o.id] =
forms.ChoiceField(required=False,
label=o.p_question,
widget=forms.Select,
choices=o.get_e_choices())
The view includes these lines:
attributes = ParticipantAttrForm()
t = loader.get_template('add_entry.html')
c = Context({
'attributes': attributes,
})
return HttpResponse(t.render(c))
And the template looks like this:
<table>
{% for attribute in attributes %}
{{ attribute.label }} {{attribute }}
{% endfor %}
</table>
> From: Rubic <[EMAIL PROTECTED]>
> Reply-To: "django-users@googlegroups.com" <django-users@googlegroups.com>
> Date: Mon, 12 Feb 2007 13:20:59 -0800
> To: Django users <django-users@googlegroups.com>
> Subject: Re: Radio and Checkbox rendering
>
>
> Have you looked into passing a widget attribute into your field? You
> can either subclass a widget or create one from scratch.
>
> --
> Jeff Bauer
> Rubicon, Inc.
>
>
>> I have a form that is generated dynamically and contains either radio,
>> checkbox, text field or drop down menu.
>>
>> The following is used to render the form:
>>
>> <table>
>> {% for attribute in attributes %}
>> <div class="row">
>> {{ attribute.label }} {{attribute }}
>> </div>
>> {% endfor %}
>> </table>
>>
>> This work well except when attribute is a radio or a checkbox it
>> renders the field as unordered list. This is not what I want in this
>> particular case. From the source I can see that RadioFieldRenderer
>> should be used to customize how the radio button is rendered.
>> (Couldn't find a similar renderer for a checkbox).
>>
>> How can I take advantage of the RadioFieldRenderer in a template? And
>> can I check if attribute is a particular field type in a template?
--
Gall y neges e-bost hon, ac unrhyw atodiadau a anfonwyd gyda hi,
gynnwys deunydd cyfrinachol ac wedi eu bwriadu i'w defnyddio'n unig
gan y sawl y cawsant eu cyfeirio ato (atynt). Os ydych wedi derbyn y
neges e-bost hon trwy gamgymeriad, rhowch wybod i'r anfonwr ar
unwaith a dilëwch y neges. Os na fwriadwyd anfon y neges atoch chi,
rhaid i chi beidio â defnyddio, cadw neu ddatgelu unrhyw wybodaeth a
gynhwysir ynddi. Mae unrhyw farn neu safbwynt yn eiddo i'r sawl a'i
hanfonodd yn unig ac nid yw o anghenraid yn cynrychioli barn
Prifysgol Cymru, Bangor. Nid yw Prifysgol Cymru, Bangor yn gwarantu
bod y neges e-bost hon neu unrhyw atodiadau yn rhydd rhag firysau neu
100% yn ddiogel. Oni bai fod hyn wedi ei ddatgan yn uniongyrchol yn
nhestun yr e-bost, nid bwriad y neges e-bost hon yw ffurfio contract
rhwymol - mae rhestr o lofnodwyr awdurdodedig ar gael o Swyddfa
Cyllid Prifysgol Cymru, Bangor. www.bangor.ac.uk
This email and any attachments may contain confidential material and
is solely for the use of the intended recipient(s). If you have
received this email in error, please notify the sender immediately
and delete this email. If you are not the intended recipient(s), you
must not use, retain or disclose any information contained in this
email. Any views or opinions are solely those of the sender and do
not necessarily represent those of the University of Wales, Bangor.
The University of Wales, Bangor does not guarantee that this email or
any attachments are free from viruses or 100% secure. Unless
expressly stated in the body of the text of the email, this email is
not intended to form a binding contract - a list of authorised
signatories is available from the University of Wales, Bangor Finance
Office. www.bangor.ac.uk
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
