- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] prebuilt 1.1 #11035
by Marcus Denker Nov. 8, 2009

Nov. 8, 2009

http://gforge.inria.fr/frs/download.php/24734/PharoCore-1.1-11035-alpha.zip

6 15

[Pharo-project] Fwd: [update 1.1] #11036
by StÃ©phane Ducasse Nov. 8, 2009

Nov. 8, 2009

11036 ----- - Issue 480: [Pending Etoy Cleaning] Object>>objectRepresented - SplitJoin fixed - Issue 487: [Pending Etoy Cleaning] Morph>>assureExternalName - Issue 497: [Pending Etoy Cleaning] Morph>>holdsSeparateDataForEachInstance - Issue 498: [Pending Etoy Cleaning] Morph>>playSoundNamed: soundName - Issue 1424: Comparing a MethodProperties analogousCodeTo: an AdditionalMethodState is broken - Issue 1422: remove #playfieldOptionsMenu\ - Issue 1416: Trait isSelfEvaluating Stef (thanks nicolas and marcus).

1 0

Re: [Pharo-project] How to access classVariable access with the browser
by Dale Henrichs Nov. 8, 2009

Nov. 8, 2009

3 4

[Pharo-project] Fwd: nice bug with regex
by StÃ©phane Ducasse Nov. 8, 2009

Nov. 8, 2009

> l := '1Ã¨re partie\nmilieu\nfin'. > '.*' asRegex matchesIn l. -> infinite and freezing loop. Stef

6 11

[Pharo-project] lastKeystroke: ???
by StÃ©phane Ducasse Nov. 8, 2009

Nov. 8, 2009

Hi guys apparently typing a character on the world -> DNU lastKeystroke: from PasteUpMorph is not there. Apparently the senders was integrated by me on 26 of October but I could not find its trace. So does anybody know from where this bug is coming? Stef

3 6

[Pharo-project] invalid sources for unregistered CompiledMethod
by Nicolas Cellier Nov. 8, 2009

Nov. 8, 2009

Most CompiledMethod are registered in a methodDictionary. But some are not. (CompiledMethod allInstances reject: [:e | e methodClass ~~ nil and: [e selector ~~ nil and: [e == (e methodClass methodDictionary at: e selector ifAbsent: [nil])]]]) size This is often because a BlockClosure has been registered somewhere in a registry (a ServiceRegistry for example). The objects pointers chain is something like: a SeviceRegistry -> a ServiceAction -> a BlockClosure -> a MethodContext -> a CompiledMethod... Another source of MethodContext instances is a concurrent Process running in the image. If ever recompiled, a new instance of the CompiledMethod is installed in the methodDictionary. But the old CompiledMethod is still there, being pointed to by above chains. The old CompiledMethod has a source code pointer pointing to sourceCode somewhere in the change Log, and so far it's fine. But what if you compress the change log ? The registered CompiledMethod all get a valid new pointer to the new source location. But the unregistered ones retain their old pointer now pointing randomly in the change file. This is bad. (CompiledMethod allInstances select: [:e | e selector = #id:text:button:description:action: and: [(e methodClass methodDictionary at: e selector ifAbsent: [nil]) ~~ e]]) anyOne getSource Now if you try to decompile the method, either there is an Error like here, or unfortunately the random sourceCode is valid a valid chunk of Smalltalk and you open the door to potentially strange things... It could be misleading if you try to understand what the hell this SeviceAction could be doing. If you try to decompile the BlockClosure, and getSource does not point to valid code, it doesn't work, you get nil... This is another bug, because #decompile should revert to homeMethod decompile decompileString... I propose that #condenseChanges and the like, anihilate source code pointers of unregistered CompiledMethod. This should solve the issue. What do you think ?

9 14

Re: [Pharo-project] Seaside and SUnit
by Dale Henrichs Nov. 7, 2009

Nov. 7, 2009

