Downloaded Area Seems Redundant

Issue #98 new
Randall Fitzgerald created an issue

It seems to me that the manga's chapter list could be used to either automatically read online or open local files based on a stored type without the need for a file browser.

Indeed all chapter handling could be done through the main chapter view, at least for bookmarked manga. As well, thinking of the bookmarks as a personal library and having users default to that, while thinking of the online sites as repositories from which library items are added seems to be ideal from a UX perspective. But that's more of a naming convention than a real change to back-end, still could effect user behavior and lead to more orderly experience.

As to all chapter handling, I'd include marking things as read, downloading (currently its only function, really), and deleting or converting as need be. This could also make underlying functions (pdf and zip handling) more readily accessible to end users. Select a load of Manga, click download as zip, ezpz.

I'm willing to do mock ups of any proposed changes or even code on them if you like. Thanks for readin' my tickets so far. Will add more as I see things if I see things.

Also, feel free to change any of my priorities.

Comments (2)

  1. cylonu87 repo owner

    The download area is the only way to access the files when you are offline. The list of chapters requires an internet connection.

  2. Randall Fitzgerald reporter

    Alright, so this one relates to issue #99, and I'll propose a fix (improvement, more than fix) here.

    Basically, however you're grabbing a list of chapters, I would suggest that you store a local flatfile (JSON or something) with the chapter list and cache that for X amount of time (three hours or so) and then use that local file until the cache expires (to keep hitting the webservers down) and to keep chapter list loading snappy on local devices or to ensure we have access to a chapter list if we're offline.

    This way, you could put more files handling into a unified UI area and possibly store other metadata in a small JSON sort of file (which would allow attaching a folder to a given chapter in a meaningful way) but also works for people who happen to be offline without needing the downloaded area (which could be left in, but out of sight).

    Obviously, I'd think SQLite or something similar would work as well, but honestly might be more complicated than is necessary. JSON flatfiles would be clean and easy to work with on a per-series basis.

  3. Log in to comment