June 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] OB Debugger

by Lukas Renggli

Hi Johan, > We found you have implementation of an OB-Debugger in your omnibrowser repo. Yes, in the package OB-Tools there are functional implementations of debugger, filesystem browser, object browser (inspector), process browser, workspace, and transcript. > Could you comment to us what is the state of that code? I haven't looked into the code lately, so it might be slightly out of sync with the current OmniBrowser code. The code was functional and provided about 90% of the functionality the original Smalltalk-80 tools provided. At the time the tools were built they were notably slower than the original tools. I doubt that that this is still a big problem, because the meta-model has seen various major optimizations. The worst thing about the code is that there are no tests. There is no excuse for that. This is plain bad. > Is there a newer version? Not that I know. Dale from GemStone had been working on the tools for a while, but I think all his changes are in my repository. > Does it makes sense for us to pick up the project and see what we can do with it? I think that would be beneficial. Imagine we could extend our debuggers and inspectors the same way as the browsers. Lukas -- Lukas Renggli www.lukas-renggli.ch

June 12, 2010

[Pharo-project] [ANN 1.2] first 1.2 pre-built core image 12003

by Marcus Denker

https://gforge.inria.fr/frs/download.php/27158/PharoCore-1.2-12003-UNSTABLE… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

Re: [Pharo-project] [ANN 1.1] pre-built CoreRC1 1400

by Marcus Denker

On Jun 12, 2010, at 1:18 PM, Marcus Denker wrote: > > > https://gforge.inria.fr/frs/download.php/27156/PharoCore-1.1-11400-rc1.zip ... due to the workings of the update stream, we had to re-issue this as rc2: https://gforge.inria.fr/frs/download.php/27157/PharoCore-1.1-11400-rc2.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

[Pharo-project] [ANN 1.1] pre-built CoreRC1 1400

by Marcus Denker

https://gforge.inria.fr/frs/download.php/27156/PharoCore-1.1-11400-rc1.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

[Pharo-project] [update 1.1] #11400

by Marcus Denker

11400 ----- Issue 2548: NewTestMorphTests>>#testAcceptContents fails Issue 2547: FilesStreamTest>>testPositionPastEndIsAtEnd Issue 2506: Browsing hierarchy of Traits crashes OB Issues left tagged 1.1: Issue 2448: display of WideStrings with StrikeFonts Issue 2546: Tests failing: BlockClosureTest and MessageTallyTest Issue 1628: Error: There is no free space in this set!' -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

Re: [Pharo-project] Preferences

by Laval Jannik

Thank you Alain, I will try it this afternoon. Cheers, Jannik On Jun 12, 2010, at 10:46 , Alain Plantec wrote: > Le 12/06/2010 10:18, Laval Jannik a Ã©crit : >> Hi all, >> >> I want to use Preferences made by Alain. >> Is there a tutorial somewhere ? >> > We are currently writing it. > you can find a small help here: http://book.pharo-project.org/book/TipsAndTricks/DeclaringSetting > Cheers > Alain > >> Cheers, >> --- >> Jannik Laval >> >> >> _______________________________________________ >> 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 --- Jannik Laval

June 12, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Marcus Denker

On Wed, Jun 9, 2010 at 1:34 PM, Niko Schwarz <niko.schwarz(a)googlemail.com> wrote: > On Wed, Jun 9, 2010 at 9:29 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> Also, people who know there is something that really needs to be fixed for a 1.1 release should speak up now. > > I think http://code.google.com/p/pharo/issues/detail?id=2469 should be > integrated before 1.1. I remember how much of a pain the simulator > behavior was when messing with SUnit. Toon's patch might be the > foundation for cleaner SUnit code. > I added it... I wonder if that was a good idea. Now we have failing tests: http://code.google.com/p/pharo/issues/detail?id=2546 Marcus -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

June 12, 2010

[Pharo-project] 1.1: Current Issues

by Marcus Denker

http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.1 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

Re: [Pharo-project] in issue 2537: OB System Browser fix

by Lukas Renggli

I think these queries were originally proposed in a blog post and eventually they got added to OB. Unfortunately I can find the post anymore. I've never used or enabled the mercury panel myself. It was suggested to be removed from the codebase as only very few people find it useful or know how to use it. Since there are quite some test cases for the mercury panel I was hesitating to do so up to now. I recently removed the protocol browser. I never used it, it was untested, violated model and view separation, and was badly broken. Lukas On 12 June 2010 10:36, Johan Brichau <johan.brichau(a)uclouvain.be> wrote: > thanks Lukas > > just for us to know: where can we find info on those kinds of queries? (we were not aware about them) > > On 11 Jun 2010, at 19:15, Lukas Renggli wrote: > >> The proposed change unfortunately breaks other queries (string search >> and parse tree search). >> >> I committed a slightly different solution: >> >> http://code.google.com/p/pharo/issues/detail?id=2537 >> >> Lukas >> >> On 11 June 2010 18:18, Johan Brichau <johan.brichau(a)uclouvain.be> wrote: >>> A simple fix to an annoying problem ;-) >>> >>> The OB System Browser's search bar has the annoying property that an expansion of keyworded messages inserts whitespaces between the keywords. >>> That eventually means the search will not find the keyworded message if you do not remove the whitespace before hitting enter. >>> This changeset fixes it >>> >>> Lukas: we can also send the mcz, but where? >>> >>> ---------------------------- >>> Johan Brichau >>> johan.brichau(a)uclouvain.be >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > ---------------------------- > Johan Brichau > johan.brichau(a)uclouvain.be > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

June 12, 2010

Re: [Pharo-project] PointerFinder & PointerExplorer

by StÃ©phane Ducasse

thanks. Stef On Jun 12, 2010, at 10:33 AM, Johan Brichau wrote: > Issue #156 (http://code.google.com/p/pharo/issues/detail?id=156) states that PointerFinder and PointerExplorer both have issues leaving out some pointers. > > Andy and I have been looking at the implementation of PointerFinder and PointerExplorer in Pharo1.1 to fix this. > > We came to the decision to throw out PointerFinder, replace its uses to uses of PointerExplorer and move PointerFinder's #pointersTo* class methods to ProtoObject because: > - PointerFinder's (instance) behavior seems to be really old code that was not using the pointsTo: (primitive) method, while its #pointersTo* class methods were using the pointsTo: (primitive) method > - It also seems the instance behavior of PointerFinder was wrong (it did not give us all pointers *at all*) > - PointerExplorer offers the same functionality using a tree view and eventually used the #pointersTo* class methods of PointerFinder... > > The fix is in SLICE-PointerFinderRemove-AndyKellens.1 and should be for 1.2 > > Maybe anyone has another opinion? > > ---------------------------- > Johan Brichau > johan.brichau(a)uclouvain.be > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2010