1MWise
Could we be able to scroll our entire library without page breaks? Currently I have my setting at 200 per page but I wish I didn't have to click from page to page to see all my books.
2lorax
I'd really want this to be optional, if introduced. It's far faster for me to jump to the middle of my library, or the end, with pagination than it would be with endless scroll.
3norabelle414
If you switch to cover view and make the covers very small you can fit about 600 on one page. But the page takes awhile to load that many.
4MarthaJeanne
>2 lorax: Yes, I'm really happy with 50 to a page, but able to jump.
Not only that, but I would guess that it would be a real drain on the servers to try to get a large library set up all at once.
Not only that, but I would guess that it would be a real drain on the servers to try to get a large library set up all at once.
5gilroy
I wouldn't mind a new option of maybe 500 books a page instead of a limit of 200, but outside of that, I agree that I prefer the pagination. Also, I like to use search to narrow my overall need to scroll, by finding a specific tag, title, or author.
6Keeline
In most websites this is achieved by loading another grouping when the browser's window reaches the bottom. It is done with an AJAX call or a similar technology.
If I am using my computer with a fast connection, 200 in list view is OK. However, on my iPhone or iPad Safari browser this is too much and loading the page will often fail. This could be a timeout or a RAM issue. It does not say. It just goes into a loop of trying and failing to reload. So I have to reduce the list view to 50 and it works successfully. (Separate from the iOS app, of course).
We have more than 9,000 books so putting them all on one browser page is asking for trouble, even with an AJAX view. I see it sometimes with Facebook when following a group feed and it gets slower and slower to react the farther down the list it goes.
This sort of feature could have negative impacts on people with older equipment or slower connections. It should only be done if these can be addressed.
James
If I am using my computer with a fast connection, 200 in list view is OK. However, on my iPhone or iPad Safari browser this is too much and loading the page will often fail. This could be a timeout or a RAM issue. It does not say. It just goes into a loop of trying and failing to reload. So I have to reduce the list view to 50 and it works successfully. (Separate from the iOS app, of course).
We have more than 9,000 books so putting them all on one browser page is asking for trouble, even with an AJAX view. I see it sometimes with Facebook when following a group feed and it gets slower and slower to react the farther down the list it goes.
This sort of feature could have negative impacts on people with older equipment or slower connections. It should only be done if these can be addressed.
James
7Keeline
In the likely case that LT won't care to add this feature, there may be ways for you to get the feature of "infinite scrolling" with a browser plugin. This page from 2010 gives some advice on this.
https://www.hanselman.com/blog/infinite-scroll-websites-via-autopagerize-hacky-b...
Once you know the term, it may be possible to search for other pages that are more recent.
James
https://www.hanselman.com/blog/infinite-scroll-websites-via-autopagerize-hacky-b...
Once you know the term, it may be possible to search for other pages that are more recent.
James
