Bertrand, 2 things I wonder about:
1. would it be better to produce output like: <p class=" document.write(item.color); "\">" document.write(item.text); </p> So that e.g. search engines could index the static parts? 2. Having the same templating language on client and server is nice, but maybe different delimiters would be a good idea. If the same ones are used we cannot combine server-side and client-side parts in one script. This seems like an unnecessary limitation to me. btw: reminded me of the TrimPath stuff now at http://code.google.com/p/trimpath/wiki/JavaScriptTemplates Cheers Michael On 11/29/07, Bertrand Delacretaz (JIRA) <[EMAIL PROTECTED]> wrote: > > > [ > https://issues.apache.org/jira/browse/SLING-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546652] > > Bertrand Delacretaz commented on SLING-114: > ------------------------------------------- > > Thanks for the hint, didn't know about that. I guess it's cool to have the > same templating language on both sides, we'll see how this works. > > > ECT - 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 > > > > 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. > >