Open krissy opened 8 years ago
@krissy @CathMollie is this a priority? I'm now free on Sunday so could crack on with it?
@tanyapowell Yes, @krissy and I agreed we definitely want to paginate the Manage Drawings area. We may redesign this area - but not sure if we'll achieve before next pilot so I'd say go for it. @krissy - do you agree? If pilot is a month long, there could be a lot of drawings per org!!!
Brilliant @CathMollie!
@rocioleon @EChesters what's the max number of rows in the drawing table would you recommend we display before we paginate to another page? 10? 15? More? Less?
After discussing with @EChesters, @marizoldi and @rocioleon it's been decided to go with infinite scrolling (ideally with some lazy loading), rendering 10 rows of the table at a time as a short term solution until this view has been redesigned.
@CathMollie @tanyapowell @EChesters @marizoldi @rocioleon Do we still want to go with lazy loading for now? We have devs becoming available to build out any pagination features, and the current scrolling is not ideal for field workers as the data grows, so should we prioritise the redesign or implement google-ish pagination for now?
Pagination is currently set up with the Kaminari gem and triggered on button click by calling the kaminari link
link_to_next_page
. The JS for all this lives in this JS partial. We also implement decorators to access our models and their collections via the Draper gem. You can read the section on how to integrate pagination with these decorators here: https://github.com/drapergem/draper#using-pagination.We want to change the current hide/show more functionality to Google-like numbered pagination e.g.
<< 1 | 2 | 3 >>