This is an enormous jump forward in the project, and I think you'll like what has been done and who contributed.
Some notable changes
- As of this release, there is now a formal django-uni-form release on PyPI that fully supports Django CSRF tokens.
- Better error messages to help you debug. No more annoying Null messages on bad helpers!
- The Python code has been carefully cleaned and optimized. Much easier to read, debug, and it plain runs faster on form heavy sites.
- Various improvements to the templates to better match the parent Uni-Form library.
- Only compatible with Django 1.2 or higher and Python 2.6 or higher. If you need something to work with other earlier versions of Django/Python, then I suggest using django-uni-form 0.7.0. Or better yet, upgrade your site!
- Much improved documentation on the awesome readthedocs.org site.
- Tons of other things!
- Upcoming faster release cycles. More on that in the next section...
Let's face it, over a year between releases is too long for any active open source project. I haven't done the incredible (and patient) django-uni-form community justice in supporting their issues and pull requests. This project has needed a much more active lead for some time. Fortunately, I found a new project in the way of Miguel Araujo.
Miguel Araujo shares my passion for good form generation and has a very deep understanding of Python, Django, and HTML. Also, his decisions on everything about this project either matches my own thoughts or he's been able to easily convince me why his concepts are sound. He is responsive to pull requests and issues, and his work is of high quality. So we should be seeing lots of releases and a better evolution of the system to match other advancements in the Django community.
So going forward Miguel will be the project lead for django-uni-form, and I'll be 'former project lead' and 'documentation donkey'.
The future of django-uni-form in the face of the forms refactor
Some people are wondering what place django-uni-form has in the face of the Django GSOC forms refactor by Greg Mullegger. Is the need for django-uni-form going away?
First of all, I actually have been pushing for a forms refactor in Django for some time. At the djangocon.us 2010 sprints Russel Keith-McGee, Django core developer and DSF president, asked my opinion on the design of a forms refactor. For the GSOC effort, I was delighted that the GSOC forms project followed the opinion that I preferred in how to doing things, and so I put in my non-binding vote for Gregor's approach. I'm rooting for you Gregor!
Second, while I think that while this library may change a bit to accomodate the eventual integration of Gregor's work, the need to be able to do guaranteed working Section 508 compliant layouts easily and more importantly make fancy layout changes in Python will keep this library alive and useful for a long time coming.
Whither goes the source code?
Finally, we'll be keeping the repo at https://github.com/pydanny/django-uni-form for the 0.8.x series so we have time to properly warn the community. When the forms refactor hits Django (prompting the necessary release of the 0.9.x series) we may be moving the library to its own github account.
I want to thank all the contributors, users, and anyone who gave me guidance or suggestions for this project. All the credit for this goes to you. I'm honored to have started something used by so many great people in so many wonderful ways.
This evolved from a Django beginner's shortcut filter to a rather sizable project with a great community. Due to my support of this project I learned git-scm, setuptools, JQuery, Sphinx, custom Django filters and templatetags, and more. I look forward to where it will go in the future with Miguel as lead.