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

[Pharo-project] [update 1.1] #11398

by Marcus Denker

11398 ----- Issue 2540: SmalltalkImage>>saveImageSegments still needed Issue 2538: [ENH] Let pharo be immune to line ending conventions Issue 761: Restarting a BlockClosuer in Debugger is broken -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

Re: [Pharo-project] Preferences

by Alain Plantec

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 > >

June 12, 2010

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

by Johan Brichau

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

June 12, 2010

[Pharo-project] PointerFinder & PointerExplorer

by Johan Brichau

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

June 12, 2010

[Pharo-project] Preferences

by Laval Jannik

Hi all, I want to use Preferences made by Alain. Is there a tutorial somewhere ? Cheers, --- Jannik Laval

June 12, 2010

Re: [Pharo-project] standardWindowExtent

by StÃ©phane Ducasse

no problem :) On Jun 12, 2010, at 1:23 AM, Yanni Chiu wrote: > StÃ©phane Ducasse wrote: >>> Is the intended behaviour better realized using #max: ? >> I think that this is true that now I have a 30 inches screen and that may be the realEstateAgent could be subclassed into RealEstateAgentForLargeScreen/ RealEstateAgentForSmallScreen but somebody has to do it. > > Sorry, I wasn't clear enough. I thought this was a bug - it should be a call to #max:, not #min:. But, after looking at the code some more, and experimenting with #max: vs. #min:, and changing StandardSize (experiment done on a laptop screen), I can't figure out what is best. So I guess leave it at #min: is the thing to do. > > > _______________________________________________ > 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

Re: [Pharo-project] standardWindowExtent

by Yanni Chiu

StÃ©phane Ducasse wrote: >> Is the intended behaviour better realized using #max: ? > > I think that this is true that now I have a 30 inches screen and that may be the realEstateAgent could be subclassed into > RealEstateAgentForLargeScreen/ RealEstateAgentForSmallScreen but somebody has to do it. Sorry, I wasn't clear enough. I thought this was a bug - it should be a call to #max:, not #min:. But, after looking at the code some more, and experimenting with #max: vs. #min:, and changing StandardSize (experiment done on a laptop screen), I can't figure out what is best. So I guess leave it at #min: is the thing to do.

June 11, 2010

Re: [Pharo-project] Let pharo be immune to line ending conventions

by StÃ©phane Ducasse

Thanks for let us know. Stef On Jun 11, 2010, at 11:18 PM, Nicolas Cellier wrote: > This work started in Squeak4.1/Pharo1.1 but is not finished yet. > I just published a few changes in Squeak to this aim. > See http://code.google.com/p/pharo/issues/detail?id=2538 > > Cheers > > Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2010

Re: [Pharo-project] Why Morph>>duplicate method changed in Pharo 1.1

by StÃ©phane Ducasse

thanks for testing. Stef On Jun 11, 2010, at 12:48 AM, Henrik Sperre Johansen wrote: > On 11.06.2010 00:26, Mariano Martinez Peck wrote: >> Thanks! >> >> Open a bug ticket ;) >> >> 2010/6/10 Denis Kudriashov <dionisiydk(a)gmail.com> >> Why Morph>>duplicate method changed in Pharo 1.1? >> >> Now halo button "duplicate" (at right top corner) does not work. > Seems the wrong branch was removed when cleaning up conditional player-dependent actions. > > Made issue 2530, and submitted a fixed version. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2010

Re: [Pharo-project] standardWindowExtent

by StÃ©phane Ducasse

> In RealEstateAgent>>standardWindowExtent, there is a line: > > allowedArea extent - (grid * (maxLevel + 1 * 2) + (grid // 2)) > min: StandardSize > > I changed the #min: to a #max:, and now I get a SystemBrowser that I don't have to resize every time, to make it bigger. The old solution I used in PharoCore-1.0 was to set Preferences>>bigDisplay on, then adjust the factor for scaling the initialExtent. But Preferences is gone from Pharo-1.1. the removal of the preference was just part of a major cleanup. now defining a setting could be a solution. > Is the intended behaviour better realized using #max: ? I think that this is true that now I have a 30 inches screen and that may be the realEstateAgent could be subclassed into RealEstateAgentForLargeScreen/ RealEstateAgentForSmallScreen but somebody has to do it. Stef

June 11, 2010