flafydev / epub_reader Goto Github PK

Title. Including sub chapters.

The problem is with anchors

1. What if the next chapter is in the same file but points to an anchor you haven't reached yet?

Right now the renderer is sending how many anchors you've currently passed in the current file. This is used by the reader app to correctly determine on which chapter you are in case there are multiple chapters pointing to the same file but different anchors).

My idea is instead of sending the passed anchors of the current file, send all of the anchors of the current file together with the inner page they are on. This way the reader app can compute on its own how many anchors have passed. And can also determine how many inner pages until the next chapter.

2. What if the next chapter is in a different file but points to an anchor?

You wouldn't be able to determine the percentage of how far an anchor is without having the file loaded.
This is solved by #6

Task list

• 1 solved. Change from passed anchors to a map of anchors and their inner page.
• 2 solved. Implement #6

When reopen a book on iOS, the ebook player will load next 3 chapters but not last saved point.

in pubspace.yaml file we have assets: - assets/index.html
but doesn't exist in assets folder

An Android widget where you can see your recently read books and swipe between them.

Google Play Books' widget for example.

When preprocessing a book, get the location(a number between 0-1, where 0 is the start of the file and 1 is the end of the file) of each anchor in its own file.

This is useful for issues:
#7
#8

The search results when searching queries in books are bad.

Here is how the search fails.

<p>This is a <span>short</span> paragraph</p>

This weird results are because the search only searches inside text nodes. In this case there are 3 text nodes.

If you have a book in a shelf, it will appear both in the All view and the Shelves view. Going into the book in one view, then going through a few pages, exiting the book and opening the same book in the other view. You'll see it doesn't save the the location.

Right now all the data of the reader is saved on the device.
This includes the epub files of the books and the reading progress of each book.
The disadvantages of this approach:

1. Can't use the app on multiple devices without having to manually sync all the data and reading progress yourself.
2. Can easily reach a few hundreds of MBs of data after adding a few books (because each book's epub file takes like 10mb)
3. With big amounts of data it takes a while to create backups (zipping all the data).

For these reasons, it should be possible to connect to a server to take care of all these problem.

Show the page number of each chapter(including sub chapters) similar to how Google Play Books does it.
blocked on #6

After downloading a file from the browser, loading it in the app using the file picker and then trying to open that file results in this error.

Unhandled Exception: Unable to load asset: "assets/index.html".

Below given is the screenshot of the error.

https://prnt.sc/R9RTNwvDFL97

Can somebody help me out with the error.

Thanks.

Sometimes when highlighting text it selection will go outside to the text beyond the current inner page's text

I don't know what is better: fetching HTML from webview or injecting JavaScript and processing HTML from a local webserver. From the code of epub_renderer, JavaScript from webview has to do a lot of work. If it fails at some point, the renderer will stop rendering. For example, if we highlight the first word of an inner page, the renderer will stop rendering.

When reading does not display the content of the book page

Bookmarks are useful for quickly saving your location in a book and going somewhere else without any risks.

The implementations:

• A new screen similar to the notes' screen.
• A way to press on the top right of the screen to add/remove a bookmark.
• New property in the BookSavedData for the bookmarks.
• The bookmarks will use the consistent location of the page they are were assigned to to save their location.

Problems

1. if the bookmark saves its inner location by node index, how'd we know which nodes are currently in the page to know whether or not to show the bookmark?

Pick on of two solutions:

• This can be solved by sending all of the visible nodes from the renderer to the reader app. But this requires to check each node whether is visible or not, which may take a lot of time!
• To get the node indexes between pages get the current page node index and the next page node index and the indexes between them are in the current page. This only works if the node indexes increase by the inner page they are located at, which I think is true.

Edge cases:

1. Two bookmarks on the same page after resize of font (or anything else that changes the number of inner pages)

In that case only show the bookmark once but keep in mind that

This is because of the inconsistency between the number of text nodes in the app and in the renderer.

IMO this is not worth fixing until #2 is fixed.

In any page, select first word and highlight it then page is loading (page is not ready).
Reopen book, after navigate to this page by location, can not transition to other page by horizontal drag