January 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] I am David Allouche, let me introduce myself.

by Hilaire

Le 13/01/2016 18:29, David Allouche a Ã©crit : > > The fact Smalltalk the language cannot be taken in isolation from > Smalltalk the environment became clear rather early on: reading the > UPBE and other materials shows that the language itself does almost > nothing: it cannot even define classes or packages. It is all part of > the environment. > It is not the case. For example, to define a new class, the unique way to do this is from Smalltalk itself, with the message #subclass:instanceVariableNames:classVariableNames:category: sent to the parent class. The GUI, just makes it more transparent, but it is pure Smalltalk code. Well it can't be different as the GUI is written in Smalltalk :) Hilaire -- Dr. Geo http://drgeo.eu

Jan. 14, 2016

Re: [Pharo-users] Slow object printOn: with EURO symbol

by Hilaire

I don't think like I want to hack on the system to get normal time response. I will use #render: when it will gets too slow, even if it breaks the beauty of the code. This is the kind of problem where newbie may think Pharo is slow. Hilaire Le 05/01/2016 18:59, Ben Coman a Ã©crit : > On Tue, Jan 5, 2016 at 10:20 PM, Hilaire <hilaire(a)drgeo.eu> wrote: >> Le 05/01/2016 14:38, Sven Van Caekenberghe a Ã©crit : >>> The problem can does also be restated: it is really necessary for a tool to convert 1000s of items to strings, even if only 10s are shown at the same time on a screen ? >>> >>> I believe that fast table tries to do better here. >> But I need to show 1000s of them once, all in the same view, at the same >> time. > Is it that the same 1000 strings are being rendered multiple times a > second? I had a similar problem with Roassal 1 with a unicode char > massively slowing down to UI. I managed to achieve fairly normal > response time by cached the Freetype calculated width of the string. > I found the right place to do this by both profiling the whole system, > and just the rendering by wrapping MessaeTally around the code of > fullDrawOn: . > > Then I cache both the string and its calculated length from the > rendering code, then if the cached string is the same as current I > just returned the cached length. > > Sorry I can't be clearer. > cheers -ben > > -- Dr. Geo http://drgeo.eu

Jan. 14, 2016

Re: [Pharo-users] Launcher 0.2.9 opens Spur images

by Stephan Eggermont

On 14-01-16 19:17, Esteban A. Maringolo wrote: > The thing is the vm and the image are located in different directories > (at least in Linux), following quite properly the recommended > locations for different kind of files. vms are data, just like images :) Stephan

Jan. 14, 2016

Re: [Pharo-users] [ANN] OSSubprocess first milestone

by Mariano Martinez Peck

