- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo and the rest of the ecosystem
by Marcus Denker May 2, 2012

May 2, 2012

On May 2, 2012, at 2:33 PM, H. Hirzel wrote: > On 5/1/12, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On May 1, 2012, at 8:44 AM, H. Hirzel wrote: >>> >>> Athens is an SVG canvas using Morphic, right? >>> >> No, Athens is a new Canvas. Vector graphics. >> Morphic is another layer. (Morphic *uses* a Canvas, and of >> course you can just have a canvas in a morphic window for >> drawing). >> >> https://vimeo.com/40653315 >> >>> Where is the code? >>> >> http://www.squeaksource.com/Athens.html > > Thank you Marcus, > > Where can I read more besides this > http://code.google.com/p/pharo/wiki/Athens > Nothing yet. You can bug Igor... :-) There will be more documentation, but keep in mind that this is work in progress and therefore focus is to finish, not to document. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] Pharo and the rest of the ecosystem
by Marcus Denker May 2, 2012

May 2, 2012

On May 1, 2012, at 8:44 AM, H. Hirzel wrote: > > Athens is an SVG canvas using Morphic, right? > No, Athens is a new Canvas. Vector graphics. Morphic is another layer. (Morphic *uses* a Canvas, and of course you can just have a canvas in a morphic window for drawing). https://vimeo.com/40653315 > Where is the code? > http://www.squeaksource.com/Athens.html >> - Ghost > > What is Ghost? A proxy implementation. Where you can proxy even strange objects (classes, methods...) yet it does not require a VM change. http://hal.inria.fr/index.php?halsid=kgvbe2lj6clils0070slhn2t62&view_this_d… >> - Ring > > What is Ring? > Ring is a meta model for smalltalk code that is used already in 1.4 http://hal.inria.fr/index.php?halsid=kgvbe2lj6clils0070slhn2t62&view_this_d… Marcus -- Marcus Denker -- http://marcusdenker.de

2 2

[Pharo-project] Deprecate FileDirectory
by Damien Cassou May 2, 2012

May 2, 2012

Do we have to deprecate all methods of the FileDirectory API? http://code.google.com/p/pharo/issues/detail?id=5772 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

Re: [Pharo-project] Pharo 2.0: Just need a recompileAll or a real problem in background?
by Marcus Denker May 2, 2012

May 2, 2012

On May 2, 2012, at 10:27 AM, Mariano Martinez Peck wrote: > > Ok, I wrote an ugly test and I noticed that the ONLY method with this problem in the image is > > > | behaviorAssociations broken | > behaviorAssociations := Smalltalk globals associations select: [:each | each value isBehavior or: [each value isTrait]]. > broken := OrderedCollection new. > (CompiledMethod allInstances select: [:each | each isInstalled]) > do: [:aMethod | aMethod literals > do: [:aLiteral | aLiteral isVariableBinding > ifTrue: [ ((behaviorAssociations includes: aLiteral) > and: [(behaviorAssociations identityIncludes: aLiteral) not]) > ifTrue: [broken add: (aMethod -> aLiteral)] > ] > ] > ]. > broken inspect > > And I have 6 methods from the classes SmalltalkImage and ScriptLoader and all the 6 literals are pointing to ScriptLoader. So something weird happened with this class. > Any idea? > Maybe monticello does not recompile sometimes a method when it should? > For the moment I will update the test and do a Compiler recompileAll. > ok. -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] problem with tempNamed: in Pharo 2.0
by Mariano Martinez Peck May 2, 2012

May 2, 2012

Hi guys. I noticed stef did this issue: http://code.google.com/p/pharo/issues/detail?id=5642 However, now I have the following test that fails in Pharo 2.0 but works fine in 1.4: | string context | string := 'test'. context := [self class. string asUppercase] asContext. self assert: (context tempNamed: 'string') = 'test' the current implementation of #tempNamed: is: tempNamed: aName "Returns the value of the temporaries, aName." "Implementation notes: temporary initialization in blocks simply uses pushNil to allocate and initialize each temp. So if one inspects [|a|a:=2] and sends it self method symbolic you get: 13 <8F 00 00 05> closureNumCopied: 0 numArgs: 0 bytes 17 to 21 17 <73> pushConstant: nil 18 <77> pushConstant: 2 19 <81 40> storeIntoTemp: 0 21 <7D> blockReturn 22 <7C> returnTop And when we check self asContext pc we get 17, which is *before* the nil is pushed. Therefore we should pay attention when querying a temporary if the temporary allocation was executed." | index | index := (self tempNames indexOf: aName). ^ index >= stackp ifTrue: [ nil] ifFalse: [self tempAt: (self tempNames indexOf: aName)] and previously it was: tempNamed: aName ^self tempAt: (self tempNames indexOf: aName) ideas? -- Mariano http://marianopeck.wordpress.com

