Giter Site home page Giter Site logo

Read progress about komga HOT 7 CLOSED

gotson avatar gotson commented on May 14, 2024 11
Read progress

from komga.

Comments (7)

BloodyIron avatar BloodyIron commented on May 14, 2024 3

I'm interested in this too please! \o/

from komga.

gotson avatar gotson commented on May 14, 2024 2

Yes that's the plan.

However I'm not sure how to mark a page read, once you reach it, or once you reach the one after?

Corner cases :

  • let's say we mark any page that is open : you open a book, you're on page 1. You don't want to mark it as in progress in page 1 if you close it now.
  • let's say we mark any page before the current page open as read : you reach the last page of a book, there is no page after. It should still be marked completely read, but it mark progress at the before last page instead.

I think it will need to treat first and last with extra care.

from komga.

anderaith avatar anderaith commented on May 14, 2024

I'm very interrested in this.
The missing functionnality for me is a way to recognize chapters I already read from the unread ones (Big mangas with lots of chapters).
Minimum to be useful would be a way to manually mark them as read. Full functionnality would be something that mark them as read if I saw the last page of an issue.

from komga.

gerroon avatar gerroon commented on May 14, 2024

Does this issue includes remembering the page numbers per book? I am not sure if storing page progress is the same thing

from komga.

gerroon avatar gerroon commented on May 14, 2024

Personally I am happy with anything regarding this issue. It would be so awesome if book page numbers are remembered this way or that way because trying to do this mentally is a bit not possible when browsing or reading through many books.

How about adding a manual bookmark method like reading a physical bookmark?

from komga.

gotson avatar gotson commented on May 14, 2024

How about adding a manual bookmark method like reading a physical bookmark?

Haven't thought of that, not sure it would be easy to use. Marking the max of last page read seem easier, but we'll see when we start implementing the feature!

from komga.

GlassedSilver avatar GlassedSilver commented on May 14, 2024

Yes that's the plan.

However I'm not sure how to mark a page read, once you reach it, or once you reach the one after?

Corner cases :

* let's say we mark any page that is open : you open a book, you're on page 1. You don't want to mark it as in progress in page 1 if you close it now.

* let's say we mark any page before the current page open as read : you reach the last page of a book, there is no page after. It should still be marked completely read, but it mark progress at the before last page instead.

I think it will need to treat first and last with extra care.

Mark read after n seconds, done. :)

Personally I am happy with anything regarding this issue. It would be so awesome if book page numbers are remembered this way or that way because trying to do this mentally is a bit not possible when browsing or reading through many books.

How about adding a manual bookmark method like reading a physical bookmark?

Hmm... I don't really stop mid-chapters, but when I do it's because I fall asleep, get off a train or some other unexpected event... The kinds of scenarios where general interaction with the device is interrupted.

How about adding a manual bookmark method like reading a physical bookmark?

Haven't thought of that, not sure it would be easy to use. Marking the max of last page read seem easier, but we'll see when we start implementing the feature!

To quote a beatiful meme: Why not both? Because they can serve vastly different use cases...

Like... favorite parts of the story or pages with amazing art. Right now what I do is always screenshotting them... That gets weird and wonky fast...

For read progress however it's automatic or bust.

If someone however prefers to manually set a bookmark and not use or care for the auto-set-as-read feature that's just another personal preference and workflow. :) imho good applications should try to cover multiple workflows, because people are very different. :)

from komga.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.