This is cool, thanks for sharing. I recently compiled Rust / Slint on a LicheeRV Nano, which is RISC-V 64bit musl[1]. It's a little portable audio player I'm working on, the compile process is done via custom Cross docker image.<p>Currently I'm evaluating Battery Pal[2], because the TP4057 Module was not stable enough to power USB-C to 3.5mm Adapters reliably. So far it seems to work as expected.<p>1: <a href="https://github.com/nanowave-player/nanowave-ui" rel="nofollow">https://github.com/nanowave-player/nanowave-ui</a><p>2: <a href="https://pnlabs.ca/batterypal/" rel="nofollow">https://pnlabs.ca/batterypal/</a>
Great article. Hacking old kindles is fun! I encourage everyone to give it a try. The retro feel of eink makes it special for me.<p>I wrote about my experience in cross compiling zig on an old kindle some time ago.<p><a href="https://samkhawase.com/blog/zig-kindle-gdb/" rel="nofollow">https://samkhawase.com/blog/zig-kindle-gdb/</a>
This looks cool, and one of the first posts I've seen on HN in a few months where I genuinely wanted to try it.
Tangential, how does slint fare compared to Druid/egui(?)
Tangential reply, but Druid has been abandoned. The spirit lives on as Xilem, but that doesn't have much traction either. It's very... exploratory in nature.<p>I'm partial to iced, which to me is the best GUI library in Rust by far. The Discord is super active if you have questions.<p><a href="https://iced.rs/" rel="nofollow">https://iced.rs/</a>
I'm curious as well. My understanding is one notable differencse, exemplified here, is that Slint can work on embedded devices / no-std.
This is awesome! How reliable are kindle jailbreaks/avoiding updates, etc?<p>Have opted for other devices like the xteink (or a boox in the future) due to what seemed like a relatively small ecosystem around “aftermarket” kindle modifications.<p>The kindle would be a great option if it could be reliably jailbroken and loaded with custom software
Depending on your firmware version, most jailbreak guides will have you either create an empty directory with the same name as the OTA firmware file (causing any OTA downloads to fail) or install an extension called `renameotabin` which renames the binaries responsible for performing the update, rendering them inaccessible.<p>source: <a href="https://kindlemodding.org/jailbreaking/post-jailbreak/disable-ota.html" rel="nofollow">https://kindlemodding.org/jailbreaking/post-jailbreak/disabl...</a>
One of my biggest regrets is not jailbreaking my kindle before it auto updated last year
Worth noting that kobo devices are not locked down at all and run linux. They’re very easy to build for.
the code: <a href="https://github.com/sverrejb/slint-kindle-backend" rel="nofollow">https://github.com/sverrejb/slint-kindle-backend</a>
zig as a cross-compile backend for rust is so good.
Good work! I guess you need to leave it plugged in?
[flagged]