angularjs - Angular ng-repeat with polling data provider -


i reading angular now.

let's ng-repeat binding in effect, , child records appear <li> elements beneath <ul>.

now let's new objects pushed onto watched array (watched watchcollection) in model every 60 seconds polling data provider (i.e. existing data in array don't change).

will angular append new counterpart <li> elements <ul> or completely recreate <ul> when detects array has additional elements?

edit: @blackhole has asked, "why ask...?", i'll elaborate more complicated hypothetical matches pretty actual app, i'm thinking of rewriting learn angular.

imagine have fetch manifest immensely long freight train , display users contents of each freight car. don't want user wait , wait , wait, , see entire freight train manifest. instead, ask server list of car ids , fetch each car's manifest in turn, , in success callback, pop carid off array, , fetch next car's manifest, until array of car ids empty. expect ui add current car's manifest page immediately, next car's manifest being fetched.

after quick test, can confirm when pushing new items bound array, former dom elements not recreated.

to prove it, created simple array , bound ng-repeat, created jquery method changes dom elements, note when push new element array (using angular) elements changed using jquery method:

app.controller('mainctrl', function($scope) {   $scope.items = [];    $scope.pushitems = function(){     var newitem = {description: 'item description ' + $scope.items.length};     $scope.items.push(newitem);   }    $scope.newarray = function(){     var newarray = [{description: 'first item of new array'}]     $scope.items = newarray;   }    $scope.reassign = function(){     var newarray = angular.copy($scope.items);     $scope.items = newarray;   }  });  $( document ).ready(function() {     $("#domchanger").click(function(){       $(".mylist li").html('changed');     }); });

here plunkr demonstration: http://plnkr.co/edit/2scx4zjjdorlqwgtivar?p=preview


Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more