You are reading a single comment by @halemmerich and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@halemmerich
I think the customizer will not be a problem, 700k in a variable in a browser should be normal stuff. Imagine images etc. beeing loaded into variables.
In the gpstrek app, the route and its waypoint are loaded from one big file by storing offsets into that file in a variable. I read the file completely and build this index on the first load, but you could build your index in the customizer and upload it as json. Imageclock does something like that for the resources file containing all images for the watchface.
You could just read a few k into memory at a time and store the indices for the previous and upcoming chunk somewhere to load them as soon as needed. The chunk size would need to be a tradeoff between index size and used RAM per chunk.
I had really big files from the recorder, so I would expect the file system to handle those files just fine.