Allow floppy-forms to override as_table, as_p and as_ul about django-floppyforms

[brutasse]

Yes, templates!

In my projects, I just don't use the as_* methods. I have a template that iterates over the form and renders it using

tags, or divs, or whatever. For instance: https://gist.github.com/789448

This way, you can create several templates with several rendering strategies, all you need is to include the correct template.

So, I'm not sure any sort of modification of the form class is required... What do you think? Maybe the docs should encourage the use of templates instead of Form.as_*, but this technique is already explained in the Django documentation.

[poswald]

Yes, Django has this pretty well documented in the forms section. I assume you call your form from the template with that include statement:

 {% include "form_snippet.html" with form=comment_form %}

I was thinking of making the as_* method override as a way to ensure existing code could be ported with a simple import change and make sure everything is using the same templates. I suppose it's not strictly necessary.

[brutasse]

Oh I see, you want to replace every bit of Django code that generates HTML with string interpolation :)

I understand your point though, providing a way to define / customize Form.as_something would be nice. I'll put that in the "nice to have" features, when all fields and widgets from Django have a floppyforms replacement.

[Natim]

That's it, all fields and widgets from Django have now a floppyforms replacement :)

[maraujop]

I believe this problem is widely solved by django-uni-form and you can use it in conjuction with floppyforms without problems.

[brutasse]

#35 has been merged, as_* now use templates :)