The little mouse
-
First the little mouse wanted an epub reader Then she needed a zip library to unzip the xml Then she needed an XML parser library to decode it. Then she needed an HTML library to display the content. Then she needed a CSS library to lay out the HTML Then she needed a truetype font library to render the CSS styles *sigh* If these were designed for little CPUs why did they make the technology stack so deep? :confused: :doh:
Real programmers use butterflies
-
First the little mouse wanted an epub reader Then she needed a zip library to unzip the xml Then she needed an XML parser library to decode it. Then she needed an HTML library to display the content. Then she needed a CSS library to lay out the HTML Then she needed a truetype font library to render the CSS styles *sigh* If these were designed for little CPUs why did they make the technology stack so deep? :confused: :doh:
Real programmers use butterflies
Or, the little mouse would just check out the fantastic (and 100% free) calibre reader[^]. :-D And also FOSS (GitHub - kovidgoyal/calibre: The official source code repository for the calibre ebook manager[^]) you can join the project too. It really is great software. i've been using it for years now.
-
Or, the little mouse would just check out the fantastic (and 100% free) calibre reader[^]. :-D And also FOSS (GitHub - kovidgoyal/calibre: The official source code repository for the calibre ebook manager[^]) you can join the project too. It really is great software. i've been using it for years now.
not sure it will run on a WROVER chip though
Real programmers use butterflies
-
not sure it will run on a WROVER chip though
Real programmers use butterflies
-
honey the codewitch wrote:
not sure it will run on a WROVER chip though
Oh...I had not seen that requirement. :)
I didn't list it in the OP. My bad. The thing is too, that looks like an e-book manager more than a reader. I want this thing to run on a ESP32 @ 240MHz with 4MB of PSRAM, 4MB of flash, and 512k of actual RAM, with a 600x448 7 color e-paper display. It's a tall order, to be sure. Especially processing CSS layouts and HTML. TTF support is no joke either though. This is a project and a half. However, as I'm building it I intend to develop a user interface library that is HTML based for producing more professional screens on these little IoT widgets.
Real programmers use butterflies
-
I didn't list it in the OP. My bad. The thing is too, that looks like an e-book manager more than a reader. I want this thing to run on a ESP32 @ 240MHz with 4MB of PSRAM, 4MB of flash, and 512k of actual RAM, with a 600x448 7 color e-paper display. It's a tall order, to be sure. Especially processing CSS layouts and HTML. TTF support is no joke either though. This is a project and a half. However, as I'm building it I intend to develop a user interface library that is HTML based for producing more professional screens on these little IoT widgets.
Real programmers use butterflies
That sounds cool. Maybe some of the code that renders the e-books in calibre could be leveraged to give you an idea how to do that work?? But, maybe not-- since I think the calibre code is in python. Isn't it interesting that this is about re-use -- one of the holy grails of programming that has been around forever -- and we're still talking about it in 2021? A few years ago another dev had a HTML to PDF thing in their code. I said, "hey, can I get that code so I can just create PDFs from my HTML..." I love being naive. So, then i looked at the code and everything was tied to everything else and there was no way to use the original code without copy / paste. and even then there were dependencies. so, yeah, reuse...wish it were already done once but we just keep on reinventing wheels. :rolleyes:
-
That sounds cool. Maybe some of the code that renders the e-books in calibre could be leveraged to give you an idea how to do that work?? But, maybe not-- since I think the calibre code is in python. Isn't it interesting that this is about re-use -- one of the holy grails of programming that has been around forever -- and we're still talking about it in 2021? A few years ago another dev had a HTML to PDF thing in their code. I said, "hey, can I get that code so I can just create PDFs from my HTML..." I love being naive. So, then i looked at the code and everything was tied to everything else and there was no way to use the original code without copy / paste. and even then there were dependencies. so, yeah, reuse...wish it were already done once but we just keep on reinventing wheels. :rolleyes:
I have an open source project that is an e-book reader that targets the ESP32 and does most of this so I'm using it as a reference. I'd use it entirely except: 1. I can't get it to build 2. I want to use its component features like HTML/CSS and truetype rendering in my GFX lib without necessarily using EPUB 3. It has no knowledge of color e-ink displays and only supports one device anyway, which i don't own. But at least it has given me a ton of ideas, and let me know of projects out there I didn't think would build on the ESP32 (but they do, because it uses them!) like freetype.
Real programmers use butterflies
-
First the little mouse wanted an epub reader Then she needed a zip library to unzip the xml Then she needed an XML parser library to decode it. Then she needed an HTML library to display the content. Then she needed a CSS library to lay out the HTML Then she needed a truetype font library to render the CSS styles *sigh* If these were designed for little CPUs why did they make the technology stack so deep? :confused: :doh:
Real programmers use butterflies