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

Re: [Pharo-dev] Nautilus unload...

by StÃ©phane Ducasse

Each group registers to event. Now I will try to unregister them all. > The problem is that there is a registration mechanism somewhere :) > > <Screen Shot 2013-11-29 at 10.13.30 PM.pdf>

Nov. 30, 2013

Re: [Pharo-dev] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Denis Kudriashov

2013/11/30 Sean P. DeNigris <sean(a)clipperadams.com> > Denis Kudriashov wrote > > I don't remember is it was public conclusion but we agree to try > > StateSpecs > > for Phexample. > > After I finish key features of TxText I will adapt StateSpecs to satisfy > > Camillo requirements. > > Double bump ;) I want to try Mocketry, but I'm already using Phexample, so > I need them to be compatible... > Now loading Mocketry will override existed #should implementation. So your Phexample "should expressions" will evaluated by Mocketry system. And if I remember correctly Yuriy added some compatibility messages to Mocketry to make it usage seamless for Phexample tests. Unfortunately I don't have time now to move StateSpecs to Phexample. But I will work on it some day. Best regards, Denis

Nov. 30, 2013

Re: [Pharo-dev] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Sean P. DeNigris

Denis Kudriashov wrote > I don't remember is it was public conclusion but we agree to try > StateSpecs > for Phexample. > After I finish key features of TxText I will adapt StateSpecs to satisfy > Camillo requirements. Double bump ;) I want to try Mocketry, but I'm already using Phexample, so I need them to be compatible... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Suggestion-about-Phexample-and-StateSpecs-Mocketry-in… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 30, 2013

Re: [Pharo-dev] Coordinates problem with Athens and Morphic while coding Hyperion

by Alexandre Bergel

No pb, I think I know how to fix this Alexandre > Le 29-11-2013 Ã 17:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : > > >> So far you cannot import, but only export SVG in Roassal. I know Athens has an SVG importer, but I have faced some problems with it. > > and do not expect it to be fixed soon. Because we have other priorities. > > Stef

Nov. 30, 2013

Athens-Cairo is part of Pharo?

by Bernardo Ezequiel Contreras

Hi all, There's a deprecated method in Athens-Cairo. method: AthensCairoSurface>>#createLinearGradient:origin:corner: category: #paints package: RGPackage(Athens-Cairo) Should i move it to Deprecated package? https://pharo.fogbugz.com/f/cases/11668/Move-all-deprecated-method-to-Depre… Thanks. -- Bernardo E.C. Sent from a cheap desktop computer in South America.

Nov. 29, 2013

Re: [Pharo-dev] Stepping through with GLORP Proxies

by Esteban A. Maringolo

2013/11/29 Eliot Miranda <eliot.miranda(a)gmail.com>: > On Fri, Nov 29, 2013 at 1:06 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: >> On 29 Nov 2013, at 22:03, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> > Does the Pharo debugger use the mirror primitives yet? >> No. I think the methods are not even in the image. > I'll either prepare a change set or submit. It'll get done. Thank you Eliot. I can continue stepping into until the change is ready. Please make it compatible with Pharo 2 (whatever that means in term of code) :) Best regards,

Nov. 29, 2013

Re: [Pharo-dev] Stepping through with GLORP Proxies

by Frank Shearar

On 29 November 2013 21:02, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Does the Pharo debugger use the mirror primitives yet? Unless > InstructionStream and ContextPart have been updated to use objectClass: and > objectInstVarAt: et al then the debugger will be fooled by proxies. I > really need to push this code through to Squeak trunk. Once I've done that > (Monday? it's thanksgiving here and its party time :-) ) Pharo can perhaps > adopt the code too. > > David, does the Interpreter support the mirror primitives yet? i.e. do the > MirrorPrimitiveTests pass on the Interpreter now? Obviously I'm not David, but http://build.squeak.org/job/SqueakTrunkOnInterpreter/329/testReport/Tests.C… tells me that yes, they are passing on the Interpreter VM. frank > On Fri, Nov 29, 2013 at 6:03 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: >> >> Does anybody else have issues while stepping through GLORP Proxy objects >> (collections in this case)? >> >> I simply can't use this feature unless the proxied collection was already >> materialized. >> >> I can't reproduce it right now, but it bites me everytime is step through >> blocks, because stepping into is really annoying :) >> >> >> Does anybody else have the same issue? >> >> This is Pharo 2. >> >> >> Esteban A. Maringolo > > > > > -- > best, > Eliot

Nov. 29, 2013

Similarity Matrix

by Alexandre Bergel

Hi! I know some of you are working on DSM-kind of matrix. Oscar has been working on a similarity matrix for Roassal. I just want to share a self-explanble screenshot with you guys. On this example, the methods of the subclasses of Set are compared between themselves. Black dot is a couple (m1, m2) that are very similar More on https://www.facebook.com/media/set/?set=a.550677725018829.1073741833.340543… Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 29, 2013

Re: [Pharo-dev] Nautilus unload...

by StÃ©phane Ducasse

The problem is that there is a registration mechanism somewhere :)

Nov. 29, 2013

Re: [Pharo-dev] Nautilus unload...

by StÃ©phane Ducasse

On Nov 27, 2013, at 4:29 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > hi, > > I think is nothing to do with PackageTree but with the fact that now groups are shown (and because of that created), > So, probably reseting the groups before unloading would do the trick. > > {Nautilus. PackageTreeNautilus} do: #resetGroups. just to tell you; resetGroups is missing in Nautilus but even then it does not solve my problem. stef > > Esteban > > > On Wed, Nov 27, 2013 at 8:05 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi esteban > > I'm looking for a change due to the TreePackage introduction. > Before I could simply do something like the following to unload Nautilus > > > Smalltalk tools remove: #browser. > Smalltalk tools register: Browser as: #browser. > (MCWorkingCopy forPackage: (MCPackage named: 'NautilusRefactoring')) unload. "OK" > > #Nautilus asClass cleanUp. > KMRepository reset. > KMPragmaKeymapBuilder release. > #NautilusUI asClass allSubInstances do: [ :inst | > SystemAnnouncer uniqueInstance unsubscribe: inst]. > Smalltalk garbageCollect. > (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload. > (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload. > > And now if does not work anymore. I get some TreePackage around. > > Apparently I get a weakMessageSend on classRemoved: and this message refers to an obsoletePackageTreeNautilus class. > > buildGroupManagerFor: anInstance > > | holder | > holder := GroupHolder new. > (holder > addADynamicClassGroupSilentlyNamed: 'Most Viewed Classes' > block: [ anInstance recentClassesElements ]) removable: false. > (holder > addADynamicClassGroupSilentlyNamed: 'Last Modified Classes' > block: [ self lastModifiedClasses ]) removable: false. > > (holder > addADynamicGroupSilentlyNamed: 'Work' > block: [ {} ]) removable: true; isFillable: true. > > ^ holder > > > Do you have any idea? A registration mechanism? from which I forgot to unregister. > > Stef > > >

Nov. 29, 2013