How does PicoGUI perform for applications that need to update large parts of the screen very often, without using the provided widgets (games, video players…)?
Probably about as well as X or any other GUI that supports shared memory segments. PicoGUI supports a shared memory mechanism very similar to X’s MIT-SHM. This allows the picogui server direct access to the app’s framebuffer, but still requires a blit to copy that to the real framebuffer. In the future it’s planned that picogui will support a faster (but more dangerous) method of allowing the app truly direct access to the framebuffer, similar to DGA.
Related Questions
- How does PicoGUI perform for applications that need to update large parts of the screen very often, without using the provided widgets (games, video players...)?
- My applications work with large databases. How does a Visual ProMatrix application perform with hundreds of thousands, or even millions, of records?
- Where can I perform a large compound screen?
