I tried using the group helper, but not sure it will work for my use case. I have a list of input elements (text fields, pick lists, etc). It seems the only way I can get the content to render in each input element is to always us ‘groupRows=true’. And even when it does render, it’s still very slow. Is this a known limitation of the {{group}} helper? Does it not help the efficiency of input elements?
So what is the right pattern for nested list views today? I notice with 3 levels of nested collection view, which create ~ 300 renderings, the screen is only painted once? Apparently at the end of rendering all of the subviews in serial, and it takes 3 seconds.
All of the arrays involved are Ember.A() and built up using pushObject. I’m really interested to find the pattern for achieving this which is actually performant enough to use.
Careful @lennon_p, building up your array with pushObject will mean that you will be re-rendering as each option is added. You’re better off calling pushObjects (plural) once with all of your data so that it only fires off one re-render.
The fact is unbounded result sets are bad architecture. If you’re not doing something like cloaking offscreen elements - regardless of the size of the total dataset then you’re not being a good citizen and you’re probably being lazy (instead of making your data lazy?)
Angular might be good at loading 2000 items into a list but then I’d say it’s also good at encouraging bad architecture.