Hi Krzysztof,
Ok, I now have taken a look at your UX, looks good to me. Still, you can
use infinitive scrolling, but I guess in this case that would be hard to
implement, and not really adding much performance.
I didn't look at your code at all. The performance was quite alright on my
system, b
could this help. we did something similar for an stock photo site but not
with angular. requirements was no pagination but infinite scrolling
https://sroze.github.io/ngInfiniteScroll/
On Tuesday, November 22, 2016 at 1:13:38 AM UTC-8, Krzysztof Szczesny wrote:
>
> Ah sorry, noticed a typo in m
Ah sorry, noticed a typo in my previous post. I meant to write "Paging is
out of the question in terms of UX" (for this case <- that part was
implicit). Not sure if you clicked the link or not, but that app doesn't
have a normal table - it's a collection of pictures...for gamersfor a
game i
Hi Krzysztof,
Can you show me a real UX study that favours a huge table instead of a
paged one? I have read numerous science based ones that favour interfaces
with fewer items available. Humans seem to have a problem processing UX
with more as 200 items in it.
I'm really interested in this, p
Hello Sander,
Thanks for the tip, but paging is not an option. The app is a port to
angular 2 of this http://spooky.github.io/unitdb/#/ (which is in angular
1). Paging is kind of the question in terms of UX ;) Currently the list has
406 items, but this will grow to (s I mentioned) around 1000+ i
Hi Krzysztof,
The best approach would be, 1, but combined with paginating. Just show the
first 20 to 50 rows, and then paginate over the rest (If needed, your
filter/sorting should put the needed data on top of the list anyway!)
(also, you can use an "infinite" scroll instead of paginating, but
