Introduce a nitpicker option to choose the framebuffer back end between the use of a requested framebuffer session (as done today), the use of a capture client for the pixel output, or the use of another GUI server (for stacking multiple instance of nitpicker).
The new capture session interface of the nitpicker GUI server would be the right hook for implementing screenshot/screencast applications, or a remote desktop server.
Of course, the drivers cannot talk to nitpicker GUI server via nitpicker's regular client interface.
At the lowest level, the framebuffer driver and input driver(s) were envisioned as servers that provide the Framebuffer and Input session interfaces to higher-level GUI components.
Introducing the new Event session interface and adding its implementation to the nitpicker GUI server.
I really appreciate you for taking the time to write me this feedback.
I received your feedback.
I am sorry!
An error occurred and we could not transfer your message.
Please try again or get in contact with us via mail.