December 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Sven Van Caekenberghe

Make that âPharo.image' asFileReference binaryReadStreamDo: [ :stream | (stream next: 4) reversed asInteger ]. > On 17 Dec 2015, at 14:28, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > âPharo.image' asFileReference > binaryReadStreamDo: [ :stream | (stream next: 4) reserved asInteger ]. > >> On 17 Dec 2015, at 14:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> âPharo.image' asFileReference >> readStreamDo: [ :stream | (stream binary; next: 4) longAt: 1 bigEndian: false ]. >> >>> On 17 Dec 2015, at 13:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>> >>> Iâd prefer the new API that does not use MultiByteFileStream and friends :) >>> >>> version := nil. >>> (File named: 'Pharo.image') readStreamDo: [ :stream | >>> version := (stream next: 4) longAt: 1 bigEndian: false ]. >>> version >>> >>>> On 17 dic 2015, at 1:20 p.m., Stephan Eggermont <stephan(a)stack.nl> wrote: >>>> >>>> On 17-12-15 12:53, Guillermo Polito wrote: >>>>> Hmm, usually an image file has a header that describes some meta data >>>>> about the image: version, some VM options, size of the imageâ¦ >>>> >>>> byteStream := FileStream fileNamed: '/home/stephan/.local/share/Pharo/images/50305/50305.image'. >>>> byteStream binary. >>>> version := byteStream nextLittleEndianNumber: 4. >>>> byteStream close. >>>> version >>>> >>>> 6505 >>>> >>>> That supports deciding which vm to use >>>> >>>> Stephan >>>> >>>> >>>> >>> >>> >> >> >

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Stephan Eggermont

On 17-12-15 13:26, Guillermo Polito wrote: > Iâd prefer the new API that does not use MultiByteFileStream and friends :) > > version := nil. > (File named: 'Pharo.image') readStreamDo: [ :stream | > version := (stream next: 4) longAt: 1 bigEndian: false ]. > version File isn't in the PharoLauncher image Stephan

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Sven Van Caekenberghe

âPharo.image' asFileReference binaryReadStreamDo: [ :stream | (stream next: 4) reserved asInteger ]. > On 17 Dec 2015, at 14:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > âPharo.image' asFileReference > readStreamDo: [ :stream | (stream binary; next: 4) longAt: 1 bigEndian: false ]. > >> On 17 Dec 2015, at 13:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Iâd prefer the new API that does not use MultiByteFileStream and friends :) >> >> version := nil. >> (File named: 'Pharo.image') readStreamDo: [ :stream | >> version := (stream next: 4) longAt: 1 bigEndian: false ]. >> version >> >>> On 17 dic 2015, at 1:20 p.m., Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> On 17-12-15 12:53, Guillermo Polito wrote: >>>> Hmm, usually an image file has a header that describes some meta data >>>> about the image: version, some VM options, size of the imageâ¦ >>> >>> byteStream := FileStream fileNamed: '/home/stephan/.local/share/Pharo/images/50305/50305.image'. >>> byteStream binary. >>> version := byteStream nextLittleEndianNumber: 4. >>> byteStream close. >>> version >>> >>> 6505 >>> >>> That supports deciding which vm to use >>> >>> Stephan >>> >>> >>> >> >> > >

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Stephan Eggermont

I've commited a PharoLauncher version that adds a setting for a spur vm path. If you download a spur vm and point set this setting, the launcher will start the image with the right vm Stephan

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Esteban Lorenzano

