Module - is where we write pieces of our angular application
acts as a container for the different parts of our app – controllers, services,filters, directives, etc.
where we define our dependencies
Controller - These are JavaScript functions that are bound to a particular scope.
they are bound to the DOM element they are referenced
Data binding - It is the automatic synchronization of data between model and view components.
A directive - is a piece of code that tells angular to run or reference a javascript code.
directives are markers on a DOM element that tell AngularJS to attach a specified behavior to that DOM element
Expressions - is how we insert dynamic values in our html.
JavaScript expressions are evaluated against the global window. In AngularJS, expressions are evaluated against a scope object.
e.g.
{{"hello" + "world"}}
View Model - Unlike the previous MVC models that we learned in which the controller is responsible for calling on methods once a view event is fired and when that event fired, you would try to interpret the event and parse the DOM for state so that you could perform some imperative operation.
In view model The controller no longer is responsible for listening to the view, but rather the view is responsible for issuing specific commands to the controller that it operates on.
Module - is where we write pieces of our angular application
Controller - These are JavaScript functions that are bound to a particular scope.
Data binding - It is the automatic synchronization of data between model and view components.
A directive - is a piece of code that tells angular to run or reference a javascript code.
Expressions - is how we insert dynamic values in our html.
{{"hello" + "world"}}
View Model - Unlike the previous MVC models that we learned in which the controller is responsible for calling on methods once a view event is fired and when that event fired, you would try to interpret the event and parse the DOM for state so that you could perform some imperative operation. In view model The controller no longer is responsible for listening to the view, but rather the view is responsible for issuing specific commands to the controller that it operates on.