• Statt: EUR 28,49
  • Sie sparen: EUR 0,01
  • Alle Preisangaben inkl. MwSt.
Nur noch 6 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Gebraucht: Sehr gut | Details
Verkauft von Warehouse Deals
Zustand: Gebraucht: Sehr gut
Kommentar: Gebrauchsspuren. Kleiner Fleck oder geringe Abnutzung auf der Vorderseite. Kleine Falte oder kleiner Knick auf der Vorderseite. Amazon-Kundenservice und Rücknahmegarantie (bis zu 30 Tagen) bei jedem Kauf.
Ihren Artikel jetzt
eintauschen und
EUR 6,25 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Alle 2 Bilder anzeigen

Ember.js in Action (Englisch) Taschenbuch – 23. Juni 2014


Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Taschenbuch
"Bitte wiederholen"
EUR 28,48
EUR 21,92 EUR 21,93
11 neu ab EUR 21,92 4 gebraucht ab EUR 21,93
Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


Produktinformation

  • Taschenbuch: 240 Seiten
  • Verlag: Manning Pubn; Auflage: Pap/Psc (23. Juni 2014)
  • Sprache: Englisch
  • ISBN-10: 1617291455
  • ISBN-13: 978-1617291456
  • Größe und/oder Gewicht: 23,2 x 18,8 x 0,9 cm
  • Durchschnittliche Kundenbewertung: 5.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)
  • Amazon Bestseller-Rang: Nr. 127.359 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Über den Autor und weitere Mitwirkende

AUTHOR BIO Joachim Haagen Skeie is an experienced web application developer and the author of EurekaJ, an Open Source Application Monitoring tool built using Ember.js.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Kundenrezensionen

5.0 von 5 Sternen
5 Sterne
1
4 Sterne
0
3 Sterne
0
2 Sterne
0
1 Sterne
0
Siehe die Kundenrezension
Sagen Sie Ihre Meinung zu diesem Artikel

Die hilfreichsten Kundenrezensionen

Format: Taschenbuch Verifizierter Kauf
Wenn nur alle Fachbücher so gut geschrieben wären! Anhand einer Notizanwendung steigt der Autor sofort in die Konzepte von Ember ein. Das Trivialbeispiel demonstriert die wichtigen Aspekte einer Anwendung, wie das Erstellen, Ändern, Auswählen und Löschen von Daten. Der Autor bleibt dabei fokussiert und erklärt zielführend deren Umsetzung anhand von Controllern, Templates, Routern & Co.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 10 Rezensionen
9 von 10 Kunden fanden die folgende Rezension hilfreich
It's OK 19. Juni 2014
Von Greg Turner - Veröffentlicht auf Amazon.com
Format: Taschenbuch
Glad to have a book on Ember.js and anyone who wants to learn Ember.js should probably get this book despite my 3 star rating. I am giving it only 3 stars and not 5 because the example code is poorly laid out and some explanations are very confusing.

Some examples:

1. The example code for the Notes application is poorly laid out. The Notes app is discussed in chapter 1 and 2. The example code is laid out in 5 levels, with 1 being a simple Hello World and 5 being the finished app. In the two chapters, no mention is made what-so-ever about what level the author is currently on. This was very confusing.

2. The author made the poor choice of using the word 'Notes' as the name space for the Notes app. Thus in the text the reader is expected to think through text such as 'the Notes Notes.NotesNoteRoute does ....'. Sheesh

3.On page 18, in a section explaining the NotesRoute, all of a sudden the author is writing about the NotesController and the Local Storage Adapter. Huh???

4. On page 18 is this phrase, "Inside the notes route, you'll include an input text field and a button..." Ah no. Those two things are included in the notes template, not the route. Ember.js has a steep learning curve and this kind of thing is going to be very confusing to people just starting out with Ember.js.
4 von 4 Kunden fanden die folgende Rezension hilfreich
Not for Ember newbs 16. Juli 2014
Von Al Krinker - Veröffentlicht auf Amazon.com
Format: Taschenbuch
I was really excited to read this book since Ember is getting speed and I see more and more apps that are written in it.

Like other readers, I got confused right from the start... I feel that author has great knowledge of the subject, but he does not seem to break it down to small pieces that new user of Ember would be able to digest. Right from the start, he provides a lot of code and in my opinion, line by line explanation was not very good since he would assume you know most of it and would just focus on main parts of it. Better line by line explanation would have been great.
Plus, in my great disappointment, when I pulled code from the github account, a lot of code was broken and a lot of code did not match what was in the book! When you are learning new technology it can be very frustrating experience when "Hello World" app wont even work for you.
That's the primarily reason, I gave the book 3 stars, I feel that if the code was clean, it would be solid 4 star book. Since the code is in github, I would hope that the author of the book would be able to easily fix all those issues and do some testing against different browser version(s). (or at least provide a list of supported browsers, etc). In addition, author seemed to jump around a lot between different concepts and different projects that he introduced in his book. He would refer to something and then say that it would be explained later in the book. So you would take a lot of stuff as is and hope that it would make more sense later... I personally feel that I have to be explained everything that I need to know before proceeding to the next step. So it also added to a confusion.

Since a lot of code was left out unexplained, I started to look through Ember online guides and Ember API to get me fill in the gaps. Then I was able to better understand the concept since like I said before, author knows Ember really well and introduces some cool concepts and tricks.

Bottom line, I would highly recommend reading Ember online guides on their website and going through Ember API and basic projects offered for free before reading this book. I would say this book is meant for someone with basic Ember experience to get intermediate/advance knowledge. Solid book for people with basic ember skills tyring to learn more.
2 von 2 Kunden fanden die folgende Rezension hilfreich
Book has potential, but fails to deliver 23. Juni 2014
Von David L - Veröffentlicht auf Amazon.com
Format: Taschenbuch
Unfortunately, this book's poor quality undermines what could be a successful framework.
Ember.js seems to be a very well-designed framework. This book discusses and may demonstrate features that are missing from other frameworks, but it is almost impossible to verify because the two example applications from GitHub don't work. Worse, the example code doesn't match code listing in the book.

