February 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] OT: compressing log files

by Nicolas Cellier

The problem is that (#(1 2 1 2 1 2) as: RunArray) does not save any space... Nicolas 2010/2/10 Matthias Berth <matthias.berth(a)googlemail.com>: > Hi Eliot, > > maybe RunArray helps here? > > From the class comment of RunArray (in Pharo): > My instances provide space-efficient storage of data which tends to be > constant over long runs of the possible indices. Essentially repeated > values are stored singly and then associated with a "run" length that > denotes the number of consecutive occurrences of the value. > > Cheers > > Matthias > > 2010/2/9 Eliot Miranda <eliot.miranda(a)gmail.com>: >> Hi All, >> Â Â Â I've just needed to make sense of a very long log file generated by >> strace. Â The log file is full of entries like: >> --- SIGALRM (Alarm clock) @ 0 (0) --- >> gettimeofday({1265744804, 491238}, NULL) = 0 >> sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> and my workspace script reduces these to e.g. >> --- SIGALRM (Alarm clock) @ 0 (0) --- >> gettimeofday({1265744797, 316183}, NULL) = 0 >> sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) >> NEXT 2 LINES REPEAT 715 TIMES >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> --- SIGALRM (Alarm clock) @ 0 (0) --- >> gettimeofday({1265744797, 317189}, NULL) = 0 >> sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) >> >> My question is has anyone looked at this issue in any depth and perhaps come >> up with something not as crude as the below and possibly even recursive. >> Â i.e. the above would ideally be reduced to e.g. >> NEXT 7 LINES REPEAT 123456 TIMES >> --- SIGALRM (Alarm clock) @ 0 (0) --- >> gettimeofday({1265744797, 316183}, NULL) = 0 >> sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) >> NEXT 2 LINES REPEAT BETWEEN 500 AND 800 TIMES >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 >> ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 >> --- SIGALRM (Alarm clock) @ 0 (0) --- >> gettimeofday({1265744797, 317189}, NULL) = 0 >> sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) >> >> >> Here's my quick hack that I ran in vw7.7nc: >> | f o lines maxrun repeats range | >> f := '../Cog/squeak.strace.log' asFilename readStream. >> o := 'compressed.log' asFilename writeStream. >> lines := OrderedCollection new. >> maxrun := 50. >> repeats := 0. >> range := nil. >> [[f atEnd] whileFalse: >> [lines size > maxrun ifTrue: >> [repeats > 0 >> ifTrue: >> [1 to: range first - 1 do: >> [:i| o nextPutAll: (lines at: i); cr]. >> o nextPutAll: 'NEXT '; print: range size; nextPutAll: ' LINES REPEAT '; >> print: repeats + 1; nextPutAll: ' TIMES'; cr. >> range do: >> [:i| o nextPutAll: (lines at: i); cr]. >> lines removeFirst: range last. >> repeats := 0] >> ifFalse: >> [o nextPutAll: lines removeFirst; cr; flush]. >> range := nil]. >> lines addLast: (f upTo: Character cr). >> [:exit| >> 1 to: lines size do: >> [:i| | line repeat | >> line := lines at: i. >> repeat := lines nextIndexOf: line from: i + 1 to: lines size. >> (repeat ~~ nil >> and: [lines size >= (repeat - i * 2 + i) >> and: [(i to: repeat - 1) allSatisfy: [:j| (lines at: j) = (lines at: j - i + >> repeat)]]]) ifTrue: >> [repeats := repeats + 1. >> range isNil >> ifTrue: [range := i to: repeat - 1] >> ifFalse: >> [range = (i to: repeat - 1) ifTrue: >> [range do: [:ignore| lines removeAtIndex: repeat]. >> exit value]]]]] valueWithExit]] >> ensure: [f close. o close]. >> repeats >> Forgive the cross post. Â I expect deep expertise in each newsgroup posted >> to. >> best >> Eliot >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 10, 2010

Re: [Pharo-project] [squeak-dev] File out as Ruby - Possible ?

by CÃ©drick BÃ©ler

Cool... thanks for the info. I guess this is time I go deeper in AST and friends... I'll see how it goes and I probably come back :) 2010/2/10 Lukas Renggli <renggli(a)gmail.com>: > Have a look at the RB AST. You can traverse the AST similar to the > pretty-printer that is included (RBFormatter and > RBConfigurableFormatter) and instead emit Ruby. I've done something > similar for Javascript, and others have done it for other languages. > > Lukas > > On 10 February 2010 16:51, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> Hi, >> >> Do you know if it's possible to export smalltalk code in ruby ? >> I have to port a small app I did and so, it could help me :) >> >> I don't think there's an existing tool, but maybe some directions... >> Actually, I'd prefer writing a simple tool to do that rather than >> doing all by hand. >> >> I don't expect it to work out of the box, but just save me some time. >> >> TIA >> >> -- >> CÃ©drick >> >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- CÃ©drick

Feb. 10, 2010

Re: [Pharo-project] OT: compressing log files

by Matthias Berth

Hi Eliot, maybe RunArray helps here? >From the class comment of RunArray (in Pharo): My instances provide space-efficient storage of data which tends to be constant over long runs of the possible indices. Essentially repeated values are stored singly and then associated with a "run" length that denotes the number of consecutive occurrences of the value. Cheers Matthias 2010/2/9 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi All, > Â Â Â I've just needed to make sense of a very long log file generated by > strace. Â The log file is full of entries like: > --- SIGALRM (Alarm clock) @ 0 (0) --- > gettimeofday({1265744804, 491238}, NULL) = 0 > sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > and my workspace script reduces these to e.g. > --- SIGALRM (Alarm clock) @ 0 (0) --- > gettimeofday({1265744797, 316183}, NULL) = 0 > sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) > NEXT 2 LINES REPEAT 715 TIMES > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > --- SIGALRM (Alarm clock) @ 0 (0) --- > gettimeofday({1265744797, 317189}, NULL) = 0 > sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) > > My question is has anyone looked at this issue in any depth and perhaps come > up with something not as crude as the below and possibly even recursive. > Â i.e. the above would ideally be reduced to e.g. > NEXT 7 LINES REPEAT 123456 TIMES > --- SIGALRM (Alarm clock) @ 0 (0) --- > gettimeofday({1265744797, 316183}, NULL) = 0 > sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) > NEXT 2 LINES REPEAT BETWEEN 500 AND 800 TIMES > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > ioctl(8, 0x80045530, 0xbfd4fe70) Â Â Â Â = 0 > ioctl(8, 0xc1205531, 0xbfd4fb80) Â Â Â Â = 0 > --- SIGALRM (Alarm clock) @ 0 (0) --- > gettimeofday({1265744797, 317189}, NULL) = 0 > sigreturn() Â Â Â Â Â Â Â Â Â Â Â Â Â Â = ? (mask now []) > > > Here's my quick hack that I ran in vw7.7nc: > | f o lines maxrun repeats range | > f := '../Cog/squeak.strace.log' asFilename readStream. > o := 'compressed.log' asFilename writeStream. > lines := OrderedCollection new. > maxrun := 50. > repeats := 0. > range := nil. > [[f atEnd] whileFalse: > [lines size > maxrun ifTrue: > [repeats > 0 > ifTrue: > [1 to: range first - 1 do: > [:i| o nextPutAll: (lines at: i); cr]. > o nextPutAll: 'NEXT '; print: range size; nextPutAll: ' LINES REPEAT '; > print: repeats + 1; nextPutAll: ' TIMES'; cr. > range do: > [:i| o nextPutAll: (lines at: i); cr]. > lines removeFirst: range last. > repeats := 0] > ifFalse: > [o nextPutAll: lines removeFirst; cr; flush]. > range := nil]. > lines addLast: (f upTo: Character cr). > [:exit| > 1 to: lines size do: > [:i| | line repeat | > line := lines at: i. > repeat := lines nextIndexOf: line from: i + 1 to: lines size. > (repeat ~~ nil > and: [lines size >= (repeat - i * 2 + i) > and: [(i to: repeat - 1) allSatisfy: [:j| (lines at: j) = (lines at: j - i + > repeat)]]]) ifTrue: > [repeats := repeats + 1. > range isNil > ifTrue: [range := i to: repeat - 1] > ifFalse: > [range = (i to: repeat - 1) ifTrue: > [range do: [:ignore| lines removeAtIndex: repeat]. > exit value]]]]] valueWithExit]] > ensure: [f close. o close]. > repeats > Forgive the cross post. Â I expect deep expertise in each newsgroup posted > to. > best > Eliot > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 10, 2010

Re: [Pharo-project] [squeak-dev] File out as Ruby - Possible ?

by Lukas Renggli

Have a look at the RB AST. You can traverse the AST similar to the pretty-printer that is included (RBFormatter and RBConfigurableFormatter) and instead emit Ruby. I've done something similar for Javascript, and others have done it for other languages. Lukas On 10 February 2010 16:51, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Hi, > > Do you know if it's possible to export smalltalk code in ruby ? > I have to port a small app I did and so, it could help me :) > > I don't think there's an existing tool, but maybe some directions... > Actually, I'd prefer writing a simple tool to do that rather than > doing all by hand. > > I don't expect it to work out of the box, but just save me some time. > > TIA > > -- > CÃ©drick > > -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 10, 2010

