libremarkable VS microwindows

> I rather mean the firmware of the e-ink driver board, which is a trade secret. I don't know, maybe it is not even firmware in an MCU, but they have a dedicated driver chip and it just has the look-up-tables. Anyway, the secret sauce that tells you how to drive the display cells.

Huh? What e-ink driver board? There's no such thing inside a Kindle. It is a straight NXP SoC that drives the e-ink panel directly. There is no MCU. The driver is open source. https://github.com/canselcik/libremarkable/blob/master/refer...

"Secret sauce that tells you how to drive the display cells"? You mean like a voltage table that is also present inside every LCD or OLED? The difference would be that the electrophoretic display would need a much bigger table so it would have to be kept on the SoC. That's not software, that's just a big table of voltages that's hardcoded for each unique panel. Is that what you think is "secret sauce"?

Maybe take a look at https://github.com/canselcik/libremarkable

Well, it'd be easy to test out the latency of a libremarkable demo and compare it to the default software.

First, the remarkable is a fantastic device! However it would be even better (in my opinion) if on the menu of the ui below the "Ebooks" tab there was an "Applications" tab where users could add binaries/applications of there own choosing and run them from within the xochitl ui. There is an active community of hackers and enthusiasts who are writing applications for the remarkable that would greatly appreciate a supported means of running custom programs from within the existing ui, without having to utilize a 3rd-party launcher or leave xochitl. relevant links: https://github.com/LinusCDE/retris https://github.com/canselcik/libremarkable

a) The (actually multitouch capable) finger recognition is a separate piece of hardware to the pen recognition: See https://github.com/canselcik/libremarkable/wiki/Hardware-Overview, especially Reading from Wacom I2C Digitizer Reading Parade TrueTouch Gen5 Multitouch Input

Interesting link!

If we look at this directory:

https://github.com/ghaerr/microwindows/tree/master/src/drive...

Most notably the source files that start with 'scr_', and of those most notably: scr_sdl2.c, scr_win32.c, scr_x11.c, scr_djvesa.c, scr_fb.c -- we see that this windowing system can apparently run on top of an existing windowing system, whether that system is SDL2, Win32, X11, VESA, Linux's framebuffer -- or several others.

Which makes it interesting and worthy of study...

Note that I am sure there are probably a whole lot of other windowing systems out there that also support these, let's call them "back-end" (for lack of better terminology) pre-existing windowing systems.

In other words, a windowing system -- on top of another windowing system...

Sort of like running X on top of Win32, or Win32 on top X...

But the posibilities of higher level and lower level windowing system are really unlimited -- mix and match, basically...

In conclusion -- excellent link!

I worked on this [1] Linux tablet 20 years ago, and we had working versions, but it doesn't really count as they weren't put into mass production. I don't know how many were built in the end (I left to co-found a webmail service). Sometimes it's depressing how long it takes for something to actually come to fruition. The screenshots in [1] are our custom UI based on NanoX [2], and an Opera port for the web browser screenshot (it worked). I wanted a production version for years after I left...

[1] https://linuxdevices.org/freepad-norways-alternative-to-swed...

[2] https://github.com/ghaerr/microwindows