Paperback-iOS / app

Repository to host app releases, issues, and feature requests for Paperback

Home Page:https://paperback.moe/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[FEATURE REQUEST] Set Reader View by category/source/parent title

drewjc75 opened this issue · comments

Preflight Checklist

  • I have read and I agree to follow the support disclaimer.
  • I am sure that my feature request has nothing to with third party extensions.
  • I am using the latest available Paperback version (currently 0.8).
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

What type of Apple device is the feature request for?

All device types

Describe the feature

I'd love to see an update to the viewer settings to allow the ability to set a particular view for a category, source, or title. Currently, there is only one way to set a view, and that is globally, with the ability to override a view for a specific title/file. This makes it difficult for anybody who's using the app to read both manga and Western comics, because the default will apply to everything.

Instead, I think it would be better to allow for a parent/child cascading method, where it might go something like this:

  • Source (Komga: View 1 - Left-to-Right)
    • Title (Comic 1: View 1, inherited from Source)
      • Chapter 1 (Comic 1, Issue 13: two-page view instead of single-page view, still Left-to-Right, overriding parent)
      • Chapter 2 (Comic 1, Issue 15: inherited from Title, inherited from Source)
  • Source (Third-party source, Manga: View 4 - Right-to-Left)
    • Title (Manga 1: View 4, inherited from Source)
      • Chapter 1 (Manga 1, Issue 1: Two-page view, overriding parent)
      • Chapter 2 (Manga 1, Issue 2: inherited from Title, inherited from Source)

This is really just off the top of my head, but I'm guessing that each file has a cascading set of parent objects in the database, so I would think it would be possible to do something like this:

  • User opens a file. App checks the file to see if there's a view set to it. There is no view set for it, so:
  • App checks the parent object to see if there's a view. There is no view set for it, so:
  • App checks the grandparent object to see if there's a view. There is a view set, so the app applies that view to the file.

That way, if the parent object has a view set, it would apply there, and that view would override the grandparent object, but if there is no view set, the highest-ordered view would apply. And if there is no view set for the top-level item, then the global default would apply.

Feature Motivation

This modification would allow for the most flexibility and automation with regard to how items are seen, and provide the least intrusive method for defaulting to a given preference for anybody who utilizes multiple formats inside the app. Since the app is designed to allow for Western comics, manga, and e-books, it would stand to reason that being able to customize for each of those with a built-in feature would be best.

Anything Else?

No response