[jira] Updated: (SLING-114) Sling Javascript Client Templates (was: Ecmascript Client Templates)

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated SLING-114:
--------------------------------------

    Summary: Sling Javascript Client Templates (was: Ecmascript Client Templates)  (was: ECT - Ecmascript Client Templates)

Renaming this issue to "Sling Javascript Client Templates" as discussed, suggest using that as the official name.

I'll rename things in code as well, and change to use the jst extension - (as in "jst do it" maybe ;-)

> Sling Javascript Client Templates (was: Ecmascript Client Templates)
> --------------------------------------------------------------------
>
>                 Key: SLING-114
>                 URL: https://issues.apache.org/jira/browse/SLING-114
>             Project: Sling
>          Issue Type: Improvement
>          Components: microsling
>            Reporter: Bertrand Delacretaz
>         Attachments: SLING-114.patch, SLING-114.patch
>
>
> To complete the javascript scripting features for microsling, I'd like to implement a client-side version of the ESP templates.
> A template such as
>   <p class="<%= item.color %>"><%= item.text %></p>
> Will be processed server-side to generate javascript client code such as
>   document.write("<p class=");
>   document.write(item.color);
>   document.write("\">");
>   document.write(item.text);
>   document.write("</p>\n");
> which executes on the client to render the content.
> Combined with a richer XHTML default rendering of data than what we have now, this creates interesting possibilities for ajaxish apps based on microsling/microjax (SLING-92).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.