A directive to aid in paging large datasets while requiring the bare minimum of actual paging information.
Demo Available At: http://brantwills.github.io/Angular-Paging/
I often find myself paging across millions of rows even after I'd allowed users some level of database filtering (say by date range or name).
I also find myself forced into positions with large tables where normalization was not considered, or to be fair,
the input into the database itself is just garbage or very "log based".
These two limitations have pushed me to develop a reusable paging scheme which just happens to drop nicely into AngularJS.
I wanted to create an angular directive I could easily reuse and tie back into some form of controller.
I also wanted to include as little "paging" information as possible.
There are some attributes for handling CSS classes however, I settled on the required input being:
- What page am I currently viewing
- How many items in the list to display on a page
- What is the total count of items in my list
I wanted to develop a paging display which pulls away from the typical < << first 1 2 3 4 [drop-down] last >> >.
In my experience users never really have a true need to zip to the 9th page 2nd result
and if they do they have probably bookmarked the actual URL or more directly they have found the result through "better" filtering.
I've found the the best representation allowed the user to quickly move next or previous page, as this meets the immediate need for paging, while still allowing them to "get out of jail freely" by moving to the first or last page instantly. So visually I selected the common pattern 1 2 ... 7 8 9 ... 100 101 where the count inside the ellipsis changes as the pages increase or decrease.
- None right now but I'm sure they are out there!
MIT Licensed - with the exception that you star this repo :)