Quill: The E-Ink UI framework
quill-ui.com
quill-ui.com
It also means it's expensive. Not "corporate expensive", but "average-jane expensive".
In general we've all been spoiled by open source. Someone likely put a lot of work into this. If I were building a device like this, I'd hate to have to hire staff to build this for me, and while it could be "fun" to build, money/time would likely to be better spent elsewhere.
There's often threads on here bemoaning the lack of adoption of E-Ink screens. So clearly the community here has an interest in it.
The core idea here would seem to be a UI library optimized for e-ink, that uses TypeScript to do the actual UI:s but then relies on a Rust runtime for the actual on-target execution, or something like that. I didn't click on the page, so perhaps I got the details wrong.
They specifically mention the hardware being low-cost (ESP32s are ~$6USD)
1 - https://shop.m5stack.com/products/m5paper-esp32-development-...
It does that rendering on the class of devices you're referring to, and that's where the intersection ends.
There's enough things in an e-ink UI stack to optimize and watch out for that standard toolkits leave some gaps to fill when someone is looking to build an e-ink based product on the quick, and the tech has now gotten cheap enough there's finally a minor Cambrian explosion of those. It's a nice little startup idea.
At the moment, quite a lot of the higher-end e-ink embedded products are built with Qt, by suitable experts who know how to wrangle it for that purpose and some tricks in the stack below Qt to compensate for sub-optimal behavior by the toolkit. An experienced team can do this well, but there's a wider audience wanting to build these products.
Wonder if they did drivers for external controllers as I did, or do the waveforms directly from the MCUs, or both. I should book a demo and ask!
This sounds great, would like to see a link to this documentation.
Minor note, or question maybe, I'm not sure why this needs to be in typescript though. Eink is often accompanied by low power devices, Python and C are the usual choices for these cases.
There are no links to documentation or any information beyond a snippet of code.
Not sure of the usefulness of this post. Might be too early to be here.
linkTitles.map(title => Link(title))
to linkTitles.map(Link)
Only teasing. In all seriousness this looks really nice and reminds me that I want to get a new e-ink reader! It's been like 8 years since I last used one so I imagine the technology has come a long way.Anyone here recommend a reader if money is no object? I want the highest quality one on the market that will last years. Primarily for reading, but perhaps also some note taking.