|
From: James S. <jsi...@ac...> - 2000-03-16 03:12:13
|
> In KGI terminology "focus" refers to a collection of physical input > device > drivers or event sources. E.g mice, graphic tablets, user specific > applications, etc. All events generated by these event sources will > be reported to the same event sink (input device). Currently this may > be the input device of a terminal emulator. Later a /dev/event mapper > will be added. Okay. the Y input devices of a head is a focus. Vojtech has /dev/event and a input device and it's being used for USB devices. Now that Vojtech work will be head into CVS very soon you can take a look at what he has done and we can combine whatever both of you have developed. I hope you still see a tty as just one keyboard and one display. Linus doesn't care for people breaking the rules. I think he will not mind the flexable api of where we can build a head from userland. > A "head" (or workplace as I prefer) in KGI terminology refers to a focus > and all output devices --simply speaking-- this focus may be focused on. Okay. X input devices and Y output devices. > A "workplace" may consist of several heads. Thast teh whole machine. You can have a bunch of heads per machine normally. > Why have I split this? Because this avoids unneccessary constraints > on what virtual terminal is displayed on what display and each > KGI-head may appear to be a multidisplay workplace. So /dev/vc/X appears to userland as one big VT pool even if internally where have a bunch of VT pools to each console. We just have to make sure you can't VT switch from one head to another head. If the heads are in two different offices then if we VT switch to another VT that's in another office I really don't feel like getting up and going to another office to use another VT. "Look it's a text editor, no it's a OS, no it's Emacs" James Simmons ____/| fbdev/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U |