On 6/3/07, itsnotvalid <[EMAIL PROTECTED]> wrote: > > As far as I know there isn't much a way to replace the default > template system with another third-party one (except by extensive > hacking).
100% incorrect. There is nothing forcing you to use Django's template system. HttpResponse (the class that a view is expected to return) wraps content contained in a string; you can use any technique you want to generate that string, be it Django template, or any other engine. True, some of the shortcuts (like render_to_response) won't work with other template engines, but they are generally very light wrappers around HttpResponse. Writing your own shortcuts for your own engine is trivial. The admin application is also restricted to using Django templates, for obvious reasons. However, if you want to use your own template engine, just import it and use it when generating content. We (the core devs) like the Django templates - if you don't, it's entirely your decision. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
