Shérab, on Tue 17 Nov 2015 15:04:54 +0100, wrote: > Samuel Thibault (2015/11/17 14:06 +0100): > > The problem is that these userland-driven terminals don't provide the > > screen output. Ideally we'd manage to gather the people implementing > > them, and get to define a common interface to access the screen > > output. > > Isn't AT-SPI good enough for that? Or is it too heavy for instance?
It is heavy for performance (at *best* thousands of requests per second), and it is really not suited to getting terminal information. The AccessibleTerminal interface has never been actually implemented. Generally speaking, the way AT-SPI works seems overkill to me here. The way it works (insertion/removal notification) really does not suit terminal screen reading. A shared-memory solution looking like /dev/vcsa, but rethought for unicode etc. would work much better. Samuel _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
