Closed jahu00 closed 8 years ago
Another option is dumping reader data into memory while in menu and putting it back into the reader when returning.
Closing as this is done in the EndlessScroll branch. However this issue may reappear (or not) when dealing with EPUB files.
Duplicate of #1.
Currently when the app loads a big file, it becomes less responsive and slow. However keeping a lot of data in memory (the dictionaries are around 70MB) is not an issue. The problem seems to be keeping the data in DOM and I need to reduce the amount that is stored there. This shouldn't be difficult, but it can lead to reading progress being hard to estimate. Character based progression might be an option though.