âPharo.image' asFileReference readStreamDo: [ :stream | (stream binary; next: 4) longAt: 1 bigEndian: false ]. > On 17 Dec 2015, at 13:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Iâd prefer the new API that does not use MultiByteFileStream and friends :) > > version := nil. > (File named: 'Pharo.image') readStreamDo: [ :stream | > version := (stream next: 4) longAt: 1 bigEndian: false ]. > version > >> On 17 dic 2015, at 1:20 p.m., Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 17-12-15 12:53, Guillermo Polito wrote: >>> Hmm, usually an image file has a header that describes some meta data >>> about the image: version, some VM options, size of the imageâ¦ >> >> byteStream := FileStream fileNamed: '/home/stephan/.local/share/Pharo/images/50305/50305.image'. >> byteStream binary. >> version := byteStream nextLittleEndianNumber: 4. >> byteStream close. >> version >> >> 6505 >> >> That supports deciding which vm to use >> >> Stephan >> >> >> > >

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Guillermo Polito

Iâd prefer the new API that does not use MultiByteFileStream and friends :) version := nil. (File named: 'Pharo.image') readStreamDo: [ :stream | version := (stream next: 4) longAt: 1 bigEndian: false ]. version > On 17 dic 2015, at 1:20 p.m., Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 17-12-15 12:53, Guillermo Polito wrote: >> Hmm, usually an image file has a header that describes some meta data >> about the image: version, some VM options, size of the imageâ¦ > > byteStream := FileStream fileNamed: '/home/stephan/.local/share/Pharo/images/50305/50305.image'. > byteStream binary. > version := byteStream nextLittleEndianNumber: 4. > byteStream close. > version > > 6505 > > That supports deciding which vm to use > > Stephan > > >

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Stephan Eggermont

On 17-12-15 12:53, Guillermo Polito wrote: > Hmm, usually an image file has a header that describes some meta data > about the image: version, some VM options, size of the imageâ¦ byteStream := FileStream fileNamed: '/home/stephan/.local/share/Pharo/images/50305/50305.image'. byteStream binary. version := byteStream nextLittleEndianNumber: 4. byteStream close. version 6505 That supports deciding which vm to use Stephan

Dec. 17, 2015

Re: [Pharo-dev] MacroRecorder updates (+ another demo)

by Gustavo Santos

Once you created the superclass, yes. Otherwise, there will be an error when you execute the transformation, because the superclass you indicated does not exist. On Thu, Dec 17, 2015 at 12:59 PM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > Gustavo Santos <gugajansen(a)gmail.com> writes: > > > Hello guys, > > > > thanks for the support so far. I've been working on your suggestions. > > > > Some of them concerned that the example in the first demo video was too > > "magic". :-P > > So I made another video showing how the developer can manually configure > > the tool. > > Take a look: https://youtu.be/3xc3j3PjIYQ > > great! But you stopped the video just before showing what happens for > indirect subclasses of JenkinsObject. Does macro recorder work for the > sub-sub-classes as well? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > -- Gustavo Santos http://gustavojss.github.io/

Dec. 17, 2015

Re: [Pharo-dev] Adapting the launcher to Spur VM

by Damien Cassou

Guillermo Polito <guillermopolito(a)gmail.com> writes: > Hmm, usually an image file has a header that describes some meta data about the image: version, some VM options, size of the imageâ¦ > > If you load: > > Gofer it > squeaksource3: 'ImageWriter'; > package: âImageWriter-Core'; > load. > > > Youâll get HzCogImageFormat that describes the header. Check the method writeImageHeaderOn: byteStream forWriter: aWriter thanks Guillermo. I won't do it myself because I'm very busy and don't have much time for Pharo programming, but I hope someone using the launcher with Pharo 5 will have a look. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Dec. 17, 2015

Re: [Pharo-dev] MacroRecorder updates (+ another demo)

by Damien Cassou

Gustavo Santos <gugajansen(a)gmail.com> writes: > Hello guys, > > thanks for the support so far. I've been working on your suggestions. > > Some of them concerned that the example in the first demo video was too > "magic". :-P > So I made another video showing how the developer can manually configure > the tool. > Take a look: https://youtu.be/3xc3j3PjIYQ great! But you stopped the video just before showing what happens for indirect subclasses of JenkinsObject. Does macro recorder work for the sub-sub-classes as well? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Dec. 17, 2015