{"action":"created","issue":{"url":"https://api.github.com/repos/ciscoheat/erazor/issues/18","labels_url":"https://api.github.com/repos/ciscoheat/erazor/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/ciscoheat/erazor/issues/18/comments","events_url":"https://api.github.com/repos/ciscoheat/erazor/issues/18/events","html_url":"https://github.com/ciscoheat/erazor/issues/18","id":86299896,"number":18,"title":"Project direction","user":{"login":"waneck","id":178171,"avatar_url":"https://avatars.githubusercontent.com/u/178171?v=3","gravatar_id":"","url":"https://api.github.com/users/waneck","html_url":"https://github.com/waneck","followers_url":"https://api.github.com/users/waneck/followers","following_url":"https://api.github.com/users/waneck/following{/other_user}","gists_url":"https://api.github.com/users/waneck/gists{/gist_id}","starred_url":"https://api.github.com/users/waneck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/waneck/subscriptions","organizations_url":"https://api.github.com/users/waneck/orgs","repos_url":"https://api.github.com/users/waneck/repos","events_url":"https://api.github.com/users/waneck/events{/privacy}","received_events_url":"https://api.github.com/users/waneck/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-06-08T19:26:43Z","updated_at":"2015-06-08T21:09:00Z","closed_at":null,"body":"Currently, while I like a lot and use erazor daily in my own projects, I feel that we lack a little direction or ownership about it at the moment.\r\n\r\nCan we use this issue to discuss that? I'd like to implement some extra features, and work on a better way to deal with escaping/raw, templating in general (following how razor does it), and better support for erazor macros. If no-one oposes to that, I propose that we release our current version as erazor 1.0, and start working on erazor 2.0 with these extra features - maybe breaking backwards compatibility.\r\n\r\ncc @fponticelli @ciscoheat @jasononeil "},"comment":{"url":"https://api.github.com/repos/ciscoheat/erazor/issues/comments/110141083","html_url":"https://github.com/ciscoheat/erazor/issues/18#issuecomment-110141083","issue_url":"https://api.github.com/repos/ciscoheat/erazor/issues/18","id":110141083,"user":{"login":"fponticelli","id":163915,"avatar_url":"https://avatars.githubusercontent.com/u/163915?v=3","gravatar_id":"","url":"https://api.github.com/users/fponticelli","html_url":"https://github.com/fponticelli","followers_url":"https://api.github.com/users/fponticelli/followers","following_url":"https://api.github.com/users/fponticelli/following{/other_user}","gists_url":"https://api.github.com/users/fponticelli/gists{/gist_id}","starred_url":"https://api.github.com/users/fponticelli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fponticelli/subscriptions","organizations_url":"https://api.github.com/users/fponticelli/orgs","repos_url":"https://api.github.com/users/fponticelli/repos","events_url":"https://api.github.com/users/fponticelli/events{/privacy}","received_events_url":"https://api.github.com/users/fponticelli/received_events","type":"User","site_admin":false},"created_at":"2015-06-08T21:09:00Z","updated_at":"2015-06-08T21:09:00Z","body":"First of all, feel totally free to ignore my comments if so you wish, I think that any innovation is better than no innovation. If we split the project the prefix thing is not a thing anymore because I could have my variation of the template engine that just uses my syntax instead of the erazor one.\r\n\r\nSo here is the idea for the split (why do I always want to split things?). First of all we define a nice AST format that supports the most features that templates might need (conditionals, literals, tags, attributes, expressions, plain text ...). With that we can build template languages that feed this AST (Erazor, Jaxe, thx.tpl, haxe.Template, Templo ...). We can do it with independent lexers/parser or we can also try to unify that effort maybe using hxparse. I already started that process for Jaxe with a custom lexer/parser but I would be glad to trash it. The third piece is how to consume the AST. The classic way is just to generate a method that take arguments and spits a piece of string (erazor, templo style). But the same AST again could be used for more interesting things like Virtual Dom changes (mithril style).\r\n\r\n"}}