Update 2:
I looked at the InstallFFI4.st and discovered http://source.squeakfoundation.org/FFI
 
where I found 'FFI-Kernel-ar.9.mcz', 'FFI-Tests-ar.2.mcz', 'FFI-Examples-ar.1.mcz'
convertable to .zip files by changing the extension.  Then I attempted to fileIn.
Cuis accepted the Kernal and Tests but failed on the Examples due to MacIntosh classes which Cuis doesn't support.

Unfortunately that still was insufficient to accept the example at http://wiki.squeak.org/squeak/2422 but the error is now different:

getFocus
"Return the HWND currently having the input focus"
<apicall:  return type expected ->Win32Window 'GetFocus' (void) module: 'user32.dll'>
^self externalCallFailed

So any advice?  

I'm under the impression Cuis was never intended to use FFI but to do direct binary input without a C.dll but unfortunately the details of how to do that for VideoFlow are also beyond my knowledge.  Where would I learn that?

Thanks,
Kirk Fraser



On Wed, Sep 7, 2011 at 5:53 PM, Overcomer Man <overcomer.man@gmail.com> wrote:
Update.  
I located the FFI install which works with Squeak 4.2 but fails on Cuis 3.3
http://map.squeak.org/accountbyid/cf58c358-46ee-465e-b6db-2740e9b32a53/files/InstallFFI4.st

That failed with this error walkback:
UndefinedObject(Object)>>doesNotUnderstand: #location:user:password:

Juan says it uses Monticello not included in Cuis.  Any suggestions on how to tweak installFFI4.st to work under Cuis?   Thanks.



On Wed, Sep 7, 2011 at 12:27 PM, Overcomer Man <overcomer.man@gmail.com> wrote:
FFI - Foriegn Function Interface example given at http://wiki.squeak.org/squeak/2422 fails to compile under a test class, so it can't work.  The error is expecting a '>' which implies the apicall is wrong.  Since it's example code, it's likely correct and the parser is not working. 
 
I assumed it was a failure of FFI to be installed properly in Squeak 4.2 All-In-One.  I tried the FFI install .st which gave an error about an unrecognized password.  (I have since been unable to locate that code to put the error and link in this post.)  
 
This is confusing since the FFI .dll comes with the All-In-One so it must be used somewhere.
 
Any suggestions?  Getting FFI code to accept is needed in my attempt to load the old video package or try openCV.