On Thu, Jan 14, 2016 at 3:44 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com > wrote: > Le 14/01/2016 19:33, Mariano Martinez Peck a Ã©crit : > > Dear all, > > > > I am happy to tell you I have a first prototype of the tool for > > executing OS processes: > > > > https://github.com/marianopeck/OSSubprocess > > > > As I said many times, the main idea was to be as much as possible > > FFI-based, only for executing OS commands and, from my point of view, a > > better end-user API. Also, as for the first step, I had to focus on > > Linux/OSX. > > > > I would like to thank Pharo Consortium for the sponsor of this > > development effort. Here is the first milestone! > > > > There are many things on my to-do but I think the code is ready for some > > usage, testing, code review and feedback! > > > > All classes and all methods have comments and I have quite some unit > > tests. All tests are green in my OSX and a CentOS box. > > > > *Important: you CANNOT have OSProcess installed in the same image as > > OSSubprocess. This is because I am reusing his SIGCHLD handler and for > > the time being both cannot coexist. * > > > > Keep in mind that the tool may be unstable and that MAY mean a VM crash. > > So use with care, mostly the first time. If all tests passes, then there > > are much less chances of something going bad. > > > > Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY > > influenced by a subset of the OSProcess project. There are parts which I > > even simply copied and adapted them (OSSPipe, OSSAttachableStream, > > OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the > > idea of ThisOSProcess representing the VM process, the child watcher, > > and many others). In addition, I AM STILL USING (maybe as a first step?) > > some of the OSProcess PLUGIN (not OSProcess image side), such as the > > SIGCHLD handler or the creation of pipes. > > > > In github url you have all the documentation of the project, included > > how to install it and use it. > > > > *Finally, if you test it in a OS different than OSX and CentOS please > > share with me the results (about the tests).* Tomorrow the > > ConfigurationOf should also appear in the Catalog of Pharo 5.0. > > > > Any feedback is appreciated. > > > > Best, > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > Hi, > > Thank you for your work! > > In Windows seven I got an error on loading. > > Yes, sorry, no windows for the moment. Should work in OSX, Linux and other's Unix* as far as I can think of. At some point we may unify an API with ProcessWrapper but not right now (at least from my side). > Executed code in Pharo 5: > > Metacello new > configuration: 'OSSubprocess'; > repository: 'github://marianopeck/OSSubprocess:master/repository'; > version: #stable; > load. > > Stack: > > ExternalLibraryFunction(Object)>>error: > ExternalLibraryFunction(Object)>>externalCallFailed > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > OSSUnixSystemAccessor>>primitiveGetpid > FFICalloutAPI>>function:module: > OSSUnixSystemAccessor(Object)>>ffiCall: > OSSUnixSystemAccessor>>primitiveGetpid > OSSUnixSystemAccessor>>getPid > OSSVMProcess>>initialize > OSSVMProcess class>>initializeVMProcessInstance > OSSVMProcess class>>initialize > MCMethodDefinition>>postloadOver: > [ :each | each postloadOver: (self obsoletionFor: each) ] in > MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each > postloadOver: (self obsoletionFor: ...etc... > [ :each | > | newLabel | > "Special handling for first and last element" > (count = 0 > or: > [ count + 1 = size > or: [ (Time millisecondsSince: lastUpdate) >= > msecs ] ]) > ifTrue: > [ bar current: count. > oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ > oldLabel ]) > ifFalse: [ bar label: newLabel. > oldLabel := newLabel ]. > lastUpdate := Time millisecondClockValue ]. > aBlock value: each. > count := count + 1 ] in [ :bar | > labelBlock := aStringOrBlock isString > ifTrue: [ bar label: aStringOrBlock. > [ :dummyItem | aStringOrBlock ] ] > ifFalse: [ aStringOrBlock ]. > self > do: > [ :each | > | newLabel | > "Special handling for first and last element" > (count = 0 > or: > [ count + 1 = size > or: [ (Time millisecondsSince: > lastUpdate) >= msecs ] ]) > ifTrue: > [ bar current: count. > oldLabel > = (newLabel := (labelBlock cull: > each) ifNil: [ oldLabel ]) > ifFalse: [ bar label: newLabel. > oldLabel := newLabel ]. > lastUpdate := Time millisecondClockValue ]. > aBlock value: each. > count := count + 1 ] ] in > OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ > :each | ... > OrderedCollection>>do: > [ :bar | > labelBlock := aStringOrBlock isString > ifTrue: [ bar label: aStringOrBlock. > [ :dummyItem | aStringOrBlock ] ] > ifFalse: [ aStringOrBlock ]. > self > do: > [ :each | > | newLabel | > "Special handling for first and last element" > (count = 0 > or: > [ count + 1 = size > or: [ (Time millisecondsSince: > lastUpdate) >= msecs ] ]) > ifTrue: > [ bar current: count. > oldLabel > = (newLabel := (labelBlock cull: > each) ifNil: [ oldLabel ]) > ifFalse: [ bar label: newLabel. > oldLabel := newLabel ]. > lastUpdate := Time millisecondClockValue ]. > aBlock value: each. > count := count + 1 ] ] in > OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ > :bar | ... > BlockClosure>>cull: > [ ^ block cull: self ] in [ self prepareForRunning. > CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in > Block: [ ^ block cull: self ] > [ p psValueAt: index put: anObject. > aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ > p psValueAt: index put: anObject.... > BlockClosure>>ensure: > CurrentJob(DynamicVariable)>>value:during: > CurrentJob class(DynamicVariable class)>>value:during: > [ self prepareForRunning. > CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in > Block: [ self prepareForRunning.... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > OrderedCollection(Collection)>>do:displayingProgress:every: > OrderedCollection(Collection)>>do:displayingProgress: > MCPackageLoader>>basicLoadDefinitions > > > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > > -- Mariano http://marianopeck.wordpress.com

