[EMAIL PROTECTED] wrote:
> | But you don't listen to a window for events. You listen to the server
> | connection ('XDisplay') for events which *refer* to windows. A window -
> | as it is seen by the application - is completely unaware of events.
>
> The ability to listen to the display as a whole not just your own
> window is a source of security problems (snooping/eavesdropping/...).
Note that I'm not out to defend X' architecure. X' shortcomings are
one reason for berlin's existence.
[...]
> Perhaps output 'structures' need to be generalised to deal with offscreen
> bitmaps,
my point exactly.
> but input should only be allowed in association with its "window".
what do you mean with 'its' ? Do you mean that each offscreen bitmap should
have a "window" it is associated with ? This would be what X refers to as
visual, i.e. a structure holding formatting info for pixels, colors etc.
Lots of windows can use the same visual. This makes my point since I'm arguing
that GGI's visual plays the role of all of them: drawawbles (which I might want
to have many), visuals (there might be a few) and event queues (generally
one, at least in a single threaded application).
Stefan
_______________________________________________________
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: [EMAIL PROTECTED]
_______________________________________________________
...ich hab' noch einen Koffer in Berlin...
