2008/11/15 Michael Rueger <m.rueger@acm.org>:
Igor Stasenko wrote:
Instead, i suggest that events should go in different route: EventSensor -> HostWindow instance -> subscriber(s).
A subscriber model is part of my design, allowing for pluggable event architectures actually. I'm not going to change the current Morphic event handling itself, that would require rewriting most of the system.
Heh :)
I will publish code as soon as I can make it load and run somewhat safely. Swapping out the event handling is, let's say, interesting ;-)
Reagarding another suggestion in an earlier mail, I don't think the event object creation should be in the VM. The raw, barebones event structure is the most flexible, anything else can and should be handled in the image.
I'm ok with it. What i hate to see is the countless places dealing with bare bones instead of single place which converts this stuff into a nice wrappings with simple and understandable behavior/protocol - so you can easily extract any bit of information from event in human friendly manner and forget about using bare event buffers at all.
More on that later.
Michael
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.