Jan. 14, 2016

Re: [Pharo-users] [ANN] OSSubprocess first milestone

by Ferlicot D. Cyril

Le 14/01/2016 19:33, Mariano Martinez Peck a Ã©crit : > Dear all, > > I am happy to tell you I have a first prototype of the tool for > executing OS processes: > > https://github.com/marianopeck/OSSubprocess > > As I said many times, the main idea was to be as much as possible > FFI-based, only for executing OS commands and, from my point of view, a > better end-user API. Also, as for the first step, I had to focus on > Linux/OSX. > > I would like to thank Pharo Consortium for the sponsor of this > development effort. Here is the first milestone! > > There are many things on my to-do but I think the code is ready for some > usage, testing, code review and feedback! > > All classes and all methods have comments and I have quite some unit > tests. All tests are green in my OSX and a CentOS box. > > *Important: you CANNOT have OSProcess installed in the same image as > OSSubprocess. This is because I am reusing his SIGCHLD handler and for > the time being both cannot coexist. * > > Keep in mind that the tool may be unstable and that MAY mean a VM crash. > So use with care, mostly the first time. If all tests passes, then there > are much less chances of something going bad. > > Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY > influenced by a subset of the OSProcess project. There are parts which I > even simply copied and adapted them (OSSPipe, OSSAttachableStream, > OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the > idea of ThisOSProcess representing the VM process, the child watcher, > and many others). In addition, I AM STILL USING (maybe as a first step?) > some of the OSProcess PLUGIN (not OSProcess image side), such as the > SIGCHLD handler or the creation of pipes. > > In github url you have all the documentation of the project, included > how to install it and use it. > > *Finally, if you test it in a OS different than OSX and CentOS please > share with me the results (about the tests).* Tomorrow the > ConfigurationOf should also appear in the Catalog of Pharo 5.0. > > Any feedback is appreciated. > > Best, > > -- > Mariano > http://marianopeck.wordpress.com Hi, Thank you for your work! In Windows seven I got an error on loading. Executed code in Pharo 5: Metacello new configuration: 'OSSubprocess'; repository: 'github://marianopeck/OSSubprocess:master/repository'; version: #stable; load. Stack: ExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: OSSUnixSystemAccessor>>primitiveGetpid FFICalloutAPI>>function:module: OSSUnixSystemAccessor(Object)>>ffiCall: OSSUnixSystemAccessor>>primitiveGetpid OSSUnixSystemAccessor>>getPid OSSVMProcess>>initialize OSSVMProcess class>>initializeVMProcessInstance OSSVMProcess class>>initialize MCMethodDefinition>>postloadOver: [ :each | each postloadOver: (self obsoletionFor: each) ] in MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each postloadOver: (self obsoletionFor: ...etc... [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] in [ :bar | labelBlock := aStringOrBlock isString ifTrue: [ bar label: aStringOrBlock. [ :dummyItem | aStringOrBlock ] ] ifFalse: [ aStringOrBlock ]. self do: [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :each | ... OrderedCollection>>do: [ :bar | labelBlock := aStringOrBlock isString ifTrue: [ bar label: aStringOrBlock. [ :dummyItem | aStringOrBlock ] ] ifFalse: [ aStringOrBlock ]. self do: [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :bar | ... BlockClosure>>cull: [ ^ block cull: self ] in [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] [ p psValueAt: index put: anObject. aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ p psValueAt: index put: anObject.... BlockClosure>>ensure: CurrentJob(DynamicVariable)>>value:during: CurrentJob class(DynamicVariable class)>>value:during: [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: OrderedCollection(Collection)>>do:displayingProgress:every: OrderedCollection(Collection)>>do:displayingProgress: MCPackageLoader>>basicLoadDefinitions -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 14, 2016

