Parsley 1.2 support

[tuxcanfly]

They've dropped the data- syntax and moved to parsley-

Maybe need to include some docs around this and a switch between <1.2 or >1.2.

[chachra]

agreed, not working as expected.

[treyhunner]

I don't think the attribute prefix should be hard coded because the prefix can be changed with the data-parsley-namespace form attribute or the namespace parsley option.

Maybe there should be a namespace meta option of an optional namespace keyword given to the decorator?

[tuxcanfly]

Good idea... on it.

[tuxcanfly]

Done. Meta attr parsley_namespace now provides the prefix which defaults to parsley and next version will ship with parsleyjs 1.2. What about people not using the app staticfiles? They'll face an issue when django-parsley > 0.2 but parsleyjs < 1.2...

[coveralls]

Coverage increased (+0.04%) when pulling 4beca9a on parsley-1.2 into 1438f31 on master.

[tuxcanfly]

I think we can put down a note in the docs on how to work with parsleyjs < 1.2.. specifically to set parsley_namepsace = data

[shabda]

@tuxcanfly : Shouldn we default parsley_namepsace = data if not set to maintain backwards compatibility? (And update docs too),

[tuxcanfly]

@shabda parsleyjs itself is not backward compatible so I guess it can't be helped.

[coveralls]

Coverage increased (+0.04%) when pulling 502208c on parsley-1.2 into 1438f31 on master.