4 ms·
I've been contributing to another HAML derivitive for python called HamlPy (https://github.com/jessemiller/HamlPy https://github.com/jessemiller/HamlPy). It com
by dmclain 16y ago
I've been contributing to another HAML derivitive for python called HamlPy (https://github.com/jessemiller/HamlPy https://github.com/jessemiller/HamlPy). It compiles down to Django templates, which made it very easy for me to convert my existing project. It's under pretty active development right now.
- raineri 16y agoI forked that project and made it compile down to a Mako template (I use pylons). https://github.com/raineri/MakoHaml https://github.com/raineri/MakoHaml :)
- true_religion 16y agoYou might want to update your readme file so everyone knows that it compiles down to Mako just at a glance. Right now its confusing. But if I'd known about this project a few days ago, you'd have definitely been added to my list of Muses. Also, does your fork support the full range of Mako control structures? Looking at the nodes.py it seems that its still targeted towards a Django-templates backend.
- raineri 16y agoYeah, I quickly hacked it together, I will update the readme soon. It does support the mako control structures. You see them rendered around line 200 in nodes.py.
- true_religion 16y agoYou forgot to change the list of self-closing tags. I'd suggest making 'while' self closing. How do you handle Mako defs, and namespace tags?
- true_religion 16y agoYou can actually use Nemo alongside Django-templates. It registers a Mako template loader with Django, that by default points to your /templates directory in your folder. However you can override it by modifying MAKO_TEMPLATE_DIRS in your settings.py. MAKO_TEMPLATE_DIRS is just a tuple containing the directories to look under for Mako/Nemo files. My full project runs under Mako, but 3rd party apps, and the django admin run with django-templates.