Of course there has to be a generic representation to account for OS specifics. It's a trade off. There is always a compromise. We extract meaningful data, put it in an array and let the Squeak image handle the object representation for it. That's as raw as you can and should get.

Just my two cents. :-)

Best,
Marcel




Am 26.04.2018 18:46:16 schrieb tim Rowledge <tim at rowledge.org>:


> On 26-04-2018, at 12:09 AM, Marcel Taeumel wrote:
> the VM does deliver "the rawest data possible" for most events. For mouse-wheel events, we lose the scroll-delta (or acceleration), though. And left/right wheeling from the MightyMouse. :-)

Take a look at ioProcessEvents() and related code and tell me that with a straight face! We do huge amounts of mangling of incoming events before queuing them up for the image to read. If we were passing raw stuff to the image it would be all in the image, with OS specific classes to do the work. It can be done - has been done - but it isn't trivial. The earliest Squeaks had a very narrow channel to the VM and we had to do a great deal of messing around to get it to work for non-Mac systems, a lot of which we really ought not have done. But that was 20 years ago; the sad part is how little of that we've improved.


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: SDP: Search and Destroy Pointer



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180427/c56b8751/attachment.html>