Malcolm Tredinnick wrote: > I want to hear the use-case first. I may change my mind, but nobody's > come up with a good reason so far.
How about looking at things from the opposite direction? Yes, it would be nice if the Django template system could be more easily used standalone, but by doing this it would also most probably allow Django to plug in other template engines more easily. This feature could be a deciding factor for folks who would use Django "if only I could use my favorite XML-based templating system" or those switching from another framework with existing templates that they wouldn't want to totally rewrite. Also, food for thought, it seems that the "merger" of TurboGears and Pylons [1][2][3] sparked the creation of the pytemplates google group [4], where interested parties have been talking about creating a standard API with plugins for various template engines. Gary [1] http://compoundthinking.com/blog/index.php/2007/03/05/merging-turbogears-and-pylons/ [2] http://www.oreillynet.com/onlamp/blog/2007/06/python_web_application_framewo.html [3] http://www.blueskyonmars.com/2007/06/27/turbogears-2-a-reinvention-and-back-to-its-roots/ [4] http://groups.google.com/group/pytemplates --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
