accept add adds ajax append bf bferrors bit blog cciwformmixin changed class client code control controlid controlidn controlname create createpollform cssclass curmember dec def defaultformfilter development div django djangonormalisecontrolid domnode edit editpollformname element elements elm enc encodeform err error errorclass errorrow errors escape event existingpoll facebook false field fields filter forceunicode form formfilter formname formnode forms forum function functions handle handler handlers helptext hiddenfields html http id import inarray include initial input inputs insert instance javascript join jquery json jsonencoder konqueror kwargs label len length li lines maxlength method mkinputchangehandler mochikit newforms newpoll node note null obj object opt option options output parentnode part passed path poll pollid polloption polloptionlistfield post push python pythontojson relevant rendering req request return returns row save script show side site splitdatetimewidget standardformclearerror standardformgetformrow string submit suffix summary tagname text textarea textjavascript title today tolowercase toperrors topic type ul validation validationerror validationerrorbottom values var widget widgets work

Keyword Cloud Navigation Map

Before we get going, some context: the Christian Camps in Wales web site has a forum system which allows people to create polls. I rewrote this recently to use newforms, mainly to keep up to date with Django, and also to try out some AJAX.

I first had to write a 'Form' subclass which encapsulates the logic for validating and processing the form. As it happens, the form is based on a model 'Poll', but it requires more fields. In particular, this single form is used to create all the PollOption objects that are attached to the Poll. This is handled by a simple textarea field, into which all the options are entered on separate lines. In Django, we implement this using a custom 'Field' that uses the 'Textarea' widget and adds the relevant validation.