Verifying that the examples from the a book exist, can be deployed, and function at least somewhat like the book claims, might be a good idea. Manning? The author may have had good intentions, but this book is not finished. The following text is ironic given the book's state:

"Even though JavaScript has matured significantly over the past five years, in a couple
of areas you’ll notice that you’re working with a project that still has some
maturing to do. Testing is one of these areas ..."

The "It's OK" review is accurate on all four example points. The book and code are hard to follow.

There are three separate repositories for code from the book. Chapters 1 and 3, and two larger applications.
For the application chapters, listings are labeled by chapter and number, but that won't help you find the code. You have to search for code that's similar. Here's one example:

// listing in book

Emberfest.Router.map(function() {
this.route('tickets');
this.resource('talks', function() {
this.route('talk', {path: "/talk/:talk_id"});
});
this.route('schedule');
this.route('venue');
this.route('organizers');
this.route('sponsors');
this.route("registerTalk");
});

// code from EIA branch repository

Emberfest.Router.map(function() {
this.resource("index", {path: "/"}, function() {
this.route('tickets');
this.route('talks');
this.route('schedule');
this.route('venue');
this.route('organizers');
this.route('sponsors');
});
});

It appears that the author provides an early version of project code, but the book discusses code as the application evolves. You really can't tell. Code and discussion for the EmberFest and Montric applications are similar to the Notes application, but instead of providing several snapshots of application code, you get an early snapshot and then code listing from undetermined points in development. It's like a puzzle with missing pieces.

The GetHub site states there is a Live Demo: [...] ( - connection timeout )

One readme.md states: "You need to install Perst into your local Maven Repo. Download from [...]". But apparently you don't - the Ember Fest project (EIA) doesn't use that database. The instructions for installing and running the example code are incomplete, wrong, or missing.

A well-designed and feature-rich framework should be easy to learn. The current state of this book fails to deliver. Fixing all the errors and aligning the source code would be a nice start for the 2nd edition.
2 von 2 Kunden fanden die folgende Rezension hilfreich
... that writing a book on Ember is not an easy task - I'm sure this will slow down eventually ... 8. August 2014
Von R. Lauer - Veröffentlicht auf Amazon.com
Format: Taschenbuch
Let me begin by saying that writing a book on Ember is not an easy task - I'm sure this will slow down eventually (and already has to some extent), but Ember.js was evolving very rapidly not too long ago. Large changes were still being made, old features were being deprecated and replaced by newer, better features. However, an author has to pick a version and stick with it; Otherwise the book will never be finished. The author's examples were written with Ember 1.0.0, but at the time of this writing, Ember is on version 1.6.1. Maybe I'm wrong on this, but I think it would have served the author better to wait until Ember stabilized more.

As others have pointed out already, the main flaw in the book was the code samples. When you're writing a technical book and posting code to GitHub, it is imperative that the code matches what's in the book, and more importantly, that the code works. It is very frustrating to try to follow along with a book, but to have different code than what's in the book, or to have code not work.

I think the author took on a difficult task - Ember is one of the most comprehensive frameworks out, which means there is a lot to cover. Unfortunately, I feel the author fell short in a few places. It's not a terrible book by any means, but it certainly could have been better.
Good real-world use cases and background information but not a tutorial 26. August 2014
Von Jacob Quant - Veröffentlicht auf Amazon.com
Format: Taschenbuch
Disclaimer: Manning Publications was kind enough to give me a review's copy of the book, but I will do my best not to let that influence my review.

Some have commented that the code in this book is confusing. As one new to developing with Ember.js I have to agree at least somewhat. But I think part of that is because the learning curve is relatively steep and seeing some snippets of code in a book is not a natural way to get comfortable with all the concepts. However, I believe it is worth the work as Ember.js provides a wealth of well-thought-out features and good conventions. For that reason, if you decide to read this book I highly recommend that you visit the publisher's site and follow the links to companion site (or search github for Ember.js-in-Action-Source). It is much better to read this book while sitting with a computer where you can try things out or look-up more information rather than on a bus or in some other constrained environment.

Some things I liked about the book:

* Each chapter starts with a shaded block diagram indicating which parts of Ember.js are about to be discussed. This is nice because it helps demystify how Ember.js is itself designed. Knowing how its constituent parts work together makes it feel a lot less like black magic. In fact, this book has good diagrams in general. For another example, the model relationships in chapter 5 were quite helpful.

* It draws attention to places where Ember.js is doing something automatically so that you know where to look if you want to modify the default behavior.

* Illustrates Ember's MVC model in detail including how ember-data syncs the models of the client and server (i.e. using a RESTful web service) and explaining the steps in the router lifecycle.

* It shows how to use some additional open source software together with Ember.js in practical situations (e.g. using Persona for authentication)

Some things I disliked about the book:

* It seems to jump from one topic to another rather abruptly. I think this is probably because the author wanted to give a taste of many ideas without making the book too long. If you're the type who want to achieve mastery of one bit of subject matter before proceeding to the next then I'd suggest supplementing the book with not only the online resources from the author but also with material from the emberjs and emberwatch websites.

* The text between code listings felt too short to me. I understand that it is usually helpful to split large chunks into smaller ones but I think in this case it would often be helpful to have a longer text introduction / roadmap before diving into an undertaking.

All in all, it was worth reading, I learned some things, and the content is unique (not just a rehashing of other resources such as tutorials online), but it wasn't an easy read and probably won't have much reference value for me.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.