Skip to content
This repository has been archived by the owner on Aug 5, 2023. It is now read-only.

continous scroll to next ( or prev ) chapter #275

Open
mathroc opened this issue Sep 30, 2021 · 1 comment
Open

continous scroll to next ( or prev ) chapter #275

mathroc opened this issue Sep 30, 2021 · 1 comment

Comments

@mathroc
Copy link
Contributor

mathroc commented Sep 30, 2021

instead of having to click on next chapter, the next chapter should instead load at the end of the current one so that I can just keep scrolling

(ideally the same would work when going to the previous chapter)

I suppose the only two chapters should be loaded at the same time to avoid increasing ram usage too much in the browser

when going to the previous chapter it could get tricky because until the pages are loaded their height is not the definitive height and it may make the page jump around as images are loading. it would be nice if the height could be given from the api so that the ui can reserve the correct space (this would be nice even on its own)

ps: I'm describing Tachiyomi behavior here

@faldez
Copy link
Owner

faldez commented Oct 1, 2021

I did thought about this, but considered not applying this until we figure out to do recylerview in rust.

I suppose the only two chapters should be loaded at the same time to avoid increasing ram usage too much in the browser

or this may suffice without recylerview, unless 1 chapter is 1 volume which consists over a hundred pages.

when going to the previous chapter it could get tricky because until the pages are loaded their height is not the definitive height and it may make the page jump around as images are loading.

yeah, it's janky but I think it's better than having to scroll so far to bottom. does tachiyomi have no problem? I think paperback have same problem

it would be nice if the height could be given from the api so that the ui can reserve the correct space (this would be nice even on its own)

to do this we need to download all the pages beforehand, or at least some of each pages to get the size. I don't know if the performance will be acceptable if we do that

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants