2008/11/15 Michael Rueger <m.rueger@acm.org>:
Igor Stasenko wrote:
As you understand, this is only a tip of the iceberg. It is really scary piece of system, each time i'm looking at it, something tells me - hey pal, leave this stuff and never look at it again :)
Tell me about it.
I have something 80% finished, hope to have it ready for testing really soon now :-) It's always the 20% that gets you...
Good to hear. I'm currently trying to do something with VM part of it, to support multiple host windows and a clear way how language side can control it. But this will require changing an event dispatching scheme. Currently the events going in following way: EventSensor -> HandMorph , or even worse, consumed directly by different code. If you wanna look how easy to consume the VM event, just look at HandMorph>>processEvents (sarcasm). Instead, i suggest that events should go in different route: EventSensor -> HostWindow instance -> subscriber(s). A HostWindow instance does not know anything about subscriber(s). So it can be a HandMorph, or something else (if one wants to use a non-morphic framework, we should allow it). It is important to handle event by HostWindow at first place, because some events, obviously, will be specific to host window (like window closing notification, or window activation/deactivation). It is good, that the there is not much senders of #nextEvent , a most importrant one is HandMorph, but there is a number messy code which deals with raw event buffers spread among different XXXXXInputInterpreter classes in Multilingual-TextConversion category. I'm sure there is a number of other places like this. As i mentioned, it is highly inefficient and inhumane to force people dealing with raw event buffers with their cryptic stuff (if someone want to argue - just take a look at #nextCharFrom:firstEvt: implementations). I can't imagine how much patience people had to write up this code. And i can't imagine one who may want to fix it, if there is a bug :) I missed the discussion and was not aware that you are rewriting the events. Michael , can you, please , give me a pointers where i can read about new events design? Also, if you have some code to download, may i take a look at it? I want to know how i can integrate my stuff with it.
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.