We use the angular controller to interact with a View and a Model. Mark the html code with Ng-controller allows the correct instance of a controller and its scope to be bind, and its data and methods to be made available in the DOM.
The controller must have a name and can have a callback function - it's a fancy way to say the developer can specify what kind of data and methods the controller instance can have.
Todd Motto, a famous Angular developer and author wrote "a controller's purpose in an application lifecycle is to interpret business logic from the model and turn it into a presentational format." He also points out that the controller is main role is to talk to the Service and pass the corresponding data to the View via the $scope.
On the "return trip", the Controller can also pass any presentation view layer change back to the server via the Service.
(Not covered in this blog post - the controllerAs concept)
No comments:
Post a Comment