Single page apps in depth (new free book)

I was expecting the book to be on a single page

Gave this a quick skim, matches with a lot of what I've been thinking lately. I particularly like idea of isolating modules from the DOM so they can be tested in the CLI-- could also enable reuse on server &#38; client.<p>Look forward to reading the whole thing tonight.

I'v did some single apps. * <a href="https://trakrapp.com/" rel="nofollow">https://trakrapp.com/</a> (server's certificate has expired) an issue tracking app. with Backbone, Jquery. * <a href="http://mei.fm/create" rel="nofollow">http://mei.fm/create</a> Wwn's online stack editing app. (need to signin to get full functionality). A team structure the code with the help of Jquery, Mustache.js, Underscore. * <a href="http://rssminer.net/demo" rel="nofollow">http://rssminer.net/demo</a> .yet another RSS reader. I write it with Jquery, Mustache.js, Underscore.

This is quite nearly the PERFECT book, one that every web developer should read front to back.

Don't call this a 'book'. I know it is a great plug but it is simply not true.

here is my single page app www.cardivvy.com<p>its simple app using api to get list of car2go available cars, parking spots, with a simple Google Map mashup.<p>it isn't DOM-&#62;Model-&#62;View structure. its simple call to api to retrieve json using php and javascript and php/html presentation.<p>any generalized suggestions about how to do this as DOM-&#62;Model-&#62;View structure?<p>where does the api call fit? in DOM

thanks for the book! currently reading it on my kindle and really enjoying it!<p>is there any possibility to donate or contribute?

I'm a little skeptical from my initial skim of this.<p>His attacks on using the DOM to store information make me think he's never know the joy of a clean data-binding setup.

This is my preferred solution to single page apps:<p><a href="http://www.enyojs.com" rel="nofollow">http://www.enyojs.com</a>