Status Updates From AngularJS in Action

Form validation looks pretty good. Appendices are so so. They rely too much on projects that are already set up.

URL routing in the app and extracting parameters.

The chapter on animations was almost as confusing as the one on directives. You can't just throw in a piece of code and only restate it in English. You have to explain how the parts fit together too. Including which bits are AngularJS and which ones are some third-party library.

Finished the very convoluted section on directives.

Building a directive for drag-and-drop. There is no context. The prose paragraphs that "explain" the code merely restate the JS code in English. I can read the code! Tell me why it has to look the way it does and what it's trying to achieve!

Introduction to directives. Dives into details way too quickly without providing enough context. What is the control flow? How and when are the various parts called?

Using decorators to enhance services and models. Testing with specs and mocking the $httpBackend. Could really use some class, object, and sequence diagrams to give better visibility into what is going on. I seem to write this observation for all the "... in Action" books.

Services (internal) and models (remote). $http and REST calls. Promises and deferred objects with $q. $http interceptors. This section is very rushed and with lots of "for more, see the documentation at..."

Views, controllers, and the binding between them. Some built-in directives for building views and calling actions on controllers.

Application file structure and basic module hierarchy. Basic routes through the application.

How the basic parts fit together with the Angello Lite sample application. Share state between controllers using services. Directives are the equivalent of Grails taglibs: small chunks of reusable presentation logic.

Why you want to use AngularJS.