Bresleveloper's AngularJS Tutorial : Basic Route / Routing

http://bresleveloper.blogspot.co.il/2013/08/breslevelopers-angularjs-tutorial-table.html

u'll here a lot about angular's $route and $routeProvider, and let me warn u: its awesome and does ITS work great, BUT ONLY ITS JOB. so u should either manage ur app flow / navigation with angular's routing ALONE, or some other way while NOT mixing the angular route.

the good part is that if u use routing right u already have full links "built in" (I mean like www.ursite.com/thing1/filter2) support and browsers entries for back and forward, and that really great and sometimes that's what u need.

lets see why - if we take our previous example and try to "just" add routing like that we'll see that stuff just wont get updated, u can try to add to this all kinds like broadcast ect., the point is that here is where u can easly fall:

our view (I call it problemView cuz I don't use myService.X in it):

<div class="singleItem" ng-repeat="catalogItem in MainCatalog" ng-click="MainItemClick(catalogItem)" >
   <a class="box" href="#" >
      <img ng-src="{{ catalogItem.image }}" width="100">
      <div class="textContainer" >
         <h4>{{ catalogItem.level }} - {{ catalogItem.name }}</h4>
      </div>
   </a>
</div>

our code (Ex 4)

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<style>
   .main { width: 400px; }
   .singleItem { width: 25%; display:inline-block; border: 2px dashed green; }
   .textContainer { text-align: center; }
</style>

<script src="angular.js"></script>
<script >
   var myStudyModule = angular.module('myStudyModule', []);

   myStudyModule.config(function ($routeProvider) {
      console.log("config");
      $routeProvider
         .when('/', { controller: 'myController', templateUrl: 'Views/problemView.html' })
         .when('/somethingElse/:level', { controller: 'myController', templateUrl: 'Views/problemView.html' })
         .otherwise({ redirectTo: '/' });
   });

   myStudyModule.service('myService', function ($http) {
      console.log("myService");
      var self = this;
     
      self.getDataPromise = function (parentKey, level) {
         console.log("myService.getDataPromise");
         var url = 'Handler1.ashx';
         if (parentKey && level)
            url += '?parentKey=' + parentKey + '&level=' + level;
         return $http.get(url);
      };
   });

   var myController = function ($scope, myService) {
      console.log("myController - NEW INSTANCE");
      $scope.MainCatalog = [];
      
      var getMyData = function (parentKey, level) {
         console.log("myController.getMyData");
         myService.getDataPromise(parentKey, level).success(function (data) {
            $scope.MainCatalog = data;
         });
      };

      getMyData();
      $scope.MainItemClick = function (catalogItem) {
         console.log("$scope.MainItemClick");
         getMyData(catalogItem.key, catalogItem.level + 1);
      };
   };

   myStudyModule.controller(myController);

 </script>
</head>
<body>
   <div class="main" ng-app="myStudyModule" ng-controller="myController">
      <ng-view></ng-view>
   </div>
</body>
</html>

that's cuz when ur using $routeProvider its will create a new controller with every change. that thing is really forcing u to make ur controllers very abstracts, pure user behavior managers.
the right way to use routing is like that:

view (simpleView):

<div class="singleItem" ng-repeat="catalogItem in myService.catalog" ng-click="MainItemClick(catalogItem)" >
   <a class="box" href="#" >
      <img ng-src="{{ catalogItem.image }}" width="100">
      <div class="textContainer" >
         <h4>{{ catalogItem.level }} - {{ catalogItem.name }}</h4>
      </div>
   </a>
</div>

code (Ex 5)

var myStudyModule = angular.module('myStudyModule', []);

myStudyModule.config(function ($routeProvider) {
   console.log("config");
   $routeProvider
      .when('/', { controller: 'myController', templateUrl: 'Views/simpleView.html' })
      .when('/somethingElse/:level', { controller: 'myController', templateUrl: 'Views/simpleView.html' })
      .otherwise({ redirectTo: '/' });
});

myStudyModule.service('myService', function ($http) {
   console.log("myService");
   var self = this;
   self.catalog = [];

   self.getData = function (parentKey, level) {
      console.log("myService.getMyData");
      var url = 'Handler1.ashx';
      if (parentKey && level)
         url += '?parentKey=' + parentKey + '&level=' + level;
      $http.get(url).success(function (data) {
         console.log("$http.get.success");
         self.catalog = data;
      });
   };

   self.getData();
});
var myController = function ($scope, myService) {
   console.log("myController - NEW INSTANCE");
   $scope.myService = myService;
  
   $scope.MainItemClick = function (catalogItem) {
      console.log("$scope.MainItemClick");
      myService.getData(catalogItem.key, catalogItem.level + 1);
   };
};

myStudyModule.controller(myController); 

but that's a bit futile and can be very dangerous, we want to use the route parameters for the flow, so angular provides us the $routeParams.
with this way we actually use the anchor's href or $location or $window id needed.

DONT use is in the controller, in my example project (goto toc) ex no.6 is how bad it is, and 7-9 are just more examples about how to use all that but only Ex 10 is the really right one and i'll save for u here and give just no.10:

view (routeView - cuz I use href here):

<div class="singleItem" ng-repeat="catalogItem in myService.catalog" >
   <a class="box" href="#/{{ catalogItem.level + 1 }}" >
      <img ng-src="{{ catalogItem.image }}" width="100">
      <div class="textContainer" >
         <h4>{{ catalogItem.level }} - {{ catalogItem.name }}</h4>
      </div>
   </a>
</div>

code (Ex 10)

var myStudyModule = angular.module('myStudyModule', []);

myStudyModule.config(function ($routeProvider) {
   console.log("config");
   $routeProvider
      .when('/', { controller: 'myController', templateUrl: 'Views/routeView.html' })
      .when('/:level', { controller: 'myController', templateUrl: 'Views/routeView.html' })
      .otherwise({ redirectTo: '/' });
});
        
myStudyModule.service('myService', function ($http, $routeParams) {
   console.log("myService");
   var self = this;
   self.catalog = [];

   self.getData = function () {
      console.log("myService.getMyData");
      var level = $routeParams.level;
      if (!level)
         level = 1;
      var parentKey = 1; //this should also come from $routeParams with the same logic as level
      var url = 'Handler1.ashx?parentKey=' + parentKey + '&level=' + level;
      $http.get(url).success(function (data) {
         console.log("$http.get.success");
         self.catalog = data;
      });
   };
  
   //u cant put getData here cuz the service gets only 1 instance unlike the ctrl who gets an instance every route
});
 
var myController = function ($scope, myService) {
   console.log("myController - NEW INSTANCE");
   $scope.myService = myService;
   myService.getData();
};

myStudyModule.controller(myController); 

Next : http://bresleveloper.blogspot.co.il/2013/08/breslevelopers-angularjs-tutorial-basic_20.html
 

Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more