I agree that something like this is becoming more necessary, as I ran into this a few days ago myself. Funny how similar our strategies were (David's is more robust): http://gist.github.com/629508
-Eric Florenzano On Oct 19, 10:24 am, David Gouldin <dgoul...@gmail.com> wrote: > As client-side templates become more popular, it is increasingly > likely that django's template language will not be the only one > present in a template. (jQuery's new template language makes frequent > use of curly braces in its syntax.) At the same time, the assumption > that all template syntax should be parsed and rendered on the server > should be questioned. > > I've created an effective albeit gross hack of a template tag to > accomplish this goal: > > http://gist.github.com/634534 > > I understand this can already be accomplished with {% ssi %}, but the > absolute path requirement and need for a separate file for even the > smallest bit of client template syntax is a turn-off to me. A > template tag in the same vein as {% autoescape %} and {% comment %} > seems a much more straightforward way to tackle the problem. > > Thoughts/opinions? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
