[ 
https://issues.apache.org/jira/browse/SLING-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850265#comment-15850265
 ] 

Brenn Hill commented on SLING-2919:
-----------------------------------

[~olli] This doesn't really solve the underlying desire for handlebars:  A 
template engine that works for both modern FE dev (usually node.js powered with 
stuff like gulp/grunt doing CSS compilation, sprite building, etc) that ALSO 
works natively inside Sling.  

And it's doable: we have it working right now and the workflow is GLORIOUS.  

https://github.com/phornig/sling-handlebars

This is what it is based on, already Apache 2 licensed.  It would be trivial to 
add this to Sling officially.  My company will be releasing our updates soon 
which include a number of extra helpers and AEM 6.2 support with service users 
for handlebars.

> Support handlebars as a scripting language
> ------------------------------------------
>
>                 Key: SLING-2919
>                 URL: https://issues.apache.org/jira/browse/SLING-2919
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>            Reporter: Ian Boston
>            Assignee: Ian Boston
>
> Handlebars.js is a popular scripting language used client side. The markup is 
> simple and straightforward, much like velocity in some ways, but without any 
> of the confusion ove template or MVC. There is a version of Handlebars for 
> java that uses an identical template language and appears to be well 
> supported and has some nice features such as pre-compiling scripts serverside 
> into Javascript functions and modules. (not all that relevant for server side 
> scripting, but interesting none the less).
> I am going to experiment with a Sling Script engine in the whiteboard area to 
> see if its viable to use handlebars java as an alternative to JSP.
> Handlebars Java, A2 Liencesed: https://github.com/jknack/handlebars.java



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to