Am I understanding right that it’s running terminal Emacs since it’s using efbpad? If so what would be needed to get graphical Emacs running? I’d actually be interested in using this as a development environment but I’ve heard terminal Emacs breaks some things.
enthdegree 4 days ago [-]
Yes it’s running in a terminal. GUI emacs would be nice because it can show images and rich text. People here have probably read things like this https://blog.aaronbieber.com/2016/12/29/don-t-use-terminal-e... (though the tramp criticism doesn’t apply here)
It would require further compiling an X server or Wayland, the Lucid GUI toolkit, freetype and fontconfig, a bunch of image libraries and maybe more stuff I don’t know about, plus of course all their dependencies.
It would likely take some effort to get X or Wayland to refresh the screen responsively, possibly using xdamage or Wayland protocol stuff to intelligently ask fbink to do limited refreshes.
The keyboard and touchscreen might be configurable but I haven’t done it. If it turns out to not work out of the box another option besides fighting drivers would be to be translate the event devices in /dev/input into virtual devices like efbpad kbreader does.
GUI emacs seems doable and requires, in my estimation, about “this project” again more work. The issues with the terminal version should probably be resolved before continuing. I’m unsure how much less responsive it will be than the terminal one.
Rendered at 07:10:09 GMT+0000 (UTC) with Wasmer Edge.
It would require further compiling an X server or Wayland, the Lucid GUI toolkit, freetype and fontconfig, a bunch of image libraries and maybe more stuff I don’t know about, plus of course all their dependencies.
It would likely take some effort to get X or Wayland to refresh the screen responsively, possibly using xdamage or Wayland protocol stuff to intelligently ask fbink to do limited refreshes.
The keyboard and touchscreen might be configurable but I haven’t done it. If it turns out to not work out of the box another option besides fighting drivers would be to be translate the event devices in /dev/input into virtual devices like efbpad kbreader does.
GUI emacs seems doable and requires, in my estimation, about “this project” again more work. The issues with the terminal version should probably be resolved before continuing. I’m unsure how much less responsive it will be than the terminal one.