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

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

by pharo＠googlecode.com

Updates: Status: Closed Comment #11 on issue 3216 by stephane.ducasse: [enh] Support for Metacello in Monticello http://code.google.com/p/pharo/issues/detail?id=3216 in fact I'm not sure that the metacello creation should be driven by the monticello browser but I will integrate it now and we rethink it later. in 12235

Nov. 11, 2010

Re: [Pharo-project] Issue 3185 in pharo: BitmapStreamTests have errors

by pharo＠googlecode.com

Updates: Cc: alexandre.bergel Comment #2 on issue 3185 by guillermopolito: BitmapStreamTests have errors http://code.google.com/p/pharo/issues/detail?id=3185 As we noticed, here are two problems: 1) SmartStreamRef>>nextPut: has already an instance variable that (as we supose) was removed while removing UniClasses) 2) After removing the line using that variable, we had another issue: The test is Saving an ImageSegment in a file, and then it is loading it using (FileDirectory default readOnlyFileNamed: externalSegmentFilename) fileInObjectAndCode which throws an Invalid UTF8 input detected (because it is assuming the file as a text file).

Nov. 11, 2010

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

by Dale Henrichs

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

Nov. 11, 2010

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

by Dale Henrichs

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.

Nov. 11, 2010

Re: [Pharo-project] Issue 3182 in pharo: UndoManagerTest>>#testGrouping failing

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3182 by marianopeck: UndoManagerTest>>#testGrouping failing http://code.google.com/p/pharo/issues/detail?id=3182 (No comment was entered for this change.)

Nov. 11, 2010

Re: [Pharo-project] VM Plugins that are important for performance?

by Levente Uzonyi

On Thu, 11 Nov 2010, Stefan Marr wrote: > Hi Levente: > > > On 11 Nov 2010, at 00:34, Levente Uzonyi wrote: >> I doubt any plugin changes the performance of #tinyBenchmarks. But the following plugins make a huge difference in other benchmarks and GUI performance: >> - MiscPrimitivePlugin >> - LargeIntegers >> - FloatMathPlugin >> - FloatArrayPlugin >> - Matrix2x3Plugin >> - B2DPlugin > > Are you sure about FloatMathPlugin? > I haven't found any usage of it. Neither in Squeak 4.1 nor in Pharo 1.2. Yeah, it's not used at the moment, but it if the primitives are used, then some codes get much faster without a JIT (I don't know if it's faster or slower with Cog). So, you're right, the current images don't need/use it. Therefore it doesn't make a difference. Levente > > Thanks > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

Nov. 11, 2010

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

by pharo＠googlecode.com

Updates: Status: Fixed Comment #10 on issue 3216 by stephane.ducasse: [enh] Support for Metacello in Monticello http://code.google.com/p/pharo/issues/detail?id=3216 ok

Nov. 11, 2010

Re: [Pharo-project] Issue 3240 in pharo: be more explicit about attribute changes to gain another 5-10x speedup

by pharo＠googlecode.com

Updates: Labels: Type-Squeak Comment #3 on issue 3240 by stephane.ducasse: be more explicit about attribute changes to gain another 5-10x speedup http://code.google.com/p/pharo/issues/detail?id=3240 (No comment was entered for this change.)

Nov. 11, 2010

Re: [Pharo-project] Issue 3243 in pharo: enhanced AttributedTextStream so it can be used as a TextStream in some cases.

by pharo＠googlecode.com

Comment #1 on issue 3243 by stephane.ducasse: enhanced AttributedTextStream so it can be used as a TextStream in some cases. http://code.google.com/p/pharo/issues/detail?id=3243 Apparently this fixes is based on the introduction of AttributedTextStream which is used by TextDiffBuilder It seems worth to integrate that and the AttributedTextStream. Now it should probably be put in System-FilePackage instead of Stream.

Nov. 11, 2010

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

by Tudor Girba

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