-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add paginatior for big tables #381
Comments
I am also in favour of paginated lists where the number of elements is really large. To help performance, this should not just be a UI change but actual load only part of the entities from the database (however, these need to be in the required order). |
These long lists without pagination have become a big problem for performance (and thereby for usability). Assigning this high priority. |
# [2.14.0](2.13.2...2.14.0) (2020-06-27) ### Bug Fixes * prevent error log message about serviceworker not available ([a2eebf9](a2eebf9)) * **dashboard:** improve styling of recent-notes dashboard widgets ([4355ea4](4355ea4)) * **note:** prevent disappearing of children linked in notes ([4aba52b](4aba52b)) * **notes:** add full width to notes table ([7eef007](7eef007)), closes [#457](#457) [#458](#458) * **search:** improve search: loading indication and other hints ([6995476](6995476)), closes [#366](#366) [#456](#456) ### Features * add pagination to tables ([87cddde](87cddde)), closes [#381](#381) [#445](#445) * **conflict-resolution:** view and resolve pouchdb document conflicts ([2a84025](2a84025)), closes [#79](#79) [#393](#393) * **latest-changes:** display changelog based on GitHub Release information ([7226f08](7226f08)), closes [#238](#238)
🎉 This issue has been resolved in version 2.14.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
At the moment, big tables used in, for example, the notes-manager or the children-list display every single element in a big scroll view at once.
In my opinion, a better user experience can be achieved using a paginator that displays the entries throughout different pages. The first test of this has also shown better performance since not every entry has to be loaded and rendered at once.
Personally, I do not know how those entries are being used in a temporal context. However, I can imagine that the working set might only include a few months of entries. If this is the case, and the database allows it, it might be a good idea in a second step to only load a few months worths of data and then load more if needed.
The text was updated successfully, but these errors were encountered: