Over at the Lawrence Journal-World, we have a bunch of custom template tags included in Ellington, our commercial CMS based on Django. One day, I finally got fed up with writing the same damned boilerplate code for custom tags over and over again (for parsing arguments, resolving context variables, etc.); the customtags library was the result. My wonderfully cool boss agreed to allow me to contribute this library back to Django.
customtags is a higher-level API for template tags that borrows much of its syntax style from the Django model API; it makes writing new template tags a breeze (if I may say so ^_^). I've been cleaning up the code over the past few days, making improvements, and writing documentation and tests; I'm not done, but I'd certainly like to get some eyeballs on the code ahead of submitting a final patch for inclusion into Django trunk. I've been maintaining the patch using Mercurial Queues; the most recent version can always be found at: http://hg.korpios.com/django.korpios.patches/file/tip/customtags.patch Again, documentation is still quite raw; it should be good enough to get a rough feel, though. The best "documentation" at the moment, though, might be django.template.defaulttags; I've rewritten every default tag as a customtags tag, with the exception of {% cycle %} (since cycle is something of an odd case). I'd appreciate any and all feedback, both positive and critical. :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
