> It's a generic templating language, it's not particularly geared toward HTML. > It's no HAML (you'll still get to write all the HTML yourself), but writing > custom tags is much easier than with Django. Also, it compiles templates to > Python code, which makes it reaaally fast.
fast is always good. > The issue is that views of third-party apps will use Django's stock > render_to_response, which will use Django's standard templating system, > which will mean you'll get to maintain templates in two different templating > languages. > > If you don't need third-party apps, this is not a problem (though it removes a > lot of Django's appeal in my opinion). Not sure yet, I'm just playing with it - but it's probably safe to assume I will someday in the future. Plus the GHRML page wasn't updated in about 13 months... So it's probably dead. Thanks, Shilo. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
