Clicking on the reload button when an image fails to load reloads the whole chapter.

• #491
• #509
• #552
• #415
• #416
• mobile design: Settings

Frequency can be changed in the "settings" page.

• CRON: update mangas chapters list
• CRON: clear old cache.
• Add a page where user can see detailed logs (both manga updates and cache clearing)

probably because we're using Quasar's QVirtualScroller.
We should probably switch to QScrollArea

• search by manga name or displayname
• filter by mirror/source
• filter by language
• filter by both mirror and languages
• hide manga with no unread chapter
• merge mangas with same name/displayname but different sources/languages
• Manga thumbnail (carousel w/ multiple covers)
• click on manga thumbnail opens a mirror/language select menu
• unread chapter indicator

• download image
• download chapter

• Library
• Manga Page
• Reader
• Search
• Explore

• user can force chapters lists update
• all clients are aware if there's an ongoing update
• cannot update if already updating
• do not interfer with scheduled (auto) updates

• #336
• #334

• Add manga to database button
• Chapters list and navigation buttons
• Mark chapter as read button
• Zoom option
• Display mode buttons (ala AMR)
• If manga is in database changes are saved for this specific manga
• if manga isn't in the database changes are only applied to the current session. (changes are lost on page refresh)
• If manga is in database automatically loads the settings attached to the manga.
• if manga isn't in the database automatically loads the default settings

• define implementation strategy
• #325
• #329
• #337
• #328
• handle "import by url" for self-hosted sources

• Display manga name
• Option to edit a manga display name (custom-name)
• Show cover(s) (carousel)
• Show tags
• Show language
• Show source/mirror
• "Add manga to database" button
• List available chapters
• Option to mark a chapter as read
• Option to mark next/previous chapters as read
• Chapter read status indicator
• Click on chapter opens the reader
• Carry over the reader's current settings when manga is added to database.
• Carry over the chapters read statuses when manga is added to database.

• #496
• #331
• #332
• #333
• #334
• #338

• Sidebar
• Library
• #516
• #553
• #413
• #414
• Options

Is your feature request related to a problem? Please describe.
as it is right now i can't actually load my whole tachidesk library because of how it loads one at a time

i have ~400 manga on tachidesk when clicking explore on tachidesk i get maybe a dozen before it fails
and what does load takes ages as it is doing every manga one by one rather than asynchronously

Describe the solution you'd like
either lazy loading the images or just doing all the requests simultaneously (tachidesk can handle it)

Describe alternatives you've considered
none

Additional context

• #322
• #323

Is your feature request related to a problem? Please describe.
i want to run it on a headless server (that is already setup for containers)

Describe the solution you'd like
ideally github actions setup to automatically build and test a docker image on every release and preview(like beta release)

Describe alternatives you've considered
none

Additional context
how techidesk does it (.github/workflows/)

Manga Page

• #657
  • couldn't reproduce

Reader

• #656
• #655

Describe the bug
Language and source filter's interaction isn't consistent

To Reproduce
Steps to reproduce the behavior:

1. Add two mangas from different sources and languages: en and de as examples
2. Unselect en language from filter
3. The source using en should also be unchecked
4. Check that source again
5. en should be now checked, but it's not

Expected behavior
Language and source filter should interact with each other according to available sources and languages.
(unchecking a language should also uncheck every source using that same language)

• Adjust image to the reader's settings
• Keep track of page position
• Mark chapter as read when on last page
• "reload this image" button on image error
• "reload this chapter" button on chapter error
• Copy image to clipboard
• #300
• Mark chapter as read when reaching last page
• Prefetch next chapter
• #301

the reader is supposed to detect if the user clicks on the right/left side of an image to move to the next/prev image.

option 1

have a secondary database

option 2

• save chapter's read status in localStorage
• when manga is added to the db, push localStorage's data to db and clear localStorage
• when manga is removed push the data back to localStorage