News for hackers. Stuff that matters.
Re:Stop sending template engines to the browser. How to make... by dochtman on Friday September 14, 2012 @02:45AM (#4520405)
I've written a Jinja-to-JavaScript compiler:

https://bitbucket.org/djc/jasinja

It reuses the Jinja front-end, it really only replaces Jinja's code generator and supports a pretty large subset of Jinja. I think this is particularly great because it allows you to switch from server-side template rendering to client-side rendering of templates piecemeal, or use both with the same templating language.

Re:Stop sending template engines to the browser. How to make... by masklinn on Friday September 14, 2012 @07:17AM (#4521083)
That's kinda neat. I assume it only supports built-in filters and control structures?
Re:Stop sending template engines to the browser. How to make... by dochtman on Friday September 14, 2012 @09:22AM (#4521466)
The compiler output looks roughly like this:

  var Jasinja = {
    "filters": {
      "attr": function(obj, name) { return obj[name]; }
    },
    "tests": {
      "lower": function(val) { return val.toLowerCase() == val; }
    },
    "templates": {
      "test": {
        "macros": {},
        "blocks": {},
        "render": function(ctx, tmpl) {
          return "a";
        }
      }
    }
  };
So you can easily add some filters by setting Jasinja.filters['myfilter'] to a function.