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

Re: [Pharo-project] Issue 3226 in pharo: New finder enh

by pharo＠googlecode.com

Comment #2 on issue 3226 by Benjamin.VanRyseghem.Pharo: New finder enh http://code.google.com/p/pharo/issues/detail?id=3226 Steph : It's done, and commited on PharoTaskForces gazzaguru2 : I do not know how to do that, but if you can explain it to me, I will be glad :)

Nov. 11, 2010

Re: [Pharo-project] [Metacello] Re: Metacello 1.0-beta.27.5 released

by Tudor Girba

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."

Nov. 11, 2010

[Pharo-project] Issue 3249 in pharo: SourceReference throw an error when <historical> is answered

by pharo＠googlecode.com

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo New issue 3249 by Benjamin.VanRyseghem.Pharo: SourceReference throw an error when <historical> is answered http://code.google.com/p/pharo/issues/detail?id=3249 Attached: the cs Attachments: SourceReferenceHistoricalFix.1.cs 1.4 KB

Nov. 11, 2010

Re: [Pharo-project] Issue 3216 in pharo: [enh] Support for Metacello in Monticello

by pharo＠googlecode.com

Comment #13 on issue 3216 by da...(a)teleport.com: [enh] Support for Metacello in Monticello http://code.google.com/p/pharo/issues/detail?id=3216 I tend to agree, but the MonticelloBrowser is a better place to hang Metacello functionality than the code browser (considering that OB isn't loaded all of the time). I use the OB tools all of the time except when I am in a PharoCore and I miss the tools there ... I am building the tool kit so that the functionality can move around or be implemented in multiple places while maintaining the same functionality ...

Nov. 11, 2010

Re: [Pharo-project] Issue 3189 in pharo: Changes not working since update 12220

by pharo＠googlecode.com

Comment #1 on issue 3189 by guillermopolito: Changes not working since update 12220 http://code.google.com/p/pharo/issues/detail?id=3189 With the last version of PharoCore 1.2 (12233) I did ScriptLoader new cleanUpForRelease the I created a new class and it got logged in the change sorter... So I couldn't reproduce it.

Nov. 11, 2010

Re: [Pharo-project] [Metacello] Re: Metacello 1.0-beta.27.5 released

by Dale Henrichs

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." > > >

Nov. 11, 2010

Re: [Pharo-project] Issue 3216 in pharo: [enh] Support for Metacello in Monticello

by pharo＠googlecode.com

Comment #12 on issue 3216 by alexandre.bergel: [enh] Support for Metacello in Monticello http://code.google.com/p/pharo/issues/detail?id=3216 I agree with you Stef. But I am looking for an easy way to use Metacello

Nov. 11, 2010

Re: [Pharo-project] Issue 3087 in pharo: optimize hasBindingThatBeginsWith:

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3087 by marianopeck: optimize hasBindingThatBeginsWith: http://code.google.com/p/pharo/issues/detail?id=3087 Ok, together with Nicolas Passerini we analyzed the code. Seems to be ok for our point of view. Commited in Name: SLICE-Issue-3087-optimize-hasBindingThatBeginsWith-MarianoMartinezPeck.1 Author: MarianoMartinezPeck Time: 11 November 2010, 7:48:24 pm UUID: 42a67e72-f21b-4157-bf83-9ce961ddc692 Ancestors: Dependencies: System-Support-MarianoMartinezPeck.405 Fix to issue 3087

Nov. 11, 2010

Re: [Pharo-project] Issue 3248 in pharo: Bad error message for non existing changes file.

by pharo＠googlecode.com

Comment #4 on issue 3248 by npasserini: Bad error message for non existing changes file. http://code.google.com/p/pharo/issues/detail?id=3248 Sorry, we mean the ".changes" file. When you open an image, if the corresponding changes file cannot be found, it produces an error message. The former error message said "Pharo cannot locate the changes file XXXX.sources". The new one says "Pharo cannot locate the changes file XXXX.changes". It is only a correctio of the error message.

Nov. 11, 2010

Re: [Pharo-project] Issue 3187 in pharo: Undeclared in SmartRefStream>>#nextPut:

by pharo＠googlecode.com

Comment #1 on issue 3187 by guillermopolito: Undeclared in SmartRefStream>>#nextPut: http://code.google.com/p/pharo/issues/detail?id=3187 There's a line that's using that instance variable, but it was removed. Does it have something to do with the Uniclasses removal? There are no tests for SmartRefStream... :(

Nov. 11, 2010