Beginning AngularJS 1st ed. Edition

I bought this e-book due to I found the other book that I bought was really hard for me to keep reading it. And I'm so glad that I have this one, easy to read and samples are almost all working as what the author said. But just a reminder for people who also want to read this book: due to the author used version 1.2.9 of AngularJS which became an old version now, if you want to use any version newer than that, you should be aware there is a little difference between those versions. For example, in code listing 2-1, the author just put ng-app without giving it a name in the html tag, this made that sample doesn't work as expected. So I checked the official tutorial on AngularJS website and changed that code into ng-app='myapp', then in the following script section declared 'myapp' as an angular.module, then the code worked. Except this little trouble, all the rest samples in this book works just fine.

I expected read more about foundation of AngularJS, module, services, constant, factories, providers, i mean the “abc” of AngularJS. That thing you need to feel comfortable with this new approach.The first chapter is really unnecessary, and other parts to, because most developer already have strong knowledge in JavaScript, HTML, CSS, Forms, so on. I say this because AngularJS is a Framework, is like deep sea, you not start learn to swim in deep sea.There are random parts you can get some useful examples, to teach.

A few sample codes (after ch3) are not working in IE10 and 11.

Whole chapters of code don't work. Probably the worst programming book I have come across for code not working. The concepts are there but you really need some working code examples to back it up. I found the more advanced books were easier to get through since they had working code.

This is a book I really want to like and recommend wholeheartedly but it is plagued with some issues. I'll start with what I like and then back up what I just said with some details. The book is well written if you like a conversational approach to teaching (I do) and a gentle introduction that mixes in concepts with working examples (I do).I think the examples provided by the author are quite well contrived. For instance, the running example in chapter 4 regarding a fake set of data that showcases how to use filters is particularly effective. Overall, I recommend giving the book a read if you are learning AngularJS. It is a quick read, with good examples, and drives to the heart of AngularJS quite a bit more quickly than some other books out there.Now, however, on to the hurdles ...I have seen a few people reviewing how code examples don't work in this book. A lot of this may stem from early code examples. As just one example, the MVC code provided for example 3-3 and 3-4 (in chapter 3) will no longer work if you use AngularJS 1.3. The author was apparently using 1.2 and does in fact indicate that in the book -- even though 1.3 was stable by the time the book was written. (As the screenshots in the book show.)The problem is that AngularJS, starting from 1.3 on, no longer allows you to use a controller declaration on the global scope without explicitly registering the controller. That wasn't the case in AngularJS 1.2, which did allow this. The author does actually cover the more appropriate way to write AngularJS code by the use of modules. But that starts in chapter 4 (specifically, on page 68 of my book). The problem, of course, is that prior to this point, you would just be seeing code examples that don't work. To get the early examples to work you have to use that knowledge from later in the book and backport it to earlier in the book.To me, this shows exactly why books like this are sometimes problematic and why blog posts and other online resources are often a better way to go. Books simply can't keep pace with the development of these frameworks and libraries. In this case, the author wasn't wrong in the code he used initially. It's simply that the AngularJS team tightened up their restrictions a bit, rendering the early code non-working. With a blog post, you could simply update the code. With a book, you are out of luck. (If the author provided a GitHub site or some updated code repository, this would be less of an issue. More on that later in the review.)There are also code mistakes of a very general variety. For example, in listing 4-17, the author provides this:Full Name: {{ data.firstName + data.surname | toTitleCase}}In fact, that won't work for the example he is providing. What it needs to be is this:Full Name: {{ data.firstName + " " + data.surname | toTitleCase}}It's also the case that many of his later code examples are inconsistent or missing elements. A good example is listing 6-15, which shows a particular way that the author says he prefers for setting up a controller. This listing is missing a critical line. However, the author doesn't even follow this way that he says he prefers. In listing 6-17 we're back to the original way that the author provided. Yet another example is listing 7-7 which revisits a particular example from a previous chapter. Here the author shows this:form name="registrationForm" ng-submit="register()" novalidateWhen it absolutely should be this:form name="registrationForm" ng-submit="person.register()" novalidateThe addition of "person" is critical there. It was that way in the earlier example, but not in the later example. This kind of inconsistency is incredibly annoying.The author also does point out that his example from chapter 7 (which adds services to a previous example for a registration form) will not work as provided because it is relying on sending a post method. If you are running the examples in your browser via the filesystem (as opposed to on a server), that one particular example won't work entirely. And it's a pity because I do think it is a very good, concise example.Remember earlier I mentioned that an up-to-date code repo provided by the author could help mitigate the in-book code issues? Well, one other very annoying thing about the book, or at least the supporting material for it, is that the code examples provided on the Apress site -- such as for checking your code against that of the author -- are provided as Word docx files. Why someone would have a book about HTML and JavaScript (plain text file formats) and have the code examples provided as Word documents is utterly beyond me. That said, those Word documents have the same issues as the in-book code examples so in the end it doesn't matter what format they are.Even with all these really bad examples of code quality, I was -- believe it or not -- really torn with this book. I ended up judging the book based on the fact that I think the author really did choose his examples well and presented them well, at least in concept. While it's a matter of style, I feel too many authors are dry in their presentation and that wasn't the case for me here. I felt the author truly had an effective "written voice" that made me feel as if I was in a conversation. But the author apparently lacked a good reviewer who could have found some of the more obvious mistakes made in the code examples. After all, it took me a single read through to find this stuff. I have to believe a reviewer could have done just as well, if not better.In the end, I just can't recommend the book even though I genuinely did learn a lot from it. The problem was I had to spend more time correcting the author's code examples. In one way that did force me to learn some aspects even better, but it's hard to credit a book with a positive review based on that alone.

