Hi Jimmy,

We have just released a new version of PURE, including new features such as :

Auto-rendering: a new PURE method takes your HTML and your JSON data and merges them automatically. The class attribute is used to map the HTML and the data.

Recursive Template Call

The changes are quite important.

We took back your example and changed it to fit with the new release.

The code source can be seen below and as you will see, it is really easier :

http://friendpaste.com/FSBbhtb5

I have a zip file for you with the example if you contact me directly.

I am actually don’t call chain.js a templating engine, it is rather a data binding service.

by the way you’re asking about more advanced example, so I created it here:
http://code.riiv.net/demos/tree/

best regard, Rizqi

I understand the initial dislike for ${} tags in the HTML. They are after all not HTML. However, they do serve the function of being easier to use. An alternation tag %{odd:even} replaces in a few characters what would normally take many lines of javascript to accomplish.

I built this library in order to make it easy to use. Changing layout in HTML is much easier than changing it in javascript. If there is anything I can offer in their defence it would be that ${} markup is declarative in the same way that is declarative whereas javascript if functional.

@Risqi – Thanks as well for having a look at the jsRepeater library. I had a look at the library you mentioned and appreciate the similarities although I did baulk at explicit ‘for’ loops in HTML markup. I think of HTML as being declerative whereas a ‘for’ loop in HTML did seem to be a bit of a mix of metaphors.

You mentioned that your project, while being eay to use in the beginning, suffered from scaleability issues. Do you have any examples of these, prehaps a particular example in which templates using innerHTML could not rise to the challenge? I would appreciate it if you could post it so that we could all benefit from the lessons you learned. (I tried to open the demos at http://github.com/raid-ox/interaction.js/wikis/demos but IE7 died on all the example pages with the error ‘Operation Aborted’, damn IE!, unfortunately we can’t ignore it).

Keep up the good work!

I have also been looking around for templating solutions. I want to have to write as little javascript as possible and wanted a solution where all the heavy lifting is done in the HTML. Let’s face it, it’s easier to change HTML than to write javascript to create HTML.

None of the templates I have found do all the things I wanted e.g. more than one alternating template, nested templates, specifying which part of the object you want to bind to, and importantly; being able to bind recursively without having to specify a subtemplate for each level down.

So I wrote one. I have made it available as an opensource jquery plugin.

Perhaps you might find it useful as well.
http://jsrepeater.devprog.com/

but I think, there are still some missunderstanding about the way chain.js should be used . If I release the v0.2, would you please update this article? (Only if you want).

@Shawn
This is not about templating, but about managing data efficiently and more importantly scaling! You can write a simple code first, and extending it as it is required. For example, chain.js is so extensible that you can extend it to provide useful interaction service as can be seen here: http://github.com/raid-ox/interaction.js/wikis/demos

Actually I wrote similar library two years ago, called zparse: http://code.riiv.net/zparse/ . But using string based templating and innerHTML, makes your code too limited, not enough flexibility.

Of course jsrepeater is very efficient and easy, but as your code grow and grow, jsrepeater can’t provide the flexibility that is required.