Patches in scope?

[mjl]

Over time, I have collected a couple of patches to form-designer, but I'm not sure if I should clean them up for merging or just keep them locked away where nobody sees the horror. Some are a bit hacky by misusing some field configs, for example.

• Add a datestamp to the file name of export xlsx
• Refactor form instance creation to add more hooks for easier subclassing/modifying
• New field types:
  • Static Text (renders a div, misuses the choices/default fields for config)
  • NumberField
  • Captcha with django-simple-captcha
• Alternative separator for choices so that a choice can contain commas
• Subject for send_as_mail configurable
• Force email recipient via setting for integration testing
• Placeholder for text fields (misuses the choices field)

[matthiask]

I think all of those are in scope. The choices field should probably be renamed (relabeled) to "choices / placeholder" or something like that.

[mjl]

Ok, thanks, I'll clean them up a bit and then you can yell at me for how ugly they are ;-)