Say Somehing about NG-REPEAT

[beastar 457]

People say that it run slow on huge amount of data this is why some other framework like ionic has implemented ng-collection do you have any idea about this?

[Sander Elias]

Hi Beastar,

Define huge amount?

Nevertheless, it makes a way better UX if there are as few as elements as possible. People are not well equipped to handle huge amounts  of data, that's why need to preprocess it for them :)

Regards

Sander

[beastar 457]

I understand well this, but let consider ng-collection from ionic framework vs ng-repeat from pure angularjs

We can see some approach that have been introduced in ng-collection is about to enhance performance why do we need this king of handle if ng-repeat is strong enough?

Okay how can we get exactly the same result if it is different. 

Richard Muragijimana

--
You received this message because you are subscribed to a topic in the Google Groups "AngularJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/angular/ntCr_d7mZNg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to angular+u...@googlegroups.com.
To post to this group, send email to ang...@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

[johny developer]

excellent answer is here:

http://stackoverflow.com/questions/9682092/how-does-data-binding-work-in-angularjs/9693933#9693933

[beastar 457]

Hello Johny I agree with this explanation it reveal all aspect and I understand now why and how

Thanks to everyone in this group.

Richard Muragijimana

On 25 February 2016 at 19:33, johny developer <semtam.n...@gmail.com> wrote:

excellent answer is here:

http://stackoverflow.com/questions/9682092/how-does-data-binding-work-in-angularjs/9693933#9693933

[Sander Elias]

Hi All,

Inspired by this thread I took plunker and created a small sample. In there, you can play around with whatever you think is a huge amount of data. It will generate any amount you see fit.

On my computer, everything works snappy until I hit 2.000 rows (10.000+ watchers). It is workable up until 6.000 rows. Although sorting the table then is taking a bit longer than I would like, and the first few letters in search are then sluggish.  

There is intentional NO optimization done. In real practice, never do it like this. If you would put a limitTo on the repeat, everything works fine untill you run out of resources. tested that up until 12.500 rows.. everything works snappy then.

So if you make a good UX (in this case, use at least paging and/or limit the number of visible row) the number of watches will seldom be much of an issue.

Regards

Sander

[beastar 457]

I am very  excited about this examples for sure It reveal all imagination about ng-repeat and some thoughts about what good and worse however I can see that Experience matter a lot in this ng-repeat master.

Richard Muragijimana

--

[beastar 457]

Thanks to use chance too as it is as useful tool I did not discover yet.

Richard Muragijimana