[ANN] OSSubprocess first milestone

by Mariano Martinez Peck

Dear all, I am happy to tell you I have a first prototype of the tool for executing OS processes: https://github.com/marianopeck/OSSubprocess As I said many times, the main idea was to be as much as possible FFI-based, only for executing OS commands and, from my point of view, a better end-user API. Also, as for the first step, I had to focus on Linux/OSX. I would like to thank Pharo Consortium for the sponsor of this development effort. Here is the first milestone! There are many things on my to-do but I think the code is ready for some usage, testing, code review and feedback! All classes and all methods have comments and I have quite some unit tests. All tests are green in my OSX and a CentOS box. *Important: you CANNOT have OSProcess installed in the same image as OSSubprocess. This is because I am reusing his SIGCHLD handler and for the time being both cannot coexist. * Keep in mind that the tool may be unstable and that MAY mean a VM crash. So use with care, mostly the first time. If all tests passes, then there are much less chances of something going bad. Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY influenced by a subset of the OSProcess project. There are parts which I even simply copied and adapted them (OSSPipe, OSSAttachableStream, OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the idea of ThisOSProcess representing the VM process, the child watcher, and many others). In addition, I AM STILL USING (maybe as a first step?) some of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD handler or the creation of pipes. In github url you have all the documentation of the project, included how to install it and use it. *Finally, if you test it in a OS different than OSX and CentOS please share with me the results (about the tests).* Tomorrow the ConfigurationOf should also appear in the Catalog of Pharo 5.0. Any feedback is appreciated. Best, -- Mariano http://marianopeck.wordpress.com

Jan. 14, 2016

Re: [Pharo-users] Launcher 0.2.9 opens Spur images

by Esteban A. Maringolo

2016-01-14 14:58 GMT-03:00 Stephan Eggermont <stephan(a)stack.nl>: > On 14-01-16 18:49, Blondeau Vincent wrote: >> >> I don't think so. One needs to add the spur VM in the package and set a >> default relative path in the Pharo launcher image. >> Should be easy. > > > I hope so. A version with both vms would be much easier for new users. > > Considering that we want to be able to also use it with multiple vm > versions, I'd suggest adding a vms directory next to the images one, > and putting it there. The thing is the vm and the image are located in different directories (at least in Linux), following quite properly the recommended locations for different kind of files. Maybe we can have a VM directory and inside it put all the VMs (with one as default linked from /usr/bin/pharo). We could even get the launcher to download other VMs too. Regards!

Jan. 14, 2016

Re: [Pharo-users] Launcher 0.2.9 opens Spur images

by Stephan Eggermont

On 14-01-16 18:49, Blondeau Vincent wrote: > I don't think so. One needs to add the spur VM in the package and set a default relative path in the Pharo launcher image. > Should be easy. I hope so. A version with both vms would be much easier for new users. Considering that we want to be able to also use it with multiple vm versions, I'd suggest adding a vms directory next to the images one, and putting it there. Stephan

Jan. 14, 2016

Re: [Pharo-users] Launcher 0.2.9 opens Spur images

by Blondeau Vincent

