javascript - AngularJS - Why have more than one controller -


what reasons there have multiple controllers in angularjs application? i've built few angular apps , i've never encountered problem thought multiple controllers make things easier me.

i'm still bit of n00b, have never written unit test , code isn't manageable i'm sure it's ignorance. , i've heard other people have multiple controllers.

put way: how 1 know should create new controller?

from i've seen of angular application should have separate controllers separate scopes. instance, applications have user data. you'll want have data attached user model, inside user controller:

function userctrl ($scope) {     $scope.user = {         name: "bmorrow",         lastlogin: "4/16/2013"     }; }

and template (our view) inside specific portion of applications structure. right side of navigation bar example, or on user details page. establish portion assigning controller using ng-controller. creates scope of said controller , binds corresponding models it. model (our data) connected view (the html) via controller.

suppose application has page user's written articles. can create controller restricted section of html holds article content.

function articlectrl ($scope) {     $scope.article = {         title: "hello world",         body: "lorem ipsum...."     }; }

in trivial example above, combining both of controllers won't harm. once application begins grow, logically organizing controllers/views according data represents make code cleaner , easier understand. less unneeded complexity make everything easier on you. , using 1 controller unneeded complexity.

you can see illustrated in basarat's answer well. don't need use 1 controller per route, doing helps logically structure application.

so, answer question, should have 1 controller per category of data. users, articles, fruits, vegetables, transactions, , on.

read angular controllers , model-view-controller pattern more information if haven't already. hope helps.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more