changes: MultiValueField instead of DecimalField and fix #8

If you want to use localisation for the form field, you'll run into an `ValueError`: too many values to unpack
This happens due to the fact, that django's `DecimalField` will use a `TextInput` rather than a `NumberInput` if `Field.localize` is set `True`.
In this case, the default value must be a `String` rather than a `Float`.
changes: MultiValueField instead of DecimalField and fix #8

If you want to use localisation for the form field, you'll run into an `ValueError`: too many values to unpack
This happens due to the fact, that django's `DecimalField` will use a `TextInput` rather than a `NumberInput` if `Field.localize` is set `True`.
In this case, the default value must be a `String` rather than a `Float`.

Revert "l10n fix for MoneyField"

This reverts commit 1911017c53f3d1685ca7185129bca27a634b9ff9.

fixes form field issue

Django’s from `SelectField` excepts a list of touples, it got passed a
list of `Currencies`. This should now allow to use from `MoneyField` on
it’s own.

adds l10n to form MoneyField

this adds support for the localize argument, as it doen’t work on when
a widget is passed

changes: Text- to NumberField

‘DeciamFields’ usually use ‘NumberInputs’. This also allows i10n input.

adds support for non i10n

changes: to MultiValueField instead of DecimalField

This is a more ‘django’-like approach. I use existing fields and there
widgets rather than creating them all.
This works well and reduces the code size and intreduces real l10n.

adds: option to swap the currency widget

updates: tests

updates most tests to proper generation for multivalue fields.
It also adds new tests.

PEP8

makes whole code PEP8 complient

fixes: test for django 1.6

Django 1.6 returns a input type number by default. If localize=True it
returns type text.

Revert "PEP8"

This reverts commit 43da78eff73ef0f70fa1b2e4f6ab79d4d92f3535.

deprecates: rendering test

add test of readonly_fields to test project