[squeak-dev] offscreen buffer/bitmap/array access

Lawson English lenglish5 at cox.net
Mon Feb 1 19:26:36 UTC 2010


Thanks John. I vaguely knew about this, but was hoping to be able to 
create an offscreen surface just by passing in an ExternalAddress to an 
existing squeak class.

The sample surface plugin looks like it might do as much as I need. Hrm. 
More reading.

Lawson



John M McIntosh wrote:
> Look at the surfacePlugin
>
> http://www.squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/Cross/plugins/SurfacePlugin/
> and a working xample . 
> http://www.squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/Mac%20OS/plugins/QuicktimePlugin/?rev=2148
>
> Also you should be aware of 
> http://bugs.squeak.org/view.php?id=5236
> which killed our usage of the QuicktimePlugin to do a surface in Sophie. However we did use the stQuicktimeSetSemaphorefor logic 
> so that quicktime could tell us when a frame rendered so we could pull the frame from quicktime to squeak. 
>
>
> On 2010-02-01, at 3:49 AM, Lawson English wrote:
>
>   
>> I've managed to work up a trivial access to the shm*   calls in Mac OS X so that I can obtain a pointer to a shared memory buffer. How can I render to this buffer without more c-level programming? The goal would be to take the shared memory address and use it to build various things like bitmaps, forms, etc. I've spent several hours rummaging around with google and searching the various squeak-related mailing lists, but there doesn't seem to be any Squeak way to draw to/write to an offscreen buffer which is only defined by an external address. Certainly, with far more work, I can devise ways to do this with FFI/plugins/etc but I'd like to prototype in smalltalk, not C.
>>
>>
>> Lawson
>>
>>     
>
> --
> ===========================================================================
> John M. McIntosh <johnmci at smalltalkconsulting.com>   Twitter:  squeaker68882
> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
> ===========================================================================
>
>
>
>
>
>
>   




More information about the Squeak-dev mailing list