window manager

[twobob]

AFAIK no.

You could speak to the duokan team and ask. They might tell you. Thomass has their email IIRC

One thing we haven't outlined here is we now know where, why and how it is done. Also what is done.

[h1ro]

well, it seems like some lua scripts belonging to awesome receive Xdamage messages and with this info tell the e-ink screen to update.

the former killing of awesome was just done by upstart respawning lxinit, which got killed when we killed awesome.

if you cut upstart out of the loop you can start Xorg manually and start and kill awesome as often as you want without getting your Xorg killed and the whole framework restarted.

[twobob]

nice precis.

Yes. I could easily put together a "drop down list" and WM selector once we have the client "einkdamage" sorted. No doubt this will all seem trivially obvious in a few weeks time and infuriatingly elusive for the next "X amount of time" : )

[NullNix]

Originally Posted by twobob

yup. we are hacking on it in #kindle-dev... if you fancy throwing your weight in...

I have to finish migrating to awesome and hacking it about locally first, before I try it on a device that I use all the time and that can't be unbricked if it goes wrong.

[twobob]

Agreed. 100%