Single Page Web Applications (Anglais) Broché – 26 septembre 2013
|Neuf à partir de||Occasion à partir de|
Produits fréquemment achetés ensemble
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Présentation de l'éditeur
ABOUT THE TECHNOLOGY
A Single Page Application (SPA) is an application delivered to the browser that does not reload the page during use.
Biographie de l'auteur
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur les auteursDécouvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.
Dans ce livre(En savoir plus)
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Meilleurs commentaires des clients
Bien sûr la partie client s'exécutant au sein du browser, qui sera familière à tous les développeurs web.
Mais surtout il offre de très bonnes introductions à Node.js et MongoDB.
Pour ceux qui ne connaissent ni l'un ni l'autre ce livre est un excellent point de départ.
Pour les autres le livre reste quand même intéressant en montrant une façon possible de les combiner.
Commentaires client les plus utiles sur Amazon.com (beta)
At the beginning of the book the authors state that "this book is not for you". You definitely need other references at your disposal, but even though I've only dabbled in web development, I'm definitely finding it useful. Hopefully I will be able to keep up with it as I get further into the book. I do have a degree in computer science though (from the prehistoric era of the Web - 1991).
I plan on updating this review as I work through the book, so stay tuned.
While all the tools that are introduced were appreciated and most of the tools work as advertised, getting JSLint off the ground didn't really happen for me. Still it's good to know it's there. Other smaller tips like HTML to JS concatenation macros for a text editor like VIM were efforts in futility, wasting a bit of time, and leading nowhere. Mobile touch compatibility was somewhat of an over-promise. It didn't shine in listings, and it was tough to test out on an actual device without pushing to production.
In general Single Page Web Applications In Action is a fun read. Almost like an adventure in its scope and structure--the way it builds into the final product from scratch. There's a lot of great material to take away for a range of skills and roles.
IMHO, here is the pros and cons of the approach taken by the authors for the client side of the example application (the most important part of the book in the context of SPA),
Just a couple of years ago, Knockout and Backbone were considered de facto standards for client-side MVC. Then, almost out of nowhere, came Angular, supported by Google’s seemingly infinite programming and marketing resources. But Angular is new and is still undergoing radical changes from release to release. As a result, documentation is often lagging and there are multiple ways to do the same thing: legacy approaches often co-exist with newer approaches, as if to see what sticks. Furthermore, each of these “automatic two-way data binding” frameworks requires the programmer to accept some rigidity in exchange for convenience.
In closing, here’s a sampling of some of the interesting approaches used in this book:
-The use of callbacks is reduced via the use of jQuery global custom events.
-The book recommends feeling a lot less guilty about using pixels since browsers have started implementing pixels as relative units and pixels are often more reliable than traditional relative units like em or percent.
-The book recommends testing views and controllers manually (although user interface (UI) testing automation frameworks have matured and I’ve had considerable success with the combination of Protractor, Jasmine, and AngularJS).
-The authors discourage the use of embedded template libraries like Underscore.js, but encourage the use of toolkit-style template systems such as those provided by Handlebars, Mustache, and Dust.