Jonny Buchanan

PR for implementation of #78

Example: ``` javascript var SignupForm = forms.Form.extend({ password: forms.CharField({widget: forms.PasswordInput}), confirm: forms.CharField({widget: forms.PasswordInput}) clean: ['password', 'confirm', function() { var {password, confirm} = this.cleanedData if (password && confirm && password !=...

Create a utility which, when provided with an HTMLFormElement, will generate source code for a corresponding forms.Form with best guesses based on form's elements.

There's a cost associated with constantly recreating new form instances in that `YourForm.prototype.baseFIelds` gets deep -cloned to `yourFormInstance.fields` by the `BaseForm` constructor. Having a means of externalising a form's working...

1. Heavy Meta! 2. It'll be fun to write 3. It'll be useful 4. It'll be a good demo

There is a performance cost to forcing a re-render of the form's containing component when something changes. Figure out and document some guidelines for writing your own `BoundField`-rendering React component...

This can wait until widgets can be specified as React components, to manage the logic of ensuring invalid days per month can never be seected

Use case: using newforms on Node.js with String-based templating, e.g. these Jade mixins: https://github.com/insin/successcrm/blob/master/views/mixins/forms.jade