August 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14096

by Marcus Denker

14096 ----- Issue 4592: ToolSet is deprecated http://code.google.com/p/pharo/issues/detail?id=4592 Issue 4576: MessageNames should be deprecated http://code.google.com/p/pharo/issues/detail?id=4576 Issue 3235: better bag sum http://code.google.com/p/pharo/issues/detail?id=3235 -- Marcus Denker -- http://marcusdenker.de

Aug. 19, 2011

Re: [Pharo-project] Smalltalk tools transcript

by Pavel Krivanek

http://code.google.com/p/pharo/issues/detail?id=4661 On Fri, Aug 19, 2011 at 10:41 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > Igor changed some uses of "Transcript" to "Smalltalk tools > transcript". Of course it is not bad idea however it has some > unwelcome consequences - mainly it cannot work on images that have no > tools and Pharo Kernel and most of derived images have no ToolRegistry > at all. Currently it breaks Pharo Kernel job on CI server. > > Here are affected methods: > > Object>>crLog: {logging} > Object>>log: {logging} > Object>>logCr: {logging} > Object>>logCrTab: {logging} > > Of course the simplest way how to fix that is revert previous versions > of this methods. However we may use some more general solution where > ToolRegistry will be part of the kernel but then we will have to solve > questions what tools are default, what to do if the tool class is > missing etc. > > -- Pavel >

Aug. 19, 2011

[Pharo-project] Smalltalk tools transcript

by Pavel Krivanek

Hi, Igor changed some uses of "Transcript" to "Smalltalk tools transcript". Of course it is not bad idea however it has some unwelcome consequences - mainly it cannot work on images that have no tools and Pharo Kernel and most of derived images have no ToolRegistry at all. Currently it breaks Pharo Kernel job on CI server. Here are affected methods: Object>>crLog: {logging} Object>>log: {logging} Object>>logCr: {logging} Object>>logCrTab: {logging} Of course the simplest way how to fix that is revert previous versions of this methods. However we may use some more general solution where ToolRegistry will be part of the kernel but then we will have to solve questions what tools are default, what to do if the tool class is missing etc. -- Pavel

Aug. 19, 2011

Re: [Pharo-project] [ANN] Fuel release version 1.6

by Mariano Martinez Peck

Ahh and thanks to Claire Barroca we now have a wonderful logo: http://rmod.lille.inria.fr/web/pier/software/Fuel On Fri, Aug 19, 2011 at 6:14 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hello! > > I want to announce the new release version number 1.6 of Fuel, a > binary serialization framework for Pharo that provides extremely fast > deserialization. More information on our home page<http://rmod.lille.inria.fr/web/pier/software/Fuel>. Again, > I thank ESUG for sponsoring me through the SummerTalk<http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011>program. > > You can download this version in Pharo 1.2.1 with: > > Gofer new > squeaksource: 'Fuel'; > package: 'ConfigurationOfFuel'; > load. > ((Smalltalk at: #ConfigurationOfFuel) project version: '1.6') load. > > This version does not add any new concrete functionality but has two main > achievements: a performance improvement and a design clean up. > > Many changes included in this release are part of a design clean up. They > are a necessary step forward to new functionalities that are coming soon. > They make code more understandable. They enable simpler extension. Happily > they also helped to improve serialization performance by reducing > unnecessary interactions. And it is specially important a bottleneck in > graph analysis stage we have successfully attacked, obtaining great results. > > Details: > - Removed explicit references to cluster classes scattered around the > system. For example, in previous versions Float>>fuelCluster has an explicit > reference to FLFloatCluster. This version replaces this by a double dispatch > interaction. > - Clusters: Better reification. Removed annoying IDs. Removed Singleton > instance creation mechanism, now mappers manage uniqueness in a better way. > - Mappers: They were simplified. New mapping machanism inspired on Chain of > Responsibility pattern. The global objects detection has been optimized > considerably. > - Analyzer: Part of its behavior and state has been moved to a new > abstraction called 'clusterization'. > > Best regards, > MartÃn Dias > -- Mariano http://marianopeck.wordpress.com

Aug. 19, 2011

[Pharo-project] [update 1.4] #14095

by Marcus Denker

14095 ----- Issue 4659: Typo on Pragma class comment http://code.google.com/p/pharo/issues/detail?id=4659 Issue 4657: cull: nice method comments http://code.google.com/p/pharo/issues/detail?id=4657 Issue 4637: Method to shrink to PharoCore http://code.google.com/p/pharo/issues/detail?id=4637 -- Marcus Denker -- http://marcusdenker.de

