- Pharo-users - lists.pharo.org

Re: [Pharo-users] Using FFI

by Esteban Lorenzano

mmm... but again, AFAIK... Old FFI will not work in ARM. On Oct 30, 2013, at 10:12 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > AFAIK, it should be in Configurations browser. > Else try this: > > Gofer new > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfFFI'; > load. > (Smalltalk at: #ConfigurationOfFFI) project lastVersion load > > > > On 30 October 2013 09:41, Annick Fron <info(a)afceurope.com> wrote: > My problem is that the Raspberry does not support native boost (as yet !). > Where can I load the old FFI ? > > Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > >> >> >> >> On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> wrote: >> Hi >> >> I want to launch a simple init with the following C signature : >> >> void gst_init (int *argc, char **argv[]) >> >> If I write >> >> <apicall: void 'gst_init' (int*, char**) module: 'blabla'> >> >> I get a Smalltalk syntax error >> >> Annick Fron >> >> >> To use this syntax, you must load old FFI implementation. >> Or use NativeBoost: >> >> init: intarg with: chararg >> <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> >> >> >> self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: 'blaba' >> >> >> -- >> Best regards, >> Igor Stasenko. > > > > > -- > Best regards, > Igor Stasenko.

Oct. 30, 2013

Re: [Pharo-users] Using FFI

by Igor Stasenko

AFAIK, it should be in Configurations browser. Else try this: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. (Smalltalk at: #ConfigurationOfFFI) project lastVersion load On 30 October 2013 09:41, Annick Fron <info(a)afceurope.com> wrote: > My problem is that the Raspberry does not support native boost (as yet !). > Where can I load the old FFI ? > > Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > > > > > On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> wrote: > >> Hi >> >> I want to launch a simple init with the following C signature : >> >> void gst_init (int *argc, char **argv[]) >> >> If I write >> >> <apicall: void 'gst_init' (int*, char**) module: 'blabla'> >> >> I get a Smalltalk syntax error >> >> Annick Fron >> >> > To use this syntax, you must load old FFI implementation. > Or use NativeBoost: > > init: intarg with: chararg > > <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> > > self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: > 'blaba' > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Oct. 30, 2013

Re: [Pharo-users] Using FFI

by Luc Fabresse

Hi Annick, Probably (others will correct me if I am wrong ;-)) that the easiest is to write a VM plugin, add it in your ARM-based VM and recompile it. Cheers, Luc #Luc 2013/10/30 Esteban Lorenzano <estebanlm(a)gmail.com> > Hi Annick, > > Rapsberry (ARM) does not supports FFI either (current implementation is > x86 architecture). > > Esteban > > > On Oct 30, 2013, at 5:41 AM, Annick Fron <info(a)afceurope.com> wrote: > > My problem is that the Raspberry does not support native boost (as yet !). > Where can I load the old FFI ? > > Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > > > > > On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> wrote: > >> Hi >> >> I want to launch a simple init with the following C signature : >> >> void gst_init (int *argc, char **argv[]) >> >> If I write >> >> <apicall: void 'gst_init' (int*, char**) module: 'blabla'> >> >> I get a Smalltalk syntax error >> >> Annick Fron >> >> > To use this syntax, you must load old FFI implementation. > Or use NativeBoost: > > init: intarg with: chararg > > <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> > > self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: > 'blaba' > > > -- > Best regards, > Igor Stasenko. > > > >

Oct. 30, 2013

Re: [Pharo-users] Using FFI

by Esteban Lorenzano

Hi Annick, Rapsberry (ARM) does not supports FFI either (current implementation is x86 architecture). Esteban On Oct 30, 2013, at 5:41 AM, Annick Fron <info(a)afceurope.com> wrote: > My problem is that the Raspberry does not support native boost (as yet !). > Where can I load the old FFI ? > > Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > >> >> >> >> On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> wrote: >> Hi >> >> I want to launch a simple init with the following C signature : >> >> void gst_init (int *argc, char **argv[]) >> >> If I write >> >> <apicall: void 'gst_init' (int*, char**) module: 'blabla'> >> >> I get a Smalltalk syntax error >> >> Annick Fron >> >> >> To use this syntax, you must load old FFI implementation. >> Or use NativeBoost: >> >> init: intarg with: chararg >> <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> >> >> self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: 'blaba' >> >> >> -- >> Best regards, >> Igor Stasenko. >

Oct. 30, 2013

CogVM arguments in Win32

by Torsten Bergmann

1. HEADLESS The SqueakVM had support for this and it was usable in the past <quote> -headless Tells Squeak to run without a main window. However, for allowing at least some access to Squeak, an icon is added to the system tray. If you double-click this icon, the Squeak window will show up again. </quote> Ask on the VM list - maybe the "headless" option could be fixed for Pharo VM to work again. 2. Shell_NotifyIcon route You use "apicall" pragram - so I expect you will use FFI. Note that I would not go that path because FFI its outdated and unsupported. Go the NativeBoost route - its much better! PNOTIFYICONDATA is a windows structure you would have to wrap. You could look at various examples in the "OS-Windows" package (loadable from config browser in Pharo 3.0) to get some examples of wrapped structures. I'm not sure if "Shell_NotifyIcon" is the right way - if I remember correctly from my C/C++ and SmalltalkMT times it is just used to work with the tray icons. These will usally have a menu (so you need callbacks) and the window is just invisible (receiving no events, ...) while the process is running. Note that you have to dive down into the darkness of Win API before you get enlightened here ;) Bye T.

Oct. 30, 2013

Re: [Pharo-users] CogVM arguments in Win32

by Bernat Romagosa

In this direction, I'm trying to call a function in the shell32.dll lib that apparently should let you minimize an app to the system tray, but I'm not having much luck... I guess I don't really understand what am I exactly doing. This is what I found in the MSDN<http://msdn.microsoft.com/en-us/library/bb762159%28VS.85%29.aspx> : BOOL Shell_NotifyIcon( _In_ DWORD dwMessage, _In_ PNOTIFYICONDATA lpdata ); So, I tried to translate this into Pharo as: MyClass >> minimizeToTray: dwMessage data: lpData <apicall: bool 'Shell_NotifyIcon' (dword PNOTIFYICONDATA) module: 'shell32.dll'> But it won't let me save the method, reporting it's expecting an argument before PNOTIFYICONDATA. I realize PNOTIFYICONDATA is not a primitive type, but I just don't know how to handle it... :(

Oct. 30, 2013

Re: [Pharo-users] CogVM arguments in Win32

by Bernat Romagosa

indeed, --headless does "work" but the image just dies after executing it... :( I guess some FFI research to minimize the app to tray is in place. Thanks! 2013/10/29 Esteban Lorenzano <estebanlm(a)gmail.com> > AFAIK you can't. > no matter what you do, it stills shows a pharo in the trial. > > I remember once I hid the fact that I had the app running there by > replacing the world with an "administrative morph" (just as other server > apps do). > It was not terrible cool, but it worked. > > Esteban > > On Oct 29, 2013, at 7:14 AM, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > > Ok, I see Pharo -help brings up a window with command line options, but > -headless is still firing up the GUI... any ideas? > > > 2013/10/29 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > >> Hi list! >> >> I've never used Pharo on Windows before, but we're starting to package a >> multi-platform app right now and I've just found out command line arguments >> don't work like I thought they would. I need to run the image headless, so >> I figured: >> >> bin-win32\Pharo -headless shared\Pharo2.0.image >> >> Would do the trick, but it's not working. >> >> Pharo /? doesn't give any hints either, and I can't seem to find the docs >> for the Windows VM anywhere. >> >> Does anybody know where I can find a Win32 VM reference? >> >> Thanks! >> >> -- >> Bernat Romagosa. >> > > > > -- > Bernat Romagosa. > > > -- Bernat Romagosa.

Oct. 30, 2013

moose 4.9

by Tudor Girba

We are happy to announce version 4.9 of the Moose Suite: http://moosetechnology.org/download/4.9 This is a minor release still based on Pharo 2.0. The differences from Moose 4.8 are: The Mondrian engine was removed. The transition to Roassal is now complete. - Small fixes in Roassal layouts and rendering. - Small fix in FAMIX regarding manipulation of accesses. - Small visual fix in Glamour for rendering splitters in tables. A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… The Moose Suite 4.9 comes for each platform as a separate bundle: - Moose Suite 4.9 for Mac https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-mac.zip - Moose Suite 4.9 for Windows https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-win.zip - Moose Suite 4.9 for Linux https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-linux.zip The Moose Suite 4.9 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. ((Smalltalk at: #ConfigurationOfMoose) project version: '4.9-snapshot') load

Oct. 30, 2013

Re: [Pharo-users] Using FFI

by Annick Fron

My problem is that the Raspberry does not support native boost (as yet !). Where can I load the old FFI ? Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > > > > On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> wrote: > Hi > > I want to launch a simple init with the following C signature : > > void gst_init (int *argc, char **argv[]) > > If I write > > <apicall: void 'gst_init' (int*, char**) module: 'blabla'> > > I get a Smalltalk syntax error > > Annick Fron > > > To use this syntax, you must load old FFI implementation. > Or use NativeBoost: > > init: intarg with: chararg > <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> > > self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: 'blaba' > > > -- > Best regards, > Igor Stasenko.

Oct. 30, 2013

Re: [Pharo-users] Prepared statements with PostgresV2

by Yanni Chiu

On 29/10/2013 9:32 PM, Yanni Chiu wrote: > > Looking at the postgres docs, I see PREPARE and EXECUTE. I'll try to > start up a postgres server, and see if I can get it to work. Here's an example: TestPGConnection new executeAll: #( 'PREPARE test1 (text,text,integer,text) AS INSERT INTO films (code, title, did, kind) VALUES ($1,$2,$3,$4)' 'EXECUTE test1(''T_601'', ''Yojimbo'', 106, ''Drama'')' ). TestPGConnection new executeAll: #( 'PREPARE test2 (text) AS SELECT * FROM films WHERE code LIKE $1' 'EXECUTE test2(''%0%'')' ). TestPGConnection new executeAll: #( 'EXECUTE test2(''%1%'')' ). But, the third example returned: ERROR: prepared statement "test2" does not exist So it seems to not remember the prepared statements across connection cycles. Re-sending the prepared statement isn't good for performance, but it does solve your security issue.

Oct. 30, 2013