I still have the problem when I use the
Pharo 1.2 image (see the issue for my steps) What has to be done that the fixed beta27.5 is used? I always thought the newest Metacello is loaded automatically if one bootstraps Metacello via a config... I also get it when I run the following in PharoCore 1.2 12235 (the latest from today): Gofer new url: 'http://seaside.gemstone.com/ss/metacello'; package: 'ConfigurationOfMetacello'; load (ConfigurationOfMetacello project version: '1.0-beta.27.5') load Are you sure its fixed? Thx T. -- GRATIS! Movie-FLAT mit über 300 Videos. Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome |
Indeed, I can confirm that the sortBy: problem is not fixed in version 1.0-beta.27.5 :(.
Cheers, Doru On 11 Nov 2010, at 23:27, Torsten Bergmann wrote: > I still have the problem when I use the > Pharo 1.2 image (see the issue for my steps) > > What has to be done that the fixed beta27.5 is used? > I always thought the newest Metacello is loaded > automatically if one bootstraps Metacello via > a config... > > I also get it when I run the following in PharoCore 1.2 12235 > (the latest from today): > > Gofer new > url: 'http://seaside.gemstone.com/ss/metacello'; > package: 'ConfigurationOfMetacello'; > load > > (ConfigurationOfMetacello project version: '1.0-beta.27.5') load > > Are you sure its fixed? > > Thx > T. > -- > GRATIS! Movie-FLAT mit über 300 Videos. > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome > -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one." |
In reply to this post by Torsten Bergmann
Okay, I got rid of all of the senders of sortBy:, but I didn't update
the ensureMetacello code ... at least that's my guess ... I'll check it out now ... Dale On 11/11/2010 02:27 PM, Torsten Bergmann wrote: > I still have the problem when I use the > Pharo 1.2 image (see the issue for my steps) > > What has to be done that the fixed beta27.5 is used? > I always thought the newest Metacello is loaded > automatically if one bootstraps Metacello via > a config... > > I also get it when I run the following in PharoCore 1.2 12235 > (the latest from today): > > Gofer new > url: 'http://seaside.gemstone.com/ss/metacello'; > package: 'ConfigurationOfMetacello'; > load > > (ConfigurationOfMetacello project version: '1.0-beta.27.5') load > > Are you sure its fixed? > > Thx > T. |
Welll....it will be awhile because I'm going to have to download and
update a PharoCore image to test ... sorry about that... Dale On 11/11/2010 02:48 PM, Dale Henrichs wrote: > Okay, I got rid of all of the senders of sortBy:, but I didn't update > the ensureMetacello code ... at least that's my guess ... I'll check it > out now ... > > Dale > > On 11/11/2010 02:27 PM, Torsten Bergmann wrote: >> I still have the problem when I use the >> Pharo 1.2 image (see the issue for my steps) >> >> What has to be done that the fixed beta27.5 is used? >> I always thought the newest Metacello is loaded >> automatically if one bootstraps Metacello via >> a config... >> >> I also get it when I run the following in PharoCore 1.2 12235 >> (the latest from today): >> >> Gofer new >> url: 'http://seaside.gemstone.com/ss/metacello'; >> package: 'ConfigurationOfMetacello'; >> load >> >> (ConfigurationOfMetacello project version: '1.0-beta.27.5') load >> >> Are you sure its fixed? >> >> Thx >> T. > |
In reply to this post by Tudor Girba
Give it another try ... I've updated the ensureMetacello code (no
version change)... Dale On 11/11/2010 02:33 PM, Tudor Girba wrote: > Indeed, I can confirm that the sortBy: problem is not fixed in version 1.0-beta.27.5 :(. > > Cheers, > Doru > > On 11 Nov 2010, at 23:27, Torsten Bergmann wrote: > >> I still have the problem when I use the >> Pharo 1.2 image (see the issue for my steps) >> >> What has to be done that the fixed beta27.5 is used? >> I always thought the newest Metacello is loaded >> automatically if one bootstraps Metacello via >> a config... >> >> I also get it when I run the following in PharoCore 1.2 12235 >> (the latest from today): >> >> Gofer new >> url: 'http://seaside.gemstone.com/ss/metacello'; >> package: 'ConfigurationOfMetacello'; >> load >> >> (ConfigurationOfMetacello project version: '1.0-beta.27.5') load >> >> Are you sure its fixed? >> >> Thx >> T. >> -- >> GRATIS! Movie-FLAT mit über 300 Videos. >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome >> > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > |
Perfect!
Doru On 12 Nov 2010, at 00:13, Dale Henrichs wrote: > Give it another try ... I've updated the ensureMetacello code (no version change)... > > Dale > > On 11/11/2010 02:33 PM, Tudor Girba wrote: >> Indeed, I can confirm that the sortBy: problem is not fixed in version 1.0-beta.27.5 :(. >> >> Cheers, >> Doru >> >> On 11 Nov 2010, at 23:27, Torsten Bergmann wrote: >> >>> I still have the problem when I use the >>> Pharo 1.2 image (see the issue for my steps) >>> >>> What has to be done that the fixed beta27.5 is used? >>> I always thought the newest Metacello is loaded >>> automatically if one bootstraps Metacello via >>> a config... >>> >>> I also get it when I run the following in PharoCore 1.2 12235 >>> (the latest from today): >>> >>> Gofer new >>> url: 'http://seaside.gemstone.com/ss/metacello'; >>> package: 'ConfigurationOfMetacello'; >>> load >>> >>> (ConfigurationOfMetacello project version: '1.0-beta.27.5') load >>> >>> Are you sure its fixed? >>> >>> Thx >>> T. >>> -- >>> GRATIS! Movie-FLAT mit über 300 Videos. >>> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome >>> >> >> -- >> www.tudorgirba.com >> >> "Every now and then stop and ask yourself if the war you're fighting is the right one." >> >> >> -- www.tudorgirba.com "Reasonable is what we are accustomed with." |
Free forum by Nabble | Edit this page |