[Pharo-project] Diff tools

by Torsten Bergmann

Gary wrote: >Done for Polymorph-Tools-Diff-gvc.21. Coool, thanks! Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

Feb. 10, 2010

Re: [Pharo-project] creating a new metacello version from current commited packages

by Fernando olivero

YES!!!! To create a new version from the current versions IN the repository, or LOADED in the image also would work. thanks Tudor for the detailed description! Fernando On Feb 10, 2010, at 4:28 PM, Tudor Girba wrote: > Hi, > > Well, before you will release anything, you will want those packages > in your image to see if it works. > > To get the latest versions of all packages from a configuration, just > load a baseline and if there are no hardcoded versions in it, you get > the latest code. Afterwards, you just create a new version from that > baseline. > > Is that not the use case? > > Cheers, > Doru > > On 10 Feb 2010, at 16:24, Mariano Martinez Peck wrote: > >> >> >> On Wed, Feb 10, 2010 at 4:21 PM, Tudor Girba <tudor.girba(a)gmail.com> >> wrote: >> Hi, >> >> You get this behavior in Spawn New Version in the OB-Metacello and in >> GTMetaceller. >> >> To run GTMetaceller you have to have Metacello 1.0-beta.23. To get it: >> >> Gofer new >> squeaksource: 'glamoroust'; >> package: 'ConfigurationOfGlamoroust'; >> load. >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. >> (Smalltalk at: #GTMetaceller) perform: #open >> >> >> Tudor: I think there is a little different. We wanted the last >> version that is in the repository (if I understood ok), but the >> spawn says "The package specs for the new method reflect the >> currently loaded Monticello package versions" So....he has to load >> first all the last versions ? >> >> >> >> Cheers, >> Doru >> >> >> On 10 Feb 2010, at 15:54, Mariano Martinez Peck wrote: >> >>> >>> >>> On Wed, Feb 10, 2010 at 3:49 PM, Fernando olivero <oliverof(a)lu.unisi.ch >>>> wrote: >>> Hi, is this feature available in Metacello? >>> >>> To create a new version automatically by >>> 1. using latest version number found in any method + 1 , in >>> the ConfigurationOfXXX) >>> 2. using commited packages in the repository >>> >>> Something like >>> >>> ConfigurationOfXXX>>createVersionNamed: aVersionNameSelector >>> >>> >>> That would compile the method >>> ConfigurationOfXXX>>aVersionNameSelector >>> <version: 'lastestVersion+1' imports: #('1.0- >>> baseline')> >>> spec for: .... do: [ >>> spec blessing: #development. >>> spec repository: 'http://www.squeaksource.com/XXX'. >>> spec >>> author:'Me'; >>> package: 'Gaucho-Core' with: 'Gaucho-Core- >>> FernandoOlivero.78' ; >>> package: 'Gaucho-Drawables' with:'Gaucho- >>> Drawables-FernandoOlivero.37' ; >>> ..... >>> >>> Or everybody is creating new version by hand, fetching the latest >>> versions names from the monticello repo? >>> >>> I am doing exactly that. But that's because I don't like and I don't >>> trust in automagic ;) >>> >>> Anyway, I think that the Metacello-OB tools may help you there. I am >>> not sure as I don't use such tools, but maybe there is something. >>> You should take a look or wait for other responses ;) >>> >>> Check: http://code.google.com/p/metacello/wiki/MetacelloTools >>> >>> Cheers >>> >>> Mariano >>> >>> >>> >>> Thanks, >>> Fernando >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "It's not how it is, it is how we see it." >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of > problem understanding." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 10, 2010

[Pharo-project] File out as Ruby - Possible ?

by CÃ©drick BÃ©ler

Hi, Do you know if it's possible to export smalltalk code in ruby ? I have to port a small app I did and so, it could help me :) I don't think there's an existing tool, but maybe some directions... Actually, I'd prefer writing a simple tool to do that rather than doing all by hand. I don't expect it to work out of the box, but just save me some time. TIA -- CÃ©drick

Feb. 10, 2010

Re: [Pharo-project] creating a new metacello version from current commited packages

by Tudor Girba

Hi, Well, before you will release anything, you will want those packages in your image to see if it works. To get the latest versions of all packages from a configuration, just load a baseline and if there are no hardcoded versions in it, you get the latest code. Afterwards, you just create a new version from that baseline. Is that not the use case? Cheers, Doru On 10 Feb 2010, at 16:24, Mariano Martinez Peck wrote: > > > On Wed, Feb 10, 2010 at 4:21 PM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > Hi, > > You get this behavior in Spawn New Version in the OB-Metacello and in > GTMetaceller. > > To run GTMetaceller you have to have Metacello 1.0-beta.23. To get it: > > Gofer new > squeaksource: 'glamoroust'; > package: 'ConfigurationOfGlamoroust'; > load. > (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > (Smalltalk at: #GTMetaceller) perform: #open > > > Tudor: I think there is a little different. We wanted the last > version that is in the repository (if I understood ok), but the > spawn says "The package specs for the new method reflect the > currently loaded Monticello package versions" So....he has to load > first all the last versions ? > > > > Cheers, > Doru > > > On 10 Feb 2010, at 15:54, Mariano Martinez Peck wrote: > > > > > > > On Wed, Feb 10, 2010 at 3:49 PM, Fernando olivero <oliverof(a)lu.unisi.ch > > > wrote: > > Hi, is this feature available in Metacello? > > > > To create a new version automatically by > > 1. using latest version number found in any method + 1 , in > > the ConfigurationOfXXX) > > 2. using commited packages in the repository > > > > Something like > > > > ConfigurationOfXXX>>createVersionNamed: aVersionNameSelector > > > > > > That would compile the method > > ConfigurationOfXXX>>aVersionNameSelector > > <version: 'lastestVersion+1' imports: #('1.0- > > baseline')> > > spec for: .... do: [ > > spec blessing: #development. > > spec repository: 'http://www.squeaksource.com/XXX'. > > spec > > author:'Me'; > > package: 'Gaucho-Core' with: 'Gaucho-Core- > > FernandoOlivero.78' ; > > package: 'Gaucho-Drawables' with:'Gaucho- > > Drawables-FernandoOlivero.37' ; > > ..... > > > > Or everybody is creating new version by hand, fetching the latest > > versions names from the monticello repo? > > > > I am doing exactly that. But that's because I don't like and I don't > > trust in automagic ;) > > > > Anyway, I think that the Metacello-OB tools may help you there. I am > > not sure as I don't use such tools, but maybe there is something. > > You should take a look or wait for other responses ;) > > > > Check: http://code.google.com/p/metacello/wiki/MetacelloTools > > > > Cheers > > > > Mariano > > > > > > > > Thanks, > > Fernando > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "It's not how it is, it is how we see it." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Feb. 10, 2010

Re: [Pharo-project] creating a new metacello version from current commited packages

by Mariano Martinez Peck

On Wed, Feb 10, 2010 at 4:21 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > You get this behavior in Spawn New Version in the OB-Metacello and in > GTMetaceller. > > To run GTMetaceller you have to have Metacello 1.0-beta.23. To get it: > > Gofer new > squeaksource: 'glamoroust'; > package: 'ConfigurationOfGlamoroust'; > load. > (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > (Smalltalk at: #GTMetaceller) perform: #open > > Tudor: I think there is a little different. We wanted the last version that is in the repository (if I understood ok), but the spawn says "The package specs for the new method reflect the currently loaded Monticello package versions" So....he has to load first all the last versions ? > > Cheers, > Doru > > > On 10 Feb 2010, at 15:54, Mariano Martinez Peck wrote: > > > > > > > On Wed, Feb 10, 2010 at 3:49 PM, Fernando olivero <oliverof(a)lu.unisi.ch > > > wrote: > > Hi, is this feature available in Metacello? > > > > To create a new version automatically by > > 1. using latest version number found in any method + 1 , in > > the ConfigurationOfXXX) > > 2. using commited packages in the repository > > > > Something like > > > > ConfigurationOfXXX>>createVersionNamed: aVersionNameSelector > > > > > > That would compile the method > > ConfigurationOfXXX>>aVersionNameSelector > > <version: 'lastestVersion+1' imports: #('1.0- > > baseline')> > > spec for: .... do: [ > > spec blessing: #development. > > spec repository: 'http://www.squeaksource.com/XXX'. > > spec > > author:'Me'; > > package: 'Gaucho-Core' with: 'Gaucho-Core- > > FernandoOlivero.78' ; > > package: 'Gaucho-Drawables' with:'Gaucho- > > Drawables-FernandoOlivero.37' ; > > ..... > > > > Or everybody is creating new version by hand, fetching the latest > > versions names from the monticello repo? > > > > I am doing exactly that. But that's because I don't like and I don't > > trust in automagic ;) > > > > Anyway, I think that the Metacello-OB tools may help you there. I am > > not sure as I don't use such tools, but maybe there is something. > > You should take a look or wait for other responses ;) > > > > Check: http://code.google.com/p/metacello/wiki/MetacelloTools > > > > Cheers > > > > Mariano > > > > > > > > Thanks, > > Fernando > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "It's not how it is, it is how we see it." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 10, 2010

Re: [Pharo-project] Diff tools

by Gary Chambers

Done for Polymorph-Tools-Diff-gvc.21. Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, February 10, 2010 1:12 PM Subject: Re: [Pharo-project] Diff tools Not entirely simple, but doable... Regards, Gary ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, February 10, 2010 12:00 PM Subject: [Pharo-project] Diff tools Hi Gary, the diff tools are really great. One feature I miss from Eclipse - when one clicks on one of the small rectangles (in the gradient area beside the srollbar) the editor in eclipse jumps to the according change (adapting the scroll bar). Maybe it is simple to add... Thanks Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 10, 2010