[UI] Normalize Dashboard Pagination
Pagination should be the same across different lists of things, eg. Package Definitions and Applications page. The UI elements should look and work the same. The Applications page does it using built-in Django methods and the Package Definitions uses OpenStack pagination.
Blueprint information
- Status:
- Complete
- Approver:
- ruhe
- Priority:
- Medium
- Drafter:
- Ryan Peters
- Direction:
- Approved
- Assignee:
- Timur Sufiev
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Timur Sufiev
- Completed by
- ruhe
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fix AppCatalog to use 'marker' attribute for pagination
Addressed by: https:/
Refactor Packages and AppCatalog pagination
Addressed by: https:/
Fix AppCatalog to use 'marker' attribute for pagination
@tsufiev (21.05.2014)
based on irc discussion with sjmc7: while the approach with having just 'Next' button is OS-compliant, still it is very desirable to also have 'Previous' button. That can be achieved using reverse search order and giving first object at current page as marker - thus we obtain Previous page contents (at the cost of doubling number of requests to murano-api). To simply determine whether Previous button should be enabled or not (similar to the function has_more_data()), we can make a reversed query with limit=1 (to reduce amount of traffic).
Addressed by: https:/
Support specifying ``sort_dir`` key in packages.search call
Addressed by: https:/
Add 'Previous Page' button to the App Catalog page
Work Items
Dependency tree
* Blueprints in grey have been implemented.
