Health to the Web

Tutorials and resources angular.org site best book and the one to buy: "mastering Web Application Development with AngularJS" how to "think in angular "  Angular js flipboard magazine Dan Wahlin blog Fundamentals video in 60ish minutes Directives:  miskos pres from co-author of angular js in action AngularJS Directives  - Vanston Scope and Directives , I need to read it, looks helpful angular js in action (manning) read re injectors I followed and coded the popular "Fundamentals in 60 mins" tutorial by Dan Wahlin, here's my notes: transcript here code at:  http://tinyurl.com/AngularJSDemos his log: http://weblogs.asp.net/dwahlin you can prefix ng directive with data- as in data-ng-repeat, good for validators $scope is what is shared between the controller and the view i.e. the ViewModel the $scope implicitly is available within the div Module angular is very modular, modules are containers simple to create, syntax like re

Javascript Definitive Guide - possibly the most comprehensive programming book ever written imo. Here's my notes Chapter 6 Objects Objects in js:     •    an object is an unordered collection of properties, each of which has a name and a value. Name is string, value can be primitive or object     •    inherits properties of another object, known as its prototype     •    in js an object is any value that is not: string, number, true, false, null, undefined     •    manipulated and passed by reference     •    "own property" is a property defined directly on the object     •    "inherited property" defined and inherited from prototype object  
 Built in object properties:     ◦    prototype reference to another object to inherit from (prototypal inheritence)     ◦    class a string e.g. "Object", "Function" accessible by Object.prototpe.toString.call(o)     ◦    writeable     ◦    enumerable     ◦    configurable     ◦    extensible ES

These are my notes from a presentation by Amy Palamountain "Unsuck Your Backbone" Model View Controller/Presenter/Arse Bananna - don't get too hung up, they're all an improvement Framework - is opinionated and proscriptive, "here's how it should be done" Library do one or two things really well, structure outside is not its concern Backbone and Knockout are libraries, Angular, Meteor, Ember are frameworks. Below is each with star count it has on Github, a measure of popularity: Backbone 15,292 Angular 12,677 Meteor 9,369 Ember 7,708 Knockout 4,050 Marionette, 3,486 Backbone keeps it small, focused and encapsulated. Its a set of building blocks. It does not give you a blueprint on how to organize. But Backbone.js apps can become large and complicated soup too! MV* are presentation patterns only. Doesn't tell us how to build a scaleable app. To scale, build a Composite Event Driven Architecture. Build smaller apps that are com