July 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Commandline

by Thierry Goubier

You can try to get the current working directory this way: argumentsAsFileReferences |pwd | pwd := (Smalltalk os environment at: 'PWD' ifAbsent: [ Smalltalk os environment at: 'CD' ]) asFileReference. ^ self argumentsWithoutOptions collect: [ :each | pwd resolveReference: each asFileReference ] This works when passing arbitrary files as argument to a shell script doing an exec on arbitraryPath/pharo afterwards. (This is how GitFileTree-MergeDriver handles being called by git with file paths). Now, it would be necessary to fix that on the default .st loading :) Thierry Le 25/07/2014 22:05, Sven Van Caekenberghe a Ã©crit : > Yes, for some reason, the shebang (#!) machinery passes ./test2.st as argument to pharo, which it seems can only be resolved if it is in the image directory (as opposed to the current shell directory). > > I have no time to look at this now, but I vaguely remember that pharo mixed the concept of current working directory and image directory (at least in some places). > > On 25 Jul 2014, at 21:43, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > >> Sven, >> Without putting a test.st file in /Users/daleh/gsDevKitHome/pharo, I get the following (it works if I `cp ./test.st /Users/daleh/gsDevKitHome/pharo`): >> >> nehalem:junk daleh$ pwd >> /Users/daleh/junk >> nehalem:junk daleh$ cat test.st >> #!/Users/daleh/gsDevKitHome/pharo/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/daleh/gsDevKitHome/pharo/todeClient.image st --quit >> FileStream stdout nextPutAll: 42 factorial asString; cr. >> nehalem:junk daleh$ ./test.st >> FileDoesNotExist: File @ /Users/daleh/gsDevKitHome/pharo/test.st >> FileHandle>>streamError >> FileHandle>>readStream >> FileSystem>>readStreamOn: >> FileReference>>readStream >> FileReference(AbstractFileReference)>>readStreamDo: >> STCommandLineHandler>>installSourceFile: >> STCommandLineHandler>>installSourceFiles in Block: [ :reference | self installSourceFile: reference ]...etc... >> OrderedCollection>>do: >> STCommandLineHandler>>installSourceFiles in Block: [ sourceFiles do: [ :reference | self installSourc...etc... >> BlockClosure>>ensure: >> STCommandLineHandler>>installSourceFiles >> STCommandLineHandler>>activate >> STCommandLineHandler class(CommandLineHandler class)>>activateWith: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] >> BlockClosure>>on:do: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: >> PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand >> PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self handleArgument: (self arguments ifEmpty: [ ...etc... >> BlockClosure>>on:do: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activate >> PharoCommandLineHandler>>activate >> PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: >> PharoCommandLineHandler class>>activateWith: in Block: [ super activateWith: aCommandLine ] >> WorldState>>runStepMethodsIn: >> WorldMorph>>runStepMethods >> WorldState>>doOneCycleNowFor: >> WorldState>>doOneCycleFor: >> WorldMorph>>doOneCycle >> MorphicUIManager>>spawnNewProcess in Block: [ ... >> >> >> >> On Fri, Jul 25, 2014 at 12:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> On 25 Jul 2014, at 21:25, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >> >>> Sven, >>> >>> I'm using Pharo3.0 and it appears that the .st scripts have to be located in the same directory as the image and changes files ... I see that you are using Pharo4.0 ... >>> >>> So is it possible to get Pharo3.0 to work on .st files in arbitary directores? >> Are you using the shebang or direct version ? >> In any case, I am always using absolute paths. >> Does that not work for you ? >> >>> Dale >>> >>> >>> On Thu, Jul 24, 2014 at 7:42 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: >>> >>>> One question I have is how fast the load of an image and processing by an image is when compared with bash. >>> Obviously, it is slower, there is a whole image that needs to be loaded, etc. >>> >>> $ cat test.st >>> #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/sven/tmp/pharo4/Pharo.image st --quit >>> FileStream stdout nextPutAll: 42 factorial asString; cr. >>> >>> $ time ./test.st >>> 1405006117752879898543142606244511569936384000000000 >>> >>> real 0m0.644s >>> user 0m0.516s >>> sys 0m0.067s >>> >>> So about half a second overhead. >>> >>> Sven >>> >> >> > > >

July 25, 2014

Re: [Pharo-users] Commandline

by Dale Henrichs

Sven, It was just that in your example you didn't mention that the .st file had to be in the image directory and I was sorta hoping that there was a real solution to that problem ... It does mean that for gsDevKit I will still need to use bash wrapper files for all scripts that may be copied to arbitrary locations on disk ... oh well ... If that problem gets fixed, I will convert gsDevKit to use pharo-based scripts for almost everything:) Dale On Fri, Jul 25, 2014 at 1:05 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Yes, for some reason, the shebang (#!) machinery passes ./test2.st as > argument to pharo, which it seems can only be resolved if it is in the > image directory (as opposed to the current shell directory). > > I have no time to look at this now, but I vaguely remember that pharo > mixed the concept of current working directory and image directory (at > least in some places). > > On 25 Jul 2014, at 21:43, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> > wrote: > > > Sven, > > Without putting a test.st file in /Users/daleh/gsDevKitHome/pharo, I > get the following (it works if I `cp ./test.st > /Users/daleh/gsDevKitHome/pharo`): > > > > nehalem:junk daleh$ pwd > > /Users/daleh/junk > > nehalem:junk daleh$ cat test.st > > > #!/Users/daleh/gsDevKitHome/pharo/pharo-vm/Pharo.app/Contents/MacOS/Pharo > --headless /Users/daleh/gsDevKitHome/pharo/todeClient.image st --quit > > FileStream stdout nextPutAll: 42 factorial asString; cr. > > nehalem:junk daleh$ ./test.st > > FileDoesNotExist: File @ /Users/daleh/gsDevKitHome/pharo/test.st > > FileHandle>>streamError > > FileHandle>>readStream > > FileSystem>>readStreamOn: > > FileReference>>readStream > > FileReference(AbstractFileReference)>>readStreamDo: > > STCommandLineHandler>>installSourceFile: > > STCommandLineHandler>>installSourceFiles in Block: [ :reference | self > installSourceFile: reference ]...etc... > > OrderedCollection>>do: > > STCommandLineHandler>>installSourceFiles in Block: [ sourceFiles do: [ > :reference | self installSourc...etc... > > BlockClosure>>ensure: > > STCommandLineHandler>>installSourceFiles > > STCommandLineHandler>>activate > > STCommandLineHandler class(CommandLineHandler class)>>activateWith: > > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in > Block: [ aCommandLinehandler activateWith: commandLine ] > > BlockClosure>>on:do: > > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > > PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ > self handleArgument: (self arguments ifEmpty: [ ...etc... > > BlockClosure>>on:do: > > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > > PharoCommandLineHandler>>activate > > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > > PharoCommandLineHandler class>>activateWith: in Block: [ super > activateWith: aCommandLine ] > > WorldState>>runStepMethodsIn: > > WorldMorph>>runStepMethods > > WorldState>>doOneCycleNowFor: > > WorldState>>doOneCycleFor: > > WorldMorph>>doOneCycle > > MorphicUIManager>>spawnNewProcess in Block: [ ... > > > > > > > > On Fri, Jul 25, 2014 at 12:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > On 25 Jul 2014, at 21:25, Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > > > > > Sven, > > > > > > I'm using Pharo3.0 and it appears that the .st scripts have to be > located in the same directory as the image and changes files ... I see > that you are using Pharo4.0 ... > > > > > > So is it possible to get Pharo3.0 to work on .st files in arbitary > directores? > > > > Are you using the shebang or direct version ? > > In any case, I am always using absolute paths. > > Does that not work for you ? > > > > > Dale > > > > > > > > > On Thu, Jul 24, 2014 at 7:42 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > > > On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: > > > > > > > One question I have is how fast the load of an image and processing > by an image is when compared with bash. > > > > > > Obviously, it is slower, there is a whole image that needs to be > loaded, etc. > > > > > > $ cat test.st > > > #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo > --headless /Users/sven/tmp/pharo4/Pharo.image st --quit > > > FileStream stdout nextPutAll: 42 factorial asString; cr. > > > > > > $ time ./test.st > > > 1405006117752879898543142606244511569936384000000000 > > > > > > real 0m0.644s > > > user 0m0.516s > > > sys 0m0.067s > > > > > > So about half a second overhead. > > > > > > Sven > > > > > > > > > > > >

July 25, 2014

Re: [Pharo-users] Commandline

by Sven Van Caekenberghe

Yes, for some reason, the shebang (#!) machinery passes ./test2.st as argument to pharo, which it seems can only be resolved if it is in the image directory (as opposed to the current shell directory). I have no time to look at this now, but I vaguely remember that pharo mixed the concept of current working directory and image directory (at least in some places). On 25 Jul 2014, at 21:43, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Sven, > Without putting a test.st file in /Users/daleh/gsDevKitHome/pharo, I get the following (it works if I `cp ./test.st /Users/daleh/gsDevKitHome/pharo`): > > nehalem:junk daleh$ pwd > /Users/daleh/junk > nehalem:junk daleh$ cat test.st > #!/Users/daleh/gsDevKitHome/pharo/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/daleh/gsDevKitHome/pharo/todeClient.image st --quit > FileStream stdout nextPutAll: 42 factorial asString; cr. > nehalem:junk daleh$ ./test.st > FileDoesNotExist: File @ /Users/daleh/gsDevKitHome/pharo/test.st > FileHandle>>streamError > FileHandle>>readStream > FileSystem>>readStreamOn: > FileReference>>readStream > FileReference(AbstractFileReference)>>readStreamDo: > STCommandLineHandler>>installSourceFile: > STCommandLineHandler>>installSourceFiles in Block: [ :reference | self installSourceFile: reference ]...etc... > OrderedCollection>>do: > STCommandLineHandler>>installSourceFiles in Block: [ sourceFiles do: [ :reference | self installSourc...etc... > BlockClosure>>ensure: > STCommandLineHandler>>installSourceFiles > STCommandLineHandler>>activate > STCommandLineHandler class(CommandLineHandler class)>>activateWith: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self handleArgument: (self arguments ifEmpty: [ ...etc... > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > PharoCommandLineHandler class>>activateWith: in Block: [ super activateWith: aCommandLine ] > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > WorldMorph>>doOneCycle > MorphicUIManager>>spawnNewProcess in Block: [ ... > > > > On Fri, Jul 25, 2014 at 12:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 25 Jul 2014, at 21:25, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > > Sven, > > > > I'm using Pharo3.0 and it appears that the .st scripts have to be located in the same directory as the image and changes files ... I see that you are using Pharo4.0 ... > > > > So is it possible to get Pharo3.0 to work on .st files in arbitary directores? > > Are you using the shebang or direct version ? > In any case, I am always using absolute paths. > Does that not work for you ? > > > Dale > > > > > > On Thu, Jul 24, 2014 at 7:42 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: > > > > > One question I have is how fast the load of an image and processing by an image is when compared with bash. > > > > Obviously, it is slower, there is a whole image that needs to be loaded, etc. > > > > $ cat test.st > > #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/sven/tmp/pharo4/Pharo.image st --quit > > FileStream stdout nextPutAll: 42 factorial asString; cr. > > > > $ time ./test.st > > 1405006117752879898543142606244511569936384000000000 > > > > real 0m0.644s > > user 0m0.516s > > sys 0m0.067s > > > > So about half a second overhead. > > > > Sven > > > > >

July 25, 2014

Re: [Pharo-users] Commandline

by Dale Henrichs

Sven, Without putting a test.st file in /Users/daleh/gsDevKitHome/pharo, I get the following (it works if I `cp ./test.st /Users/daleh/gsDevKitHome/pharo`): nehalem:junk daleh$ pwd /Users/daleh/junk nehalem:junk daleh$ cat test.st #!/Users/daleh/gsDevKitHome/pharo/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/daleh/gsDevKitHome/pharo/todeClient.image st --quit FileStream stdout nextPutAll: 42 factorial asString; cr. nehalem:junk daleh$ ./test.st FileDoesNotExist: File @ /Users/daleh/gsDevKitHome/pharo/test.st FileHandle>>streamError FileHandle>>readStream FileSystem>>readStreamOn: FileReference>>readStream FileReference(AbstractFileReference)>>readStreamDo: STCommandLineHandler>>installSourceFile: STCommandLineHandler>>installSourceFiles in Block: [ :reference | self installSourceFile: reference ]...etc... OrderedCollection>>do: STCommandLineHandler>>installSourceFiles in Block: [ sourceFiles do: [ :reference | self installSourc...etc... BlockClosure>>ensure: STCommandLineHandler>>installSourceFiles STCommandLineHandler>>activate STCommandLineHandler class(CommandLineHandler class)>>activateWith: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self handleArgument: (self arguments ifEmpty: [ ...etc... BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: PharoCommandLineHandler class>>activateWith: in Block: [ super activateWith: aCommandLine ] WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle MorphicUIManager>>spawnNewProcess in Block: [ ... On Fri, Jul 25, 2014 at 12:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 25 Jul 2014, at 21:25, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> > wrote: > > > Sven, > > > > I'm using Pharo3.0 and it appears that the .st scripts have to be > located in the same directory as the image and changes files ... I see > that you are using Pharo4.0 ... > > > > So is it possible to get Pharo3.0 to work on .st files in arbitary > directores? > > Are you using the shebang or direct version ? > In any case, I am always using absolute paths. > Does that not work for you ? > > > Dale > > > > > > On Thu, Jul 24, 2014 at 7:42 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: > > > > > One question I have is how fast the load of an image and processing by > an image is when compared with bash. > > > > Obviously, it is slower, there is a whole image that needs to be loaded, > etc. > > > > $ cat test.st > > #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo > --headless /Users/sven/tmp/pharo4/Pharo.image st --quit > > FileStream stdout nextPutAll: 42 factorial asString; cr. > > > > $ time ./test.st > > 1405006117752879898543142606244511569936384000000000 > > > > real 0m0.644s > > user 0m0.516s > > sys 0m0.067s > > > > So about half a second overhead. > > > > Sven > > > > >

July 25, 2014

Re: [Pharo-users] Commandline

by Sven Van Caekenberghe

On 25 Jul 2014, at 21:25, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Sven, > > I'm using Pharo3.0 and it appears that the .st scripts have to be located in the same directory as the image and changes files ... I see that you are using Pharo4.0 ... > > So is it possible to get Pharo3.0 to work on .st files in arbitary directores? Are you using the shebang or direct version ? In any case, I am always using absolute paths. Does that not work for you ? > Dale > > > On Thu, Jul 24, 2014 at 7:42 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: > > > One question I have is how fast the load of an image and processing by an image is when compared with bash. > > Obviously, it is slower, there is a whole image that needs to be loaded, etc. > > $ cat test.st > #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo --headless /Users/sven/tmp/pharo4/Pharo.image st --quit > FileStream stdout nextPutAll: 42 factorial asString; cr. > > $ time ./test.st > 1405006117752879898543142606244511569936384000000000 > > real 0m0.644s > user 0m0.516s > sys 0m0.067s > > So about half a second overhead. > > Sven >

July 25, 2014

Re: [Pharo-users] Commandline

by Dale Henrichs

Sven, I'm using Pharo3.0 and it appears that the .st scripts have to be located in the same directory as the image and changes files ... I see that you are using Pharo4.0 ... So is it possible to get Pharo3.0 to work on .st files in arbitary directores? Dale On Thu, Jul 24, 2014 at 7:42 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 24 Jul 2014, at 16:34, phil(a)highoctane.be wrote: > > > One question I have is how fast the load of an image and processing by > an image is when compared with bash. > > Obviously, it is slower, there is a whole image that needs to be loaded, > etc. > > $ cat test.st > #!/Users/sven/tmp/pharo4/pharo-vm/Pharo.app/Contents/MacOS/Pharo > --headless /Users/sven/tmp/pharo4/Pharo.image st --quit > FileStream stdout nextPutAll: 42 factorial asString; cr. > > $ time ./test.st > 1405006117752879898543142606244511569936384000000000 > > real 0m0.644s > user 0m0.516s > sys 0m0.067s > > So about half a second overhead. > > Sven >

July 25, 2014

Re: [Pharo-users] [Tip] Image init scripts when working with PharoLauncher

by Sean P. DeNigris

Torsten Bergmann wrote > Nonetheless I would like to share the script that I personally use Cool, thanks! My script was getting too complicated, so I made it into a class with a MetaC config, and the script is now just a Gofer load. This has the additional benefit that the start up scripts for the Pharo loader never change (they're just Gofer loads) and so avoid the caching problems that can otherwise arise. Torsten Bergmann wrote > "Set password for Squeaksource" > (MCRepositoryGroup default repositories > select: [:each | (each isKindOf: MCHttpRepository) > and: [((each locationWithTrailingSlash includesSubstring: > 'www.squeaksource.com') > or: [each locationWithTrailingSlash includesSubstring: > 'http://ss3.gemstone.com/ss/'])] > ]) > do: [:each | each user: 'squeaksourceuser'; password: > 'secretsqueaksourcepassword']. > ... I do something like this too. The shortcoming is that newly created repos are not authenticated. This should be in core built into the repo objects. I guess that's what the KeyChain stuff is about? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tip-Image-init-scripts-when-working-with-PharoLaunche… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 25, 2014

Re: [Pharo-users] export roassal views

by Alexandre Bergel

It would be fantastic if you attend ESUGâ¦ will you? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jul 25, 2014, at 9:14 AM, rosariosm <rosariosantamarina1(a)gmail.com> wrote: > Hi Alexandre, > > Yes, that solution seems to work fine. Right now i'm working at other things > but i could do the exporter later. It will be useful for everyone. > Arturo and I don't think that our work is ready for Esug, but we could > present it next year, who knows. Thanks! It's a lot of hard work. > > Cheers, > Rosario > > > > -- > View this message in context: http://forum.world.st/export-roassal-views-tp4767944p4770079.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

July 25, 2014

Re: [Pharo-users] export roassal views

by rosariosm

Hi Alexandre, Yes, that solution seems to work fine. Right now i'm working at other things but i could do the exporter later. It will be useful for everyone. Arturo and I don't think that our work is ready for Esug, but we could present it next year, who knows. Thanks! It's a lot of hard work. Cheers, Rosario -- View this message in context: http://forum.world.st/export-roassal-views-tp4767944p4770079.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 25, 2014

Re: [Pharo-users] Reference documentation on Trait

by stepharo

there is no tutorial just the academic paper. I started a documentation but got distracted. You can check my presentation about traits at ESUG-Brest On 25/7/14 09:47, Hilaire wrote: > Hi, > > Do we have such document(s)? > > Thanks > > Hilaire

July 25, 2014