I’m a huge fan of ajax requests which simply return json, letting the client decide what it wants to do with the data. Formatting that data into html client-side, however, has always felt ugly as sin to me. So, we revert to rendering the html on the server and sending that html as an ajax response. This model is fine for simple pages, especially when all we want to do is display data asynchronously. Once we want to interact with this new data, do calculations on it, manipulate it further, things start to get ugly. In the end, I strongly believe that when the client requests data via ajax, it should get data, and not display logic, back.
Say I have a list of todo actions (which may have been returned via json from an ajax request)
and a container
I want to render checkboxes and labels for these todos in the container, like this:
Let’s see how this looks.
Pretty ugly. It’s impossible to see the actual html structure at a glance. Of course it might look cleaner with document.write’s, but that’s an incredibly inflexible solution not to mention the fact that constructing a long string to display html is still gross.
Better. Cleaner. Easier to write. Still hard to see the actual html structure.
Nice right? A good separation of logic and display. Easy to see the structure of the html at a glance. (Note that I replaced script with scrip-t just to trick the gist syntax highlighter into recognizing html here. You don’t really use a scrip-t tag!)
Pretty good too. icanhaz builds in the idea of loading html from a script tag, so you don’t need the boilerplate code to get it’s html using jquery and compile a template. I actually prefer the flexibility of handlebars’ method more, though.
Pretty similar to handlebars. I do like that as a jquery plugin, we get no scope pollution.