I may be wrong but last time I checked access to the OS Graphics API was handled by the VM itself. There was a talk about decoupling that from the VM and porting it to the image but no idea if it happened.
if it was the pragma primitive inside the method that means it calls native code , the second case is using the UFFI which is the official FFI of Pharo. The Pragma needs a VM rebuild , the UFFI does not. These are the two ways that Pharo intefaces with native code (C/ObjectiveC etc). So for starters you are going to need the VMMaker which is responsible for building the VM , the good news is that it retains a lot of the live coding characteristics and can even compile smalltalk to C (Slang) which is how it keeps most of the code in Smalltalk rather than C. If the Graphics API is still inside the VM then Eliot and other contributors will be able to point you at the VM mailing list at the right direction. If it is not then pharo-dev mailing list will most likely have the developer/s responsible for porting it to the image and they will also be able to point you to the right direction. I dont think experience in smalltalk would play a big role here mainly because its a C problem than a Smalltalk problem cause those libraries that offer Retina support are written and meant to be used by C (ObjC) , this applies for both primitive pragmas and UFFI. You experience with Cocoa is going to be the crucial factor here, if you know how to do it in C , doing it in Smalltalk is relative easy. You may also be able to pintpoint the methods responsible for the rendering by inserting a breakpoint in a window's draw method. The debugger should be able to give you the stack back to the primitive/uffi call. Of course it will require a bit of navigating around but such is the nature and curse of coding. On Tue, Sep 18, 2018 at 11:13 AM andyl <andylar...@hotmail.com> wrote: > Hi, > > Has any work been done of this? If not, could someone point me in the right > direction to start it, perhaps with a list of what is already known about > the issue? I'd be willing to look at both MacOS and Windows HiDPI rendering > at the same time. > > Presumably the 64 bit MacOS build is Cocoa based, so that would be the > right > starting point? > > Although I have decades of experience of the above platforms, I'm a > relative > novice with the Smalltalk libraries - so any hints as to how the rendering > process currently hangs together (and how much is Smalltalk vs native > rendering) would be really helpful. > > Regards, > Andy. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >
