January 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Change Pharo window icon

by Eliot Miranda

Hi Vincent, On Wed, Jan 31, 2018 at 12:07 PM, <Vincent.Blondeau(a)lamresearch.com> wrote: > Hi, > > I would like to know how to change the main Pharo window icon. I saw that > there is a primitive for the title: > DisplayScreen class >> primitiveWindowTitle:string: ; primitive: > 'primitiveHostWindowTitle' module:'HostWindowPlugin' > but I cannot find one for the icon. > Should another primitive need to be implemented? > The icon is baked into the VM executable. So to change it one has to build a VM with a different icon. On Windows it is in {build.win32x86,build.win64x64}/pharo.cog.spur/Pharo.ico and the file that specifies to use Pharo.ico is {build.win32x86,build.win64x64}/pharo.cog.spur/Pharo.rc On Mac OS X it is in platforms/iOS/vm/OSX/Pharo.icns (alongside three others such as PharoImage.icns) and the file that specifies to use Pharo.icns is {build.macos32x86,build.macos64x64}/pharo.cog.spur/Makefile in setting the VM variable. The file that associates the other icons with specific file types is platforms/iOS//vm/OSX/Pharo-Info.plist If you're changing the Pharo icon let me suggest you update the icon files themselves in the opensmalltalk-vm source tree. If you're creating a new variant of the VM for some new purpose (say a special Lam VM) then let me suggest you add the icons to the opensmalltalk-vm source tree, creating special build directories for these VMs, such as {build.macos32x86,build.macos64x64}/lam.pharo.cog.spur/ If you want to do this privately, then take either of the approaches above and simply don't publish the edits. You can write a script that takes an updated checked-out opensmalltalk-vm source tree and edits it with files from a specific repository. I have such scripts and can help you with them. Hint, pax is a very convenient directory hierarchy copying tool available at least on Mac OS X. pax -rwlk will copy the trees under a sequence of directories into their corresponding places in a target tree. > Thanks! > > Vincent > > > -- _,,,^..^,,,_ best, Eliot

Jan. 31, 2018

Change Pharo window icon

by Vincent.Blondeau＠lamresearch.com

Hi, I would like to know how to change the main Pharo window icon. I saw that there is a primitive for the title: DisplayScreen class >> primitiveWindowTitle:string: ; primitive: 'primitiveHostWindowTitle' module:'HostWindowPlugin' but I cannot find one for the icon. Should another primitive need to be implemented? Thanks! Vincent

Jan. 31, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Stephane Ducasse

:) Stef On Wed, Jan 31, 2018 at 8:30 AM, Vincent BLONDEAU <vincent.blondeau(a)polytech-lille.net> wrote: > Now, yes it is. See FFICompilerPlugin :) > > Vincent > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse > Sent: mardi 30 janvier 2018 23:15 > To: Pharo Development List > Subject: Re: [Pharo-dev] FFI without the Pharo sources > > Thanks vincent. > is it the comment of some classes? > > Stef > > On Wed, Jan 31, 2018 at 3:12 AM, <Vincent.Blondeau(a)lamresearch.com> wrote: >> Hi, >> >> So, I suggest this solution: >> https://github.com/pharo-project/pharo/pull/750 >> >> It is a plugin for the OpalCompiler that can be activated with the command "FFICompilerPlugin install." >> The plugin is pragma-based to detect the methods where the arguments names should be remembered. >> The pragma should be added in the FFI API methods, i.e., the methods that are called by the FFI methods where the arguments have to be remembered. >> Example: >> >> This FFI method should remember the name of the argument named "config": >> >> repository_config: config >> ^ self >> call: #(#LGitReturnCodeEnum #git_repository_config #(#LGitConfig #* #config #, #self)) >> options: #() >> >> So, the FFI function should wear the pragma <ffiCalloutTranslator>: >> >> call: fnSpec options: options >> <ffiCalloutTranslator> >> ^ (self safeFFICalloutIn: thisContext sender) >> cdecl; >> options: options; >> function: fnSpec module: self ffiLibraryName >> >> To remove to be able to remove the sources (.changes and .sources), you only have to activate the plugin, no recompilation is necessary. You can even import new FFI methods or change the FFI API. >> >> N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) also have to wear the pragma. >> >> Cheers, >> Vincent >> >> -----Original Message----- >> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf >> Of Stephane Ducasse >> Sent: Wednesday, January 24, 2018 9:21 >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] FFI without the Pharo sources >> >> So if you implement a cool solution we will integrate it immediately >> :) >> >> On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> Thanks Vincent we are interested to make the independence on source >>> much simpler. >>> >>> Stef >>> >>> >>> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>> Hi Vincent, >>>> >>>>> On Jan 23, 2018, at 4:54 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >>>>> >>>>> Does someone (Esteban?) have a solution that I could implement to fix this issue? >>>> >>>> One avenue that should be easy to implement would be to modify the compiler to save the temporary names as a property of the method. >>>> >>>> >>>>> >>>>> Thanks! >>>>> >>>>> Vincent >>>> >>>> _,,,^..^,,,_ (phone) >> > > >

Jan. 31, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Vincent BLONDEAU

Thanks Marcus! It seems that the tests are OK now: https://github.com/pharo-project/pharo/pull/750 Vincent -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Marcus Denker Sent: mardi 30 janvier 2018 23:40 To: Pharo Development List Subject: Re: [Pharo-dev] FFI without the Pharo sources I wil merge the PR after the test ran a last time. > On 31 Jan 2018, at 08:30, Vincent BLONDEAU <vincent.blondeau(a)polytech-lille.net> wrote: > > Now, yes it is. See FFICompilerPlugin :) > > Vincent > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf > Of Stephane Ducasse > Sent: mardi 30 janvier 2018 23:15 > To: Pharo Development List > Subject: Re: [Pharo-dev] FFI without the Pharo sources > > Thanks vincent. > is it the comment of some classes? > > Stef > > On Wed, Jan 31, 2018 at 3:12 AM, <Vincent.Blondeau(a)lamresearch.com> wrote: >> Hi, >> >> So, I suggest this solution: >> https://github.com/pharo-project/pharo/pull/750 >> >> It is a plugin for the OpalCompiler that can be activated with the command "FFICompilerPlugin install." >> The plugin is pragma-based to detect the methods where the arguments names should be remembered. >> The pragma should be added in the FFI API methods, i.e., the methods that are called by the FFI methods where the arguments have to be remembered. >> Example: >> >> This FFI method should remember the name of the argument named "config": >> >> repository_config: config >> ^ self >> call: #(#LGitReturnCodeEnum #git_repository_config #(#LGitConfig #* #config #, #self)) >> options: #() >> >> So, the FFI function should wear the pragma <ffiCalloutTranslator>: >> >> call: fnSpec options: options >> <ffiCalloutTranslator> >> ^ (self safeFFICalloutIn: thisContext sender) >> cdecl; >> options: options; >> function: fnSpec module: self ffiLibraryName >> >> To remove to be able to remove the sources (.changes and .sources), you only have to activate the plugin, no recompilation is necessary. You can even import new FFI methods or change the FFI API. >> >> N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) also have to wear the pragma. >> >> Cheers, >> Vincent >> >> -----Original Message----- >> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf >> Of Stephane Ducasse >> Sent: Wednesday, January 24, 2018 9:21 >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] FFI without the Pharo sources >> >> So if you implement a cool solution we will integrate it immediately >> :) >> >> On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> Thanks Vincent we are interested to make the independence on source >>> much simpler. >>> >>> Stef >>> >>> >>> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>> Hi Vincent, >>>> >>>>> On Jan 23, 2018, at 4:54 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >>>>> >>>>> Does someone (Esteban?) have a solution that I could implement to fix this issue? >>>> >>>> One avenue that should be easy to implement would be to modify the compiler to save the temporary names as a property of the method. >>>> >>>> >>>>> >>>>> Thanks! >>>>> >>>>> Vincent >>>> >>>> _,,,^..^,,,_ (phone) >> > > >

Jan. 31, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Recording Pharo Techtalk Jan18

by Alexandre Bergel

Thanks Marcus for organizing these events. Alexandre > On Jan 31, 2018, at 7:14 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > The recording and slides for yesterdays TechTalk are available: > > Topic: Genetic Algorithms > > PDF: > http://files.pharo.org/media/techtalk/2018-TechTalk-AI-GeneticAlgorithm.pdf > > Video on Youtube: > https://www.youtube.com/watch?v=ZB1U259wPaA > > (added to the archive at http://pharo.org/TechTalk ) > > Future TechTalks: > > > â¢ Feb 15: Contributing to Pharo 7. > https://association.pharo.org/event-2797065 > > â¢ March 22: Report 2017 Pharo Consortium and Association. > https://association.pharo.org/event-2797067 > > â¢ April 12: Pillar. > https://association.pharo.org/event-2797068 > > â¢ May 17: TBA > > â¢ June 14 TBA > > > Marcus

Jan. 31, 2018

[ANN] Recording Pharo Techtalk Jan18

by Marcus Denker

