You are reading a single comment by @Ganblejs and its replies.
Click here to read the full conversation.
-
divide the book up in chunks that the app can manage without hitting ram limits
If you upload it as a plain text file, you can use
require("Storage").read(name, offset, length)to read in chunks. Memory should not be a problem, as it returns a memory-mapped String that points to the ROM anyway.
rigrig
@Ganblejs
Hi,
I'm creating a kind of e-book reader for the Bangle. The app preloaded with a small part of Wuthering Heights is on my app loader (edit: not anymore). The app customizer is only a placeholder for now, just click upload to install the app.
The code is here.
I want the user to be able to get a .txt version of a book from https://www.gutenberg.org/ (e.g. the attached wuthering-heights.txt which is 700 kB) and upload it to the app cusomizer where some preprocessing will be made before the app and book is loaded to the Bangle.
I'm not sure how to properly upload the book .txt-file and read it into a variable for manipulation. Is there a limit for how much memory a variable can occupy on the app customizer?
I think I need to divide the book up in chunks that the app can manage without hitting ram limits. My first thought was to have a JSON-file for these chunks and read them into a variable when needed, but I suspect the size of the JSON-file would be a problem in and of itself? So what I really need to do would be dividing the book up in several files instead (book1, book2, etc.). Does that sound right?
If anyone can help with some clarification on this it would be much appreciated! :)
1 Attachment