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

[Pharo-project] TWM bug when deleting a snapshot

by Sean P. DeNigris

Snapshots are cool! But try this: 1. create two snapshots 2. navigate to the last one 3. delete it Although it is shown removed from the list (i.e. "1/1"), you are not automatically navigated back to the first one. You stay on the deleted one, and when you navigate back to the first with the arrow, the deleted one reappears in the list (i.e. "1/2") Sean -- View this message in context: http://forum.world.st/TWM-bug-when-deleting-a-snapshot-tp4243197p4243197.ht… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 29, 2011

[Pharo-project] Loading projects into changing Pharo

by Sean P. DeNigris

This is an important question that deserves its own thread... > I was wondering what is planned regarding packages available on > SqueakSource and Pharo. More and more packages can't load in Pharo and it > gets more and more frustrating not being able to load anything without > having to add/modify methods/classes all over the place so those packages > can load properly in Pharo. Are we looking at a Pharo-only kind of > SqueakSource in the future ? > > Besides, having to handle platform specific (i.e. Pharo vs Squeak) for > every package is adding more complexity than what is needed. I know > backward compatibility was thrown away from the start to avoid compromises > in Pharo but how do we take care of the fact that as each day passes, less > and less stuff from SqueakSource is usable in Pharo ? > > tia > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > -- View this message in context: http://forum.world.st/Loading-projects-into-changing-Pharo-tp4243184p424318… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 29, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 98 - ZipFileConstants

by Sean P. DeNigris

StÃ©phane Ducasse wrote > > I defined some constant for the file compression. > Thanks, Steph! -- View this message in context: http://forum.world.st/Re-Pharo-users-COTDC-98-ZipFileConstants-tp4242780p42… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 29, 2011

Re: [Pharo-project] [COTDC] 98 - ZipFileConstants

by Sean P. DeNigris

Ben Coman wrote > > This class defines magic numbers taken from the PKWARE ZIP Application... > Wow! Thanks, Ben. -- View this message in context: http://forum.world.st/COTDC-98-ZipFileConstants-tp4240714p4243171.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 29, 2011

[Pharo-project] Packages and Pharo and Portability : the 3 Ps !

by Benoit St-Jean

I was wondering what is planned regarding packages available on SqueakSource and Pharo.Â More and more packages can't load in Pharo and it gets more and more frustrating not being able to load anything without having to add/modify methods/classes all over the place so those packages can load properly in Pharo.Â Are we looking at a Pharo-only kind of SqueakSource in the future ?Â Besides, having to handle platform specific (i.e. Pharo vs Squeak) for every package is adding more complexity than what is needed.Â I know backward compatibility was thrown away from the start to avoid compromises in Pharo but how do we take care of the fact that as each day passes, less and less stuff from SqueakSource is usable in Pharo ? tia Â ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

Dec. 29, 2011

Re: [Pharo-project] [update 1.4] #14276

by Benjamin

On Dec 29, 2011, at 2:42 PM, StÃ©phane Ducasse wrote: > 14276 > ----- > > - Issue 5135: Set>>grow buggy for sets with nil. Thanks Igor Stasenko. > http://code.google.com/p/pharo/issues/detail?id=5135 > > - Issue 5130: Remove magicHalo behavior. > http://code.google.com/p/pharo/issues/detail?id=5130 > > Stef and Igor Hacking HazelTracer > I wish you good luck :) Ben

Dec. 29, 2011

Re: [Pharo-project] Possible bug in FFI

by StÃ©phane Ducasse

Can you try simply removing the method? Stef On Dec 29, 2011, at 12:29 PM, Mariano Martinez Peck wrote: > > > On Thu, Dec 29, 2011 at 12:23 AM, ncalexan <ncalexander(a)gmail.com> wrote: > Hello all, > > Long-time reader, first-time poster. > > Hi and welcome :) > > Is FFI fully supported on Pharo? I > installed into the 1.3 OneClick using > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfFFI'; > load. > > ConfigurationOfFFI load. > > All seems fine but > > ExternalAddress gcallocate: 128 > > fails in ExternalAddress>>shallowCopy, complaining that clone is not > understood. > > Bug? Not supported? Misused? > > > Indeed, it looks like a bug at least for pharo (where #clone was removed) > > ExternalAddress >> shallowCopy > "Re-implemented to avoid superclass call to #new:" > ^self clone > > But now sure what to replace it with. The method #clone used to be just the call to primitive 148, which is the same as shallowCopy. So I don't understand why we need to reimplement shallowCopy in ExternalAddress. > "Re-implemented to avoid superclass call to #new:" since shallowCopy is a primitive, it would only send a message (like #new:) only if the primitive fails. So..I am lost. > > > > > Best, > Nick Alexander > > -- > View this message in context: http://forum.world.st/Possible-bug-in-FFI-tp4241299p4241299.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Dec. 29, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 98 - ZipFileConstants

by StÃ©phane Ducasse

I defined some constant for the file compression. On Dec 28, 2011, at 7:50 PM, sean(a)clipperadams.com wrote: > 97 classes done > 798 classes remaining > Continuing in Compression... > > Today: ZipFileConstants > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > p.s. this message was sent from a pharo image. Did you know you could easily do that?! >

Dec. 29, 2011

Re: [Pharo-project] Roeltyper

by StÃ©phane Ducasse

On Dec 28, 2011, at 7:24 PM, Lukas Renggli wrote: >> Yes when I looked at RB (in 99) I guess that they also used existing instances to try to get more >> information but mainly for instance variables. > > I am not aware of such code. RBRefactoryTyper is part of the > refactoring engine since I first looked at it around ESUG 2002. May be it was mentioned in their ecoop paper or in some workshop. I had fun with it when I wrote the message passing control paper in 98 after may be john told me that t was experimental. > It is > relatively hidden, and only used by a few refactorings to provide > better default suggestions (i.e. extract to component). It is also > used in OB to provide a better default class comment template. And in > ECompletion for better suggestions since RoelTyper is not useable > anymore. > >> I would really like to see more work around practical tools that can help us. I have the work on type inference >> from francisco garau on my hard-disc. But this is a pity that nobody build on top of that. > > Never heard of that code. I can put it on a server. This was the master thesis of Francisco Garau. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Dec. 29, 2011

[Pharo-project] [update 1.4] #14276

by StÃ©phane Ducasse

14276 ----- - Issue 5135: Set>>grow buggy for sets with nil. Thanks Igor Stasenko. http://code.google.com/p/pharo/issues/detail?id=5135 - Issue 5130: Remove magicHalo behavior. http://code.google.com/p/pharo/issues/detail?id=5130 Stef and Igor Hacking HazelTracer

Dec. 29, 2011