I have just released 1.1 version of django-formfieldset. I has been almost a year since version 1.0. Here is a summary of changes for this version:
New Example Project
There is a new and improved example project. It is designed to be some sort of documentation at the same time. When you run the example project and visit different pages you will see, for each examle, Python code, template code, text of rendered result and finally the result embedded.
If you have Pygments installed all the code will be nicely highlighted.
Fieldset & FieldsetMixin Improvements
Fieldset definitions are validated now. An exception will be raised if all of your fields are not included exactly once.
Template strings that are used by as_table, as_p and as_ul methods are now class attributes. You can simply override them instead of writing your own as_* method.
FieldsetMixin provides a fieldset_dict attribute. This dictionary has slugified fieldset names as keys and Fieldset instances as values. Your fieldset declarations can still be accessed from fielsets attribute.
Rendering Improvements
There are two rendering related improvements: individual fieldset rendering and renderform template filter.
Fieldset objects have as_table, as_p, as_ul methods just like forms. Errors from hidden fields are handled correctly, but you still need to call non_field_errors() to get the top level errors. Also it is template author’s responsibility to make sure all the fieldsets are rendered.
If as_* methods are not enough for you, with renderform filter you can render your forms or Fieldsets through a custom template. It works like this:
{{ form.fieldset_dict.mytitlerenderform:"myapp/mytitle_fieldset.html" }}
If you call it without an argument formfieldset/form.html template will be used.