Hi, The recording and slides for yesterdays TechTalk are available: Topic: Genetic Algorithms PDF: http://files.pharo.org/media/techtalk/2018-TechTalk-AI-GeneticAlgorithm.pdf Video on Youtube: https://www.youtube.com/watch?v=ZB1U259wPaA (added to the archive at http://pharo.org/TechTalk ) Future TechTalks: â¢ Feb 15: Contributing to Pharo 7. https://association.pharo.org/event-2797065 â¢ March 22: Report 2017 Pharo Consortium and Association. https://association.pharo.org/event-2797067 â¢ April 12: Pillar. https://association.pharo.org/event-2797068 â¢ May 17: TBA â¢ June 14 TBA Marcus

Jan. 31, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Marcus Denker

I wil merge the PR after the test ran a last time. > On 31 Jan 2018, at 08:30, Vincent BLONDEAU <vincent.blondeau(a)polytech-lille.net> wrote: > > Now, yes it is. See FFICompilerPlugin :) > > Vincent > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse > Sent: mardi 30 janvier 2018 23:15 > To: Pharo Development List > Subject: Re: [Pharo-dev] FFI without the Pharo sources > > Thanks vincent. > is it the comment of some classes? > > Stef > > On Wed, Jan 31, 2018 at 3:12 AM, <Vincent.Blondeau(a)lamresearch.com> wrote: >> Hi, >> >> So, I suggest this solution: >> https://github.com/pharo-project/pharo/pull/750 >> >> It is a plugin for the OpalCompiler that can be activated with the command "FFICompilerPlugin install." >> The plugin is pragma-based to detect the methods where the arguments names should be remembered. >> The pragma should be added in the FFI API methods, i.e., the methods that are called by the FFI methods where the arguments have to be remembered. >> Example: >> >> This FFI method should remember the name of the argument named "config": >> >> repository_config: config >> ^ self >> call: #(#LGitReturnCodeEnum #git_repository_config #(#LGitConfig #* #config #, #self)) >> options: #() >> >> So, the FFI function should wear the pragma <ffiCalloutTranslator>: >> >> call: fnSpec options: options >> <ffiCalloutTranslator> >> ^ (self safeFFICalloutIn: thisContext sender) >> cdecl; >> options: options; >> function: fnSpec module: self ffiLibraryName >> >> To remove to be able to remove the sources (.changes and .sources), you only have to activate the plugin, no recompilation is necessary. You can even import new FFI methods or change the FFI API. >> >> N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) also have to wear the pragma. >> >> Cheers, >> Vincent >> >> -----Original Message----- >> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf >> Of Stephane Ducasse >> Sent: Wednesday, January 24, 2018 9:21 >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] FFI without the Pharo sources >> >> So if you implement a cool solution we will integrate it immediately >> :) >> >> On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> Thanks Vincent we are interested to make the independence on source >>> much simpler. >>> >>> Stef >>> >>> >>> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>> Hi Vincent, >>>> >>>>> On Jan 23, 2018, at 4:54 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >>>>> >>>>> Does someone (Esteban?) have a solution that I could implement to fix this issue? >>>> >>>> One avenue that should be easy to implement would be to modify the compiler to save the temporary names as a property of the method. >>>> >>>> >>>>> >>>>> Thanks! >>>>> >>>>> Vincent >>>> >>>> _,,,^..^,,,_ (phone) >> > > >

Jan. 31, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Vincent BLONDEAU

Now, yes it is. See FFICompilerPlugin :) Vincent -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse Sent: mardi 30 janvier 2018 23:15 To: Pharo Development List Subject: Re: [Pharo-dev] FFI without the Pharo sources Thanks vincent. is it the comment of some classes? Stef On Wed, Jan 31, 2018 at 3:12 AM, <Vincent.Blondeau(a)lamresearch.com> wrote: > Hi, > > So, I suggest this solution: > https://github.com/pharo-project/pharo/pull/750 > > It is a plugin for the OpalCompiler that can be activated with the command "FFICompilerPlugin install." > The plugin is pragma-based to detect the methods where the arguments names should be remembered. > The pragma should be added in the FFI API methods, i.e., the methods that are called by the FFI methods where the arguments have to be remembered. > Example: > > This FFI method should remember the name of the argument named "config": > > repository_config: config > ^ self > call: #(#LGitReturnCodeEnum #git_repository_config #(#LGitConfig #* #config #, #self)) > options: #() > > So, the FFI function should wear the pragma <ffiCalloutTranslator>: > > call: fnSpec options: options > <ffiCalloutTranslator> > ^ (self safeFFICalloutIn: thisContext sender) > cdecl; > options: options; > function: fnSpec module: self ffiLibraryName > > To remove to be able to remove the sources (.changes and .sources), you only have to activate the plugin, no recompilation is necessary. You can even import new FFI methods or change the FFI API. > > N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) also have to wear the pragma. > > Cheers, > Vincent > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf > Of Stephane Ducasse > Sent: Wednesday, January 24, 2018 9:21 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] FFI without the Pharo sources > > So if you implement a cool solution we will integrate it immediately > :) > > On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Thanks Vincent we are interested to make the independence on source >> much simpler. >> >> Stef >> >> >> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> Hi Vincent, >>> >>>> On Jan 23, 2018, at 4:54 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >>>> >>>> Hi, >>>> >>>> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >>>> >>>> Does someone (Esteban?) have a solution that I could implement to fix this issue? >>> >>> One avenue that should be easy to implement would be to modify the compiler to save the temporary names as a property of the method. >>> >>> >>>> >>>> Thanks! >>>> >>>> Vincent >>> >>> _,,,^..^,,,_ (phone) >

