Single page apps in depth (new free book) (opens in new tab)

(singlepageappbook.com)

157 pointsmixu13y ago31 comments

31 comments

emilepetrone13y ago

I was expecting the book to be on a single page

callmeed13y ago

A book about woodworking doesn't have to be made of wood, does it?

shill13y ago

Actually, most woodworking books are made from wood.

2 more replies

kami884513y ago

No but there's always that little part of me that expects it to be.

kjbekkelund13y ago

There is a single page version: http://singlepageappbook.com/single-page.html

pfraze13y ago

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 & client.

Look forward to reading the whole thing tonight.

fshen13y ago

I'v did some single apps. * https://trakrapp.com/ (server's certificate has expired) an issue tracking app. with Backbone, Jquery. * http://mei.fm/create 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. * http://rssminer.net/demo .yet another RSS reader. I write it with Jquery, Mustache.js, Underscore.

cnp13y ago

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

rudasn13y ago

I haven't read through the whole thing [1], but I really like the fact that he actually discusses different approaches when trying to achieve a goal and instead of just mentioning them. He has an opinion and is not afraid to express it and that's good because it encourages thinking and discussion.

[1] Only read through http://singlepageappbook.com/detail1.html (on Views)

ssn13y ago

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

floptikal13y ago

It is not a book because...?

raphinou13y ago

I find the layout awful for a print version. And the PDF document has chapter links that lead to the website, rather than the page in the PDF.

I can live with that if I generate a PDF from web content, but I'd expect a book to have a better print version and a better quality PDF version...

1 more reply

ssn13y ago

What distinguishes a book is the 'form factor'. Obviously we are talking about an e-book. Nonetheless little care has been put into producing a 'book': not TOC, no index, no page numbers, etc.

(Obviously this is all independent of the content.)

2 more replies

cardivvy13y ago

here is my single page app www.cardivvy.com

its simple app using api to get list of car2go available cars, parking spots, with a simple Google Map mashup.

it isn't DOM->Model->View structure. its simple call to api to retrieve json using php and javascript and php/html presentation.

any generalized suggestions about how to do this as DOM->Model->View structure?

where does the api call fit? in DOM

zaphod198413y ago

thanks for the book! currently reading it on my kindle and really enjoying it!

is there any possibility to donate or contribute?

heretohelp13y ago

I'm a little skeptical from my initial skim of this.

His attacks on using the DOM to store information make me think he's never know the joy of a clean data-binding setup.

mixuOP13y ago

If you can get away with storing your data in the DOM, then go ahead. But this technique is mostly applicable to low-interactivity views (see the view layer overview chapter) - once you start displaying the same data in multiple locations, having your data tied to the DOM structure and state goes from being a easy technique to a complication. Hence I don't really consider storing data in the DOM as a single page app technique as much as an easy way to do low-end interactive components.

floptikal13y ago

I have never been a big fan of "easy" data binding, and totally agree that data is not to be stored in the html. Same reason why you don't use your kitchen table as the pantry...

jules13y ago

Isn't the point of data-binding that you don't store stuff in the UI, but instead store it in a model that you bind to the UI?

niels13y ago

I'd say databinding is useful for smaller convenience plugins, not for the architecture of larger JavaScript applications. From my quick skim this book is spot on.

heretohelp13y ago

It is your opinion that the answer to making a larger JavaScript application is one big bucket of state Object?

Tell me you've got something better than that.

3 more replies

rsanchez113y ago

This is my preferred solution to single page apps:

http://www.enyojs.com

j / k navigate · click thread line to collapse

31 comments

emilepetrone13y ago

I was expecting the book to be on a single page

callmeed13y ago

A book about woodworking doesn't have to be made of wood, does it?

shill13y ago

Actually, most woodworking books are made from wood.

2 more replies

kami884513y ago

No but there's always that little part of me that expects it to be.

kjbekkelund13y ago

There is a single page version: http://singlepageappbook.com/single-page.html

pfraze13y ago

Look forward to reading the whole thing tonight.

fshen13y ago

cnp13y ago

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

rudasn13y ago

[1] Only read through http://singlepageappbook.com/detail1.html (on Views)

ssn13y ago

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

floptikal13y ago

It is not a book because...?

raphinou13y ago

I find the layout awful for a print version. And the PDF document has chapter links that lead to the website, rather than the page in the PDF.

I can live with that if I generate a PDF from web content, but I'd expect a book to have a better print version and a better quality PDF version...

1 more reply

ssn13y ago

What distinguishes a book is the 'form factor'. Obviously we are talking about an e-book. Nonetheless little care has been put into producing a 'book': not TOC, no index, no page numbers, etc.

(Obviously this is all independent of the content.)

2 more replies

cardivvy13y ago

here is my single page app www.cardivvy.com

its simple app using api to get list of car2go available cars, parking spots, with a simple Google Map mashup.

it isn't DOM->Model->View structure. its simple call to api to retrieve json using php and javascript and php/html presentation.

any generalized suggestions about how to do this as DOM->Model->View structure?

where does the api call fit? in DOM

zaphod198413y ago

thanks for the book! currently reading it on my kindle and really enjoying it!

is there any possibility to donate or contribute?

heretohelp13y ago

I'm a little skeptical from my initial skim of this.

His attacks on using the DOM to store information make me think he's never know the joy of a clean data-binding setup.

mixuOP13y ago

floptikal13y ago

I have never been a big fan of "easy" data binding, and totally agree that data is not to be stored in the html. Same reason why you don't use your kitchen table as the pantry...

jules13y ago

Isn't the point of data-binding that you don't store stuff in the UI, but instead store it in a model that you bind to the UI?

niels13y ago

I'd say databinding is useful for smaller convenience plugins, not for the architecture of larger JavaScript applications. From my quick skim this book is spot on.

heretohelp13y ago

It is your opinion that the answer to making a larger JavaScript application is one big bucket of state Object?

Tell me you've got something better than that.

3 more replies

rsanchez113y ago

This is my preferred solution to single page apps:

http://www.enyojs.com

j / k navigate · click thread line to collapse