stepharo wrote in "[Pharo-dev] Visit/accept method naming philosophy":
ben pay attention that OSWindow needs a real polish phase. We logged some items to be fixed in the pharo roadmaps on github in Events.md
Thanks for the reference. Actually it answers some questions I had. I had started to review Case 14404 [1] "extend MorphicEventHandler with #mouseOver and replace all uses of MouseOverEventHandler" and thought it might be useful to add some tests of the existing mouseover, which sent me investigating InputEventFetcher. [1] https://pharo.fogbugz.com/default.asp?14404 I had some seed ideas to introduce a class to replace the eventBuffer Array in InputEventFetcher>>eventLoop, but then (besides performance considerations) wondered what was being disposed of when OSWindow was done. I think maybe I could help with: 1. move the logic of the InputEventFetcher to the OSVMWindowDriver (represents the old system within the OSWindow frameworks). -- but I don't see OSVMWindowDriver in build 40360. 2. OSWindowMorphicEventHandler>>dispatchMorphicEvent: anEvent should rewritten with a more efficient. we should remove the use of defer: 3. Adding some tests to document existing sequencing of #handlesMouseOver:, #handlesDoubleClick: etc... 4. General testing. So how can I get started? * I see a mention a while back of needing a custom VM. Is this still the case? Which VM should I use? * I see CI job https://ci.inria.fr/pharo-contribution/job/OSWindow/ started a week ago but currently disabled. * I see two repositories. Which to use? http://smalltalkhub.com/#!/~Pharo/OSWindow http://smalltalkhub.com/#!/~ronsaldo/OSWindow/commits * How to coordinate? cheers -ben