3 ms·
This is just m5paper with the claim of developer friendly environment [1] 1 - https://shop.m5stack.com/products/m5paper-esp32-development-kit-v1-1-960x540-4-7-
by isawczuk 3y ago
This is just m5paper with the claim of developer friendly environment [1]
1 - https://shop.m5stack.com/products/m5paper-esp32-development-kit-v1-1-960x540-4-7-eink-display-235-ppi https://shop.m5stack.com/products/m5paper-esp32-development-...
- cmrdporcupine 3y agoThat's clearly not what's being advertised here and this seems remarkably dismissive and incorrect. It's a library to do e-ink graphics -- which have different characteristics than standard raster rendering, so something like this makes sense. It does that rendering on the class of devices you're referring to, and that's where the intersection ends.
- sho_hn 3y agoI've built a simpler version of part of what they advertise (also with Rust and on an esp32, https://imgur.com/a/NoTr8XX https://imgur.com/a/NoTr8XX) and have a lot of experience with traditional GUI toolkits, and I would agree there's a decent value prop in what they describe. 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!