2 7

[Pharo-project] [update 2.0] #20037
by Marcus Denker May 2, 2012

May 2, 2012

20037 ----- Issue 5763: ProtoObject>>#~~ cleanup http://code.google.com/p/pharo/issues/detail?id=5763 Issue 5743: Cannot load editions of class side methods http://code.google.com/p/pharo/issues/detail?id=5743 Issue 2063: NumberTest http://code.google.com/p/pharo/issues/detail?id=2063 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Nautilus shows different code than rest of system
by Sean P. DeNigris May 2, 2012

May 2, 2012

I know someone mentioned this before, but I can't find the thread. I accepted method code in Nautilus. The little orange triangle disappeared, the new code even showed when I navigated away and came back to the method. But the system was still using the old version of the method, as proved by both failing tests, and that the old code was shown in other tools, like the implementors. I don't know how to reproduce it, but it's a really nasty bug!! Pharo1.4 Latest update: #14439 Nautilus installed via: Gofer it url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (Smalltalk at: #ConfigurationOfNautilus) perform: #loadRelease Sean p.s. I tried to piece the details together as accurately as possible, but I was playing with this image for a while before I figured out what was going on, so some details (e.g. how Nautilus was installed may not be 100%) -- View this message in context: http://forum.world.st/Nautilus-shows-different-code-than-rest-of-system-tp4… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] Nautilus question
by Francisco Garau May 2, 2012

May 2, 2012

It is showing the class side methods in bold. Is that intentional? Can we change it to something else? Blue, maybe -- but not bold! Is hard to read... - Francisco

4 10

[Pharo-project] Method Wrappers and the Debugger
by Sean P. DeNigris May 1, 2012

May 1, 2012

I'm writing a test double library similar to Ruby's rspec. The first signs of life can be downloaded via: Gofer new squeaksource: 'BDDExtensions'; package: 'Mock'; load. One of the features is to partially stub a class, so one could have e.g. DateAndTime>>#now return a canned value. It's easy enough to implement, but the wheels fall off in the debugger, where the VM quits and leaves no log on the last line of the following snippet. In a workspace, I just get a DNU, described in the comment: startTime := DateAndTime now. DateAndTime stub: #now andReturn: startTime. "DoIt this last line... works great. Debug this last line... DateAndTime class(Object)>>doesNotUnderstand: 224@116. It originally ran into Object>>at: error not indexable until I implemented at: and forwarded it to the original CompiledMethod" DateAndTime now. The ObjectAsMethodWrapper approach has a similar limitation: wrapper := ObjectAsMethodWrapper installOn: DateAndTime class selector: #now. "Debugging this line leads to 'Error: Instances of ObjectAsMethodWrapper are not indexable'" DateAndTime now. I'm going to take a look at the other MethodWrapper implementation, which I think creates CompiledMethods, so maybe that will fare better... Any other ideas? Thanks. Sean -- View this message in context: http://forum.world.st/Method-Wrappers-and-the-Debugger-tp4601773.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 1

Re: [Pharo-project] MethodWrappers
by Marcus Denker May 1, 2012

May 1, 2012

On Sep 21, 2011, at 12:59 PM, Frank Shearar wrote: > On 21 September 2011 11:48, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi Eliot, >> >> at [1] you mentioned a port of MethodWrappers to Squeak 4.2. >> Is there also a port for Pharo available or do you plan to >> port it? >> >> For those who dont know about MethodWrappers: look at [2] > > And if you're wondering why on Earth you'd want them, take a look at > SUnit's TestCoverage class for a use case. > But that is working in Pharo already, isn't it? Using the MethodWrapper version that is based on Object-As-Methods, as far as I know. Marcus -- Marcus Denker -- http://marcusdenker.de

3 2