I used this book as a quick ramp-up on the basics of AngularJS.The good: after reading this, you'll have a basic understanding of modules, controllers, filters, directives, services (factories), form binding and validation, routing, and animation. It's short and can be read in a day. The chapter on JavaScript is sufficient, although basic HTML and CSS knowledge is required.The bad: no discussion of editors or IDE's; numerous typos; the chapter on services and server communication is really incomplete without at least a mock "server-side" layer to play around with; the chapter on deployment considerations is too brief to be very useful; and the code downloads are just the code listings in Word documents (!). I think beginners will actually have a tougher go at it than experienced programmers. Beginners should also be careful to use the 1.2.x version of AngularJS, some of the code examples won't work with 1.3.x.The author does know the material (it shows), and the book does provide a basic foundation. However, I can't really recommend it, since it's the same price as Pro AngularJS, and the latter book has much more information and real projects to follow along with. If the book was about half the price with full errata it might be worthwhile.(I bought the e-book on sale directly from the publisher.)

I've got an electronic version of the book through college library. It is easy to read and cover most of the Angular framework. I am a slow reader, but I was capable of going through it in just a couple days. Don't expect the book to cover the whole framework. It basically provides with a context and a starting to point to let you go and discover the framework for yourself. I was going to start wit AngularJS pro, but I didn't have the time to use it. I had to learn the basics of angular in a very short time to prepare for a job. However, if I wasn't in a hurry, I'd have gone for the pro one. I agree that's too pricy, even the digital one. If the publishers read the amazon reviews, they should have a look at their pricing problem.

If you are beginning the Angular JS, this by far is the best book available on the market. I initially started with Pro Angular by Adam Freeman, but just got so frustrated, it just jumped around on the explanations with out really discussing the basic principles.I then went on the Beginning Angular JS and it is what the title says, beginning Angular JS.......from scratch. It gave clear and concise explanations on the building blocks for making Angular JS applications. I did all the examples, which are easy to follow and addresses the principles which the chapter discusses. And the best it keeps the code simple, I found other books worry too much about the css styling which unnecessarily adds to the code complexity, when all we really want to know are the principles the author is trying to teach for that chapter. It won't make you an expert but it will teach the principles so that you can go on to do more advanced techniques taught in other books with confidence. My only negative on the book is at the time of reading there was no source code download, but the examples are pretty easy and concise so it shouldn't be an issue.Best way with this book is to do all the examples and save each example under its own html and chapter folder. This way if you forget something, you can pull it out and reference the code. I highly recommend this book for anyone beginner in Angular JS.