Aug. 19, 2011

Re: [Pharo-project] [ANN] Fuel release version 1.6

by Mariano Martinez Peck

On Fri, Aug 19, 2011 at 6:14 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hello! > > I want to announce the new release version number 1.6 of Fuel, a > binary serialization framework for Pharo that provides extremely fast > deserialization. More information on our home page<http://rmod.lille.inria.fr/web/pier/software/Fuel>. Again, > I thank ESUG for sponsoring me through the SummerTalk<http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011>program. > > You can download this version in Pharo 1.2.1 with: > > Or Pharo 1.1 or 1.1.1 or 1.3 or 1.4 :) > Gofer new > squeaksource: 'Fuel'; > package: 'ConfigurationOfFuel'; > load. > ((Smalltalk at: #ConfigurationOfFuel) project version: '1.6') load. > > Notice that as always, since Fuel is being developed, this version is NOT compatible with older versions. That means, you cannot materialize with this version a stream which was serialized with an older version. What you have to do is: 1) materialize your graph. 2) update Fuel. 3) serialize again. > This version does not add any new concrete functionality but has two main > achievements: a performance improvement and a design clean up. > > Many changes included in this release are part of a design clean up. They > are a necessary step forward to new functionalities that are coming soon. > They make code more understandable. They enable simpler extension. Happily > they also helped to improve serialization performance by reducing > unnecessary interactions. And it is specially important a bottleneck in > graph analysis stage we have successfully attacked, obtaining great results. > > Details: > - Removed explicit references to cluster classes scattered around the > system. For example, in previous versions Float>>fuelCluster has an explicit > reference to FLFloatCluster. This version replaces this by a double dispatch > interaction. > - Clusters: Better reification. Removed annoying IDs. Removed Singleton > instance creation mechanism, now mappers manage uniqueness in a better way. > - Mappers: They were simplified. New mapping machanism inspired on Chain of > Responsibility pattern. The global objects detection has been optimized > considerably. > - Analyzer: Part of its behavior and state has been moved to a new > abstraction called 'clusterization'. > > Best regards, > MartÃn Dias > -- Mariano http://marianopeck.wordpress.com

Aug. 19, 2011

Re: [Pharo-project] Alien bug fix

by StÃ©phane Ducasse

:) Most of the things we do for pharo are freely available On Aug 19, 2011, at 9:21 AM, Torsten Bergmann wrote: > Just found the tex file: > > https://github.com/SquareBracketAssociates/PharoByExample-english/blob/mast… > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >

Aug. 19, 2011

Re: [Pharo-project] Squeak/Pharo on touchscreen: requesting opinions

by StÃ©phane Ducasse

HI dimitry I'm slowly working on a clean of the way event are managed in Pharo (double dispatch instead of large case statements, use of objects instead of array). The idea is to be able to support extension like multitouch support, genie use. So if you are interested we could pair-clean but this is far from your current work. I'm eager to play with Pharo on an android device. Stef On Aug 19, 2011, at 9:23 AM, Douglas Brebner wrote: > On 18/08/2011 19:40, Dimitry Golubovsky wrote: >> I am asking your opinion here (as much of opinion can be had about >> something only imaginary) - is the latter method worth implementing: >> would one like to use it if available? >> >> Thanks. >> > > One thing to bear in mind is that both Android and Morphic support multitouch; specifically, Morphic supports multiple simultaneous Hands (in theory, whether the code still works is another matter). > > I believe Bert did a demo of multitouch in Squeak (Etoys) on an iPad >

Aug. 19, 2011

Re: [Pharo-project] Squeak/Pharo on touchscreen: requesting opinions

by Douglas Brebner

On 18/08/2011 19:40, Dimitry Golubovsky wrote: > I am asking your opinion here (as much of opinion can be had about > something only imaginary) - is the latter method worth implementing: > would one like to use it if available? > > Thanks. > One thing to bear in mind is that both Android and Morphic support multitouch; specifically, Morphic supports multiple simultaneous Hands (in theory, whether the code still works is another matter). I believe Bert did a demo of multitouch in Squeak (Etoys) on an iPad

Aug. 19, 2011

[Pharo-project] Alien bug fix

by Torsten Bergmann

Just found the tex file: https://github.com/SquareBracketAssociates/PharoByExample-english/blob/mast… -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Aug. 19, 2011