I don't think so. One needs to add the spur VM in the package and set a default relative path in the Pharo launcher image. Should be easy. Vincent > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > Yuriy Tymchuk > EnvoyÃ© : jeudi 14 janvier 2016 18:44 > Ã : Any question about pharo is welcome > Objet : Re: [Pharo-users] Launcher 0.2.9 opens Spur images > > Amazing. > > Is there any technical difficulty of shipping Launcher bundled with 2 vm? > Because I can try to do that. > > Uko > > > > On 14 Jan 2016, at 18:31, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > > Hi, > > > > It is *automatic* :) > > > > You just setup the location of both pre and spur images in the launcher. It > will find in the image header the one it should use. > > > > Vincent > > > >> -----Message d'origine----- > >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la > >> part de Yuriy Tymchuk EnvoyÃ© : jeudi 14 janvier 2016 18:25 Ã : Any > >> question about pharo is welcome Objet : Re: [Pharo-users] Launcher > >> 0.2.9 opens Spur images > >> > >> But how does it work? Doest the launcher detect which vm should be > >> used for the image that you are launching, or you have to switch > something? > >> > >> Uko > >> > >>> On 14 Jan 2016, at 18:18, Damien Cassou <damien.cassou(a)inria.fr> > wrote: > >>> > >>> Hi list, > >>> > >>> thanks to the awesome work of Vincent Blondeau, Stephan Eggermont > >>> and Cyril Ferlicot, Pharo Launcher 0.2.9 can be configured to open > >>> both spur and pre-spur Pharo images. > >>> > >>> You can download this version from > >>> http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher. > >>> > >>> You can safely replace your existing Launcher installation with the > >>> new one. Your images won't be affected and you will still be able to > >>> launch them. > >>> > >>> The VM coming with these builds is a pre-spur VM because Launcher is > >>> based on Pharo 4. If you want to launch Pharo 5 spur images, you > >>> need to separately download a Pharo 5 Spur VM from > >>> http://get.pharo.org/vm50 and configure the location of this VM in > >>> the Launcher settings (icon at the bottom left of the Launcher window). > >>> > >>> What I like about this release is that I didn't do anything but > >>> changing the version number in > >> https://ci.inria.fr/pharo/view/all/job/Launcher :-). > >>> > >>> -- > >>> Damien Cassou > >>> http://damiencassou.seasidehosting.st > >>> > >>> "Success is the ability to go from one failure to another without > >>> losing enthusiasm." --Winston Churchill > >>> > >> > > > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout virus, > l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne > saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 14, 2016

Re: [Pharo-users] Launcher 0.2.9 opens Spur images

by Yuriy Tymchuk

Amazing. Is there any technical difficulty of shipping Launcher bundled with 2 vm? Because I can try to do that. Uko > On 14 Jan 2016, at 18:31, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > It is *automatic* :) > > You just setup the location of both pre and spur images in the launcher. It will find in the image header the one it should use. > > Vincent > >> -----Message d'origine----- >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de >> Yuriy Tymchuk >> EnvoyÃ© : jeudi 14 janvier 2016 18:25 >> Ã : Any question about pharo is welcome >> Objet : Re: [Pharo-users] Launcher 0.2.9 opens Spur images >> >> But how does it work? Doest the launcher detect which vm should be used >> for the image that you are launching, or you have to switch something? >> >> Uko >> >>> On 14 Jan 2016, at 18:18, Damien Cassou <damien.cassou(a)inria.fr> wrote: >>> >>> Hi list, >>> >>> thanks to the awesome work of Vincent Blondeau, Stephan Eggermont and >>> Cyril Ferlicot, Pharo Launcher 0.2.9 can be configured to open both >>> spur and pre-spur Pharo images. >>> >>> You can download this version from >>> http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher. >>> >>> You can safely replace your existing Launcher installation with the >>> new one. Your images won't be affected and you will still be able to >>> launch them. >>> >>> The VM coming with these builds is a pre-spur VM because Launcher is >>> based on Pharo 4. If you want to launch Pharo 5 spur images, you need >>> to separately download a Pharo 5 Spur VM from >>> http://get.pharo.org/vm50 and configure the location of this VM in the >>> Launcher settings (icon at the bottom left of the Launcher window). >>> >>> What I like about this release is that I didn't do anything but >>> changing the version number in >> https://ci.inria.fr/pharo/view/all/job/Launcher :-). >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." --Winston Churchill >>> >> > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. >

Jan. 14, 2016