<div ng-app="myApp">
<div ng-controller="myController">
<input type="text" ng-model="uname" ng-show=false placeholder="Type here" ng-change="filterCall(uname)" ng-init2="filterCall(uname)" />
<p>
We loaded only 7 peaople initiallty, when you scroll down it will display more records
</p>
<strong>Employess with name and age !!! </strong>
<div id="count"></div>
<div class="cssdiv" scroll-directive id="divScroll" ng-init="loadmore()">
<table class="cssdiv">
<tr ng-repeat="u in filterUsers">
<td><strong>({{$index+1}})</strong></td>
<td>{{u.name}}</td>
<td>{{u.age}}</td>
<td style="font-style: italic;">{{u.hobby}}</td>
</tr>
</table>
</div>
<strong>a different examaple</strong>
<div class="cssdiv" scroll-directive>
Angular uses dirty checking to keep track ################## of all the changes in app. This means it will have to go through every watcher to check if they need to be updated (call the digest cycle). If one of the watcher is relied upon by another watcher,
Angular would have to re-run the digest cycle again, to make sure that all of the changes has propagated. It will continue to do so, until all of the watchers have been updated and app has stabilized. Even though running JavaScript in modern browsers
is really fast, in Angular it is fairly easy to add so many watchers that you app will slow down to a crawl. It will continue to do so, until all of the watchers have been updated and app has stabilized. Even though running JavaScript in modern
browsers is really fast, in Angular it is fairly easy to add so many watchers that you app will slow down to a crawl. Keep in mind the following when implementing or refactoring an Angular app.
</div>
</div>
</div>