Bill, I would use R1.5 with Seaside 2.8 ... I use a version of that package with GemStone with good results. R2.9 should be used with Seaside3.0 ... I haven't ported R2.9 to GemStone yet, so I can't say how it works with the most recent Seaside3.0. Here's a link to the 2.9 announcement: http://lists.squeakfoundation.org/pipermail/seaside/2009-May/020739.html The tutorial link is a good link to follow for info on using Seaside Testing. If I'm not mistaken, the latest version of R2.9 (and r1.5 for that matter) predates the real block closure work for Pharo, so there's an outside chance that a little bit of work may be needed to get it working on Pharo... Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Dale, | | I had lots of luck finding links - all of it bad :) For fun, try some | searches on SqueakSource. Seaside results are huge; Seaside Shaffer; | Seaside testing does work, though it misses Albatross. Also, try | following seaside.st (Community|extensions) to the the Shaffer | framework. | | You raise an interesting question: with the changes in Seaside, which | is the correct version of SeasideTesting? | | Bill | | | | -----Original Message----- | From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale | Henrichs | Sent: Saturday, November 07, 2009 3:49 PM | To: Pharo-project(a)lists.gforge.inria.fr | Cc: Pharo-project(a)lists.gforge.inria.fr | Subject: Re: [Pharo-project] Seaside and SUnit | | Bill, | | Don't what link you followed but, Seaside Testing is at (works for | me:): | http://www.squeaksource.com/SeasideTesting.html | | There's a recent update (June of this year) to the framework for | Seaside3.0 (Seaside 2.9 at the time)... | | Seems you've been having bad luck finding info with google(?)... | | Dale | ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | | | Stef, | | | | Do you have a preference among them? If I am reading correctly, | | Shaffer's framework simulates the browser; Albatross uses JavaScript | | | to control a browser external to Pharo. I can see advantages to | both | | approaches. | | | | There is a lot of link rot on these frameworks. I can't find | | Shaffer's code anywhere; everything seems to ultimately point to | | SqueakMap, and the page just gives an error. His website also has a | | | dead link to a tutorial of yours. The pre-installed Albatross image | | | linked from SqueakSource leads to a corrupt file. | | | | Lunch calls, then I will try to get the pieces of Albatross. | | | | Bill | | | | | | | | -----Original Message----- | | From: pharo-project-bounces(a)lists.gforge.inria.fr | | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of | | StÃ©phane Ducasse | | Sent: Saturday, November 07, 2009 3:27 AM | | To: Pharo-project(a)lists.gforge.inria.fr | | Subject: Re: [Pharo-project] Seaside and SUnit | | | | you have two testing frameworks | | albratross | | and david shaffer testing framework | | | | You also have selenium that people use to test seaside app. | | | | Stef | | | | On Nov 7, 2009, at 1:04 AM, Schwab,Wilhelm K wrote: | | | | > Stef, | | > | | > Is albatross the right place to look for help? | | > | | > Bill | | > | | > | | > _______________________________________________ | | > Pharo-project mailing list | | > Pharo-project(a)lists.gforge.inria.fr | | > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | | | | | _______________________________________________ | | Pharo-project mailing list | | Pharo-project(a)lists.gforge.inria.fr | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | | | _______________________________________________ | | Pharo-project mailing list | | Pharo-project(a)lists.gforge.inria.fr | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Seaside and SUnit
by Schwab,Wilhelm K Nov. 7, 2009

Nov. 7, 2009

Stef, Is albatross the right place to look for help? Bill

3 5

Nov. 7, 2009

Hi all I'm trying to fix the failing tests of Nile and for example I do not know how to get this socket working. Does it work with you? testNext " this method seems to not work correctly ( or I have not understood how to yuse it). Try to run the test and you will see that the 'inObjects' instance variable is never fill in" socket1 listenOn: 8080. socket2 connectTo: NetNameResolver localHostAddress port: 8080. socket2 sendData: 'hello'. stream processIO. self assert: stream next = 'hello' Stef

1 1

Nov. 7, 2009

11035 ----- - Removing part of Project

1 0