aliebling
commented
9 years ago In theory totally possible, but definitely not trivial if you want to support more than the basic markup. Our experience is that the basics are easy, but there's a ton of nuance and little bugs (for example, based on different formatting) which take a long time to squash,
Honestly, if I were working from scratch and had the option, I'd go for a templating system which supported both natively, like Google Closure Templates - https://developers.google.com/closure/templates/.
Good luck!
Aaron
On Thu, Mar 26, 2015 at 8:44 PM, Jovica Aleksic notifications@github.com wrote:
Hi This is rather a question than an issue. Is it possible to do the conversion the other way around: freemarker templates to handlebars? If so, how would you describe or estimate the required effort for such an implementation? This would allow sharing templates with a limited feature-set between server and client, for example using a Rest interface. In my specific case, I would like to build a rather large javascript app on top of a Magnolia CMS. After initial rendering by Magnolia, new data and probably the relevant templates would be loaded into the JS client via Ajax and rendered by its view layer.
— Reply to this email directly or view it on GitHub https://github.com/cnojima/grunt-hbs2ftl/issues/4.
loopmode
Hi This is rather a question than an issue. Is it possible to do the conversion the other way around: freemarker templates to handlebars? If so, how would you describe or estimate the required effort for such an implementation? This would allow sharing templates with a limited feature-set between server and client, for example using a Rest interface. In my specific case, I would like to build a rather large javascript app on top of a Magnolia CMS. After initial rendering by Magnolia, new data and probably the relevant templates would be loaded into the JS client via Ajax and rendered by its view layer.