Just to inform you that we have released a major version of PURE :

http://beebole.com/blog/2008/09/18/major-release-for-our-javascript-template-engine/

With features such as Auto-Rendering and Recursive Template Call.

You might be interested for your own two.js.

Thanks for putting up the link to your work. I just went over to the site to take a look at it. Your approach does get at some of the problems I mentioned, but you may want to look into my library called ‘two’ (discussed in more recent posts). two makes the full expressive power of javascript available inside the template and makes it easy to split the template up into many pieces (for assembling difficult documents and/or re-rendering sub-components as necessary). I’m working on a javascript-only datagrid that I hope will give a good example of how two can be used to build sophisticated documents.

I have tried this in a few different scenarios and can honestly say that it is easier to work with.

I have put is up, it is a free library that anyone can download, at:http://jsrepeater.devprog.com/

There are functional examples of it in use with the Google AJAX API at:
http://jsrepeater.devprog.com/google.search.websearch.example.html

It seems you are reading our mind.

The creation of PURE comes in the context of the development of our solution BeeLit.

Your two last reasons are what have driven us. Your first reason came nearly as a surprise to us when we finished PURE.

We have been working for years in SAP HR before the creation of BeeBole. We were building web apps on the tope of SAP.

We have always used the technique of the single page app. It was giving us a lot more flexibility when we had to integrate our apps in an SAP Portal for example.
With BeeLit, we will bring everything a bit further with the integration of the concept of automated Mashups in a SaaS offering.

Our idea is to bring the same ideas than Netvibes or iGoogle in a business app environment.

So, we will have in fact a one-page app in which mashlets will appear or not depending in which part of the application you are in.

Mashlets will auto-determine if they need to appear or not depending of the context and your role.

Also, mashlets won’t talk to each other directly but through some kind of listener/dispatcher utility.

In that context, it was also very important for us to be able to integrate data’s from different places as I am sure DB’s will continue to spread all over the place in the coming years.

Separating the data from the presentation has been done in that sense.
The cherry on the cake came later, when we realized that the separation was really good.

Now, as soon as the HTML is done, the rest becomes trivial. (We spend a lot of time on ergonomy and presentation).