Jan. 31, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Stephane Ducasse

Thanks vincent. is it the comment of some classes? Stef On Wed, Jan 31, 2018 at 3:12 AM, <Vincent.Blondeau(a)lamresearch.com> wrote: > Hi, > > So, I suggest this solution: https://github.com/pharo-project/pharo/pull/750 > > It is a plugin for the OpalCompiler that can be activated with the command "FFICompilerPlugin install." > The plugin is pragma-based to detect the methods where the arguments names should be remembered. > The pragma should be added in the FFI API methods, i.e., the methods that are called by the FFI methods where the arguments have to be remembered. > Example: > > This FFI method should remember the name of the argument named "config": > > repository_config: config > ^ self > call: #(#LGitReturnCodeEnum #git_repository_config #(#LGitConfig #* #config #, #self)) > options: #() > > So, the FFI function should wear the pragma <ffiCalloutTranslator>: > > call: fnSpec options: options > <ffiCalloutTranslator> > ^ (self safeFFICalloutIn: thisContext sender) > cdecl; > options: options; > function: fnSpec module: self ffiLibraryName > > To remove to be able to remove the sources (.changes and .sources), you only have to activate the plugin, no recompilation is necessary. You can even import new FFI methods or change the FFI API. > > N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) also have to wear the pragma. > > Cheers, > Vincent > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse > Sent: Wednesday, January 24, 2018 9:21 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] FFI without the Pharo sources > > So if you implement a cool solution we will integrate it immediately :) > > On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Thanks Vincent we are interested to make the independence on source >> much simpler. >> >> Stef >> >> >> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> Hi Vincent, >>> >>>> On Jan 23, 2018, at 4:54 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >>>> >>>> Hi, >>>> >>>> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >>>> >>>> Does someone (Esteban?) have a solution that I could implement to fix this issue? >>> >>> One avenue that should be easy to implement would be to modify the compiler to save the temporary names as a property of the method. >>> >>> >>>> >>>> Thanks! >>>> >>>> Vincent >>> >>> _,,,^..^,,,_ (phone) >

Jan. 31, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Vincent.Blondeau＠lamresearch.com

Hi, So, I suggest this solution: https://github.com/pharo-project/pharo/pull/750 It is a plugin for the OpalCompiler that can be activated with the command "FFICompilerPlugin install." The plugin is pragma-based to detect the methods where the arguments names should be remembered. The pragma should be added in the FFI API methods, i.e., the methods that are called by the FFI methods where the arguments have to be remembered. Example: This FFI method should remember the name of the argument named "config": repository_config: config ^ self call: #(#LGitReturnCodeEnum #git_repository_config #(#LGitConfig #* #config #, #self)) options: #() So, the FFI function should wear the pragma <ffiCalloutTranslator>: call: fnSpec options: options <ffiCalloutTranslator> ^ (self safeFFICalloutIn: thisContext sender) cdecl; options: options; function: fnSpec module: self ffiLibraryName To remove to be able to remove the sources (.changes and .sources), you only have to activate the plugin, no recompilation is necessary. You can even import new FFI methods or change the FFI API. N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) also have to wear the pragma. Cheers, Vincent -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse Sent: Wednesday, January 24, 2018 9:21 To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] FFI without the Pharo sources So if you implement a cool solution we will integrate it immediately :) On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks Vincent we are interested to make the independence on source > much simpler. > > Stef > > > On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> Hi Vincent, >> >>> On Jan 23, 2018, at 4:54 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >>> >>> Hi, >>> >>> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >>> >>> Does someone (Esteban?) have a solution that I could implement to fix this issue? >> >> One avenue that should be easy to implement would be to modify the compiler to save the temporary names as a property of the method. >> >> >>> >>> Thanks! >>> >>> Vincent >> >> _,,,^..^,,,_ (phone)

Jan. 31, 2018