angelocarasig / ikaros

Browser-based epub reader

Definitely (Not) A VN Enthusiast

rosa umineko my beloved

ikaros's Issues

Start book from specific bookmark

Implement reader tracker for progression and continue from. Seems fairly straightforward in theory:

• Object that stores CFI, percentage and some other properties like a label, description
• Autosave bookmark via locationChanged emitter
• Creating a bookmark saves currentLocation which should already be handled in store (in v1.4.3)
• Since we use epubCFI (string value) to track location should be easy to incorporate into db

https://stackoverflow.com/questions/61309899/useeffect-cleaning-function-is-not-called-when-tab-is-closed

Update navbar

Updated navbar with:

• Login redirect + Logout dialog
• use novel store and quick glance for library
• profile section with settings and import log

Progression bar per section

Something like this on scroll

Smoother reader animations

Add framer-motion into reader component and do some fancy footwork

Proper last read metrics

Last read just involves which novel is in last read
Will probs just be something inside a useEffect deconstructor

• Last Read on navbar
• Sort by Last Read in library
• Last Read in dashboard

Migrate akasha sidebar

Need this for sidebar from old ver. akasha:

Progress bar on toaster uploads

Better Reader Loading animations

Need the following to mark this as completed:

• Different spinner/loader to show loading progress
• a library hook that uses sonner (or something else) to show when different props of the novel have been loaded (bookmarks, toc, book opened, etc.)
• Maybe pulsing animation? (some kind of moving gradient animation on Loading novel or just a color pulse)

Richful upload

• Add a new route (maybe /profile/imports) that show a queue of what is to be uploaded
• Upload can (and should be) on client-side to reduce vercel hassle (https://vercel.com/guides/how-to-bypass-vercel-body-size-limit-serverless-functions)
• Good opportunity here to also clean up the ugly UploadDialog client component as well

Add support for paginated mode in reader

self explanatory

Artwork tab should only show 1st image and obscure the rest

Probs just a "spoil me!" button like in vndb

Reader style injection

self-explanatory check library-settings TODO

CRUD for novels

Library should have CRUD ability for a novel, namely the following:

• Updating a novel's metadata (title, author, dates, description, etc.)
• Removing a novel from library (this one might be difficult since there is no direct relationship between a storage bucket novel object and the db row entry for it)

Extend by:

• Auto-scrape from NovelUpdates URL (probs vercel/supabase edge-function?) (unsure about other sources besides novelupdates currently)

Collections

Setup collections to be able to do the following to a novel:

• Add/edit/update/remove tags
• Add/edit/update/remove categories
• Add/edit/update/remove series
• Group by options in library sort options

CRUD operations for groups may be worthwhile to just follow stash UI format.

Refactor useSetupReader to separate hooks

Break down this disgustingly giant hook

Reader window after being unfocused (go to a different tab) and back after a certain time period does not render any new content

In such a case it'll be good to generate an autosave (#9) when page is unfocused for a given time period (at this point though it should be polling to update with an autosave)

Instead - do whats mentioned above and force refresh if page is unfocused for longer than 2 mins (?) will need to test though