2

following this post, I took a look at kanso.

From this I learnt that people are not afraid to load to the database context complicated modules if they need them, and that encouraged me a lot.

So I tried kanso. It gave me some trouble that implied immaturity - however, it demonstrateds a great potential. (mostly compatibiliy view with npm, with node 0.6.x, and some open edge-cases)

So I looked a little deeper. I saw it comes with a templates engine of it's own.

But what if I want to reuse templates that are written already by another standard? (for example - haml, or even better - jade that has also a nice text-to-text JS implementation, and a well growing jQuery plugin - same link - see end of document ).

Does anybody here know how coupled the templates engine with the kanso types mechanism, and how simple should it be to use other template engines instead? Or, what are the limitations I take upon myself when trying to use my own templates?

Community
  • 1
  • 1
Radagast the Brown
  • 3,156
  • 3
  • 27
  • 40

1 Answers1

1

As far as I can see in the source, DustJS (the template engine of kanso) is not pluggable (like in expressjs for example). That being said, it probably won't be that hard to plug in a different templating engine, the code doesn't seem very complicated.

You might want to add something to this issue on the GitHub page and request for a pluggable templating mechanism.

Jan Jongboom
  • 26,598
  • 9
  • 83
  • 120