2009/4/23 stepken <[email protected]>: > Hi, Igor! > > I've got a *brand new* design idea for PHARO ;-) > > All events (keyboard, mouse, network etc.) should be read by a separate > process, which i call ... hmmmm ... "event dispatcher". Brilliant name, > isn't it? > :)
> That one reads the event from the operating system, puts it into a > per-windowgroup "event-queue", and notifies the "view process" or > "network process" about the arrival of the event. That one sits on a > semaphore, waiting for the arrival. > Unless you going to write own *brand new* UI framework. Because modifying existing one leads to madness & frustration.. - ask Stephane ;) And in fact, things are more or less similar to what you described: there is a separate process which fetching events from VM, and then queuing them to be handled by UI process. > regards, Guido Stepken > > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
