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

Re: [Pharo-project] Issue 670: Should clean Morph menu

by Carla F. Griggio

Well, I haven't tried all those actions, but if it helps in any way, the ones I usually use are: grab delete copy text submorphs inspect show actions debug-> inspect morph inspect model browse morph class browse model class I don't see what the layout options do. I don't know much about layouts, so maybe this doesn't make sense, but... shouldn't the options for table layout be available only if the morph I'm dealing with has a table layout? On Tue, May 25, 2010 at 5:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > **EXCELLENT** > truly excellent > Yes we try to sort that and get some cleaning. > > > grab > > copy to paste buffer > > collapse > > delete > > copy text > > go behind > > add halo > > duplicate > > embed into-> > > PasteUpMorph > > SystemWindow > > resize > > change color... > > drop shadow-> > > show shadow > > shadow color... > > shadow offset... > > layout-> > > no layout > > proportional layout > > table layout > > change layout inset... > > child layout-> > > disable layout in tables > > horizontal resizing-> > > rigid > > shrink wrap > > space fill > > vertical resizing-> > > rigid > > shrink wrap > > space fill > > table layout-> > > reverse table cells > > clip to cell size > > rubber band cells > > change cell inset... > > change min cell size... > > change max cell size... > > list direction-> > > ... > > wrap direction-> > > ... > > cell positioning-> > > ... > > list centering-> > > ... > > wrap centering-> > > ... > > list spacing-> > > ... > > cell spacing-> > > ... > > provide clipping > > submorphs > ?? > > > inspect > > explore > > > browse hierarchy > ?? > > > save morph in file > > attach to resource > ?? > > > show actions > > debug-> > > inspect morph > > inspect owner chain > > inspect model > > explore morph > > browse morph class > > browse model class > > explore view hierarchy > > call #tempCommand > ?? > > define #tempCommand > ?? > > > open editing > > edit label... > > > > Cheers, > > Guille > > _______________________________________________ > > 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 >

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by StÃ©phane Ducasse

not really :) we prefer to keep it but that the user cannot use it by accident. Stef On May 25, 2010, at 11:07 PM, Guillermo Polito wrote: > Should that method be deprecated in the current Dev Image so no one makes a mistake? I don't know how the current "branches" are mantained to allow something like that... :/ > > 2010/5/25 Carla F. Griggio <carla.griggio(a)gmail.com> > :O > So I guess that's why it actually didn't update anything... :P > > > On Tue, May 25, 2010 at 5:15 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > The reason why we have turned it off is because updating Pharo images repeatedly caused problems (in contrast to PharoCore). People then reported issues. Unless this feature is working properly, we shouldn't enable it again. One possible cause of the problems are overrides by external packages in core code. But I think nobody has analyzed the problem in depth so far. > > Cheers, > Adrian > > > On May 25, 2010, at 21:48 , Carla F. Griggio wrote: > > > That annoyed me too. Shouldn't that option be checked by default? > > > > On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> wrote: > >> World Menu -> System -> Software Update > >> Cheers,Laurent Laffont > >> > >> http://pharocasts.blogspot.com/ > >> http://magaloma.blogspot.com/ > >> > >> > >> 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> > >> > >> > >> I'm sorry but i can't find how to update my 1.1 image. Can I update my image with this changes? Can someone enlight me? :) > >> > >> Guille, the newbie > >> > >> > >> > >> On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> 11371 > >> ----- > >> - Issue 1281: Button in TestRunner to fileout the test results. Thanks Laurent. > >> - Issue 2468: Better method trailer method creation. Part One. Thanks Igor. > >> - Issue 2406: MovieMorph should be removed from the core. Thanks Alain. > >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks Laurent > >> - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. Thanks Guillermo. > >> > >> Stef > >> _______________________________________________ > >> 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 > > > _______________________________________________ > 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

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Guillermo Polito

Should that method be deprecated in the current Dev Image so no one makes a mistake? I don't know how the current "branches" are mantained to allow something like that... :/ 2010/5/25 Carla F. Griggio <carla.griggio(a)gmail.com> > :O > So I guess that's why it actually didn't update anything... :P > > > On Tue, May 25, 2010 at 5:15 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> The reason why we have turned it off is because updating Pharo images >> repeatedly caused problems (in contrast to PharoCore). People then reported >> issues. Unless this feature is working properly, we shouldn't enable it >> again. One possible cause of the problems are overrides by external packages >> in core code. But I think nobody has analyzed the problem in depth so far. >> >> Cheers, >> Adrian >> >> >> On May 25, 2010, at 21:48 , Carla F. Griggio wrote: >> >> > That annoyed me too. Shouldn't that option be checked by default? >> > >> > On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> >> wrote: >> >> World Menu -> System -> Software Update >> >> Cheers,Laurent Laffont >> >> >> >> http://pharocasts.blogspot.com/ >> >> http://magaloma.blogspot.com/ >> >> >> >> >> >> 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> >> >> >> >> >> >> I'm sorry but i can't find how to update my 1.1 image. Can I update my >> image with this changes? Can someone enlight me? :) >> >> >> >> Guille, the newbie >> >> >> >> >> >> >> >> On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >> 11371 >> >> ----- >> >> - Issue 1281: Button in TestRunner to fileout the test results. Thanks >> Laurent. >> >> - Issue 2468: Better method trailer method creation. Part One. Thanks >> Igor. >> >> - Issue 2406: MovieMorph should be removed from the core. Thanks Alain. >> >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks >> Laurent >> >> - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. Thanks >> Guillermo. >> >> >> >> Stef >> >> _______________________________________________ >> >> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 25, 2010

Re: [Pharo-project] ConnectionQueue defect in 1.0

by StÃ©phane Ducasse

bill can you open a new bug entry. There are too much activities so that we could remember all the information passing around :) Stef On May 25, 2010, at 8:58 PM, Schwab,Wilhelm K wrote: > Hello all, > > Please see attached - CAREFULLY :) It turns out that NetworkSmokeTest will fail in your images, for want of #nextMany: and other additions I have made to streams. I will try to get them packaged for release, but if nothing else, please take a careful look at ConnectionQueue, which appears to be broken in 1.x, and hopefully fixed by the attached. > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] > Sent: Monday, May 24, 2010 6:33 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] ConnectionQueue defect in 1.0 > > Hello all, > > Attached is a simple test for networking. It passed in 1.0 RC1 and fails in 1.0 and in 1.1 beta. The problem arises in ConnectionQueue>>listenLoop. #waitForConnectionFor: returns a boolean, not the new socket, and the listen loop looks like it is expecting the socket. Any ideas? > > Billx > > <SocketWoes.1.cs>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Carla F. Griggio

:O So I guess that's why it actually didn't update anything... :P On Tue, May 25, 2010 at 5:15 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > The reason why we have turned it off is because updating Pharo images > repeatedly caused problems (in contrast to PharoCore). People then reported > issues. Unless this feature is working properly, we shouldn't enable it > again. One possible cause of the problems are overrides by external packages > in core code. But I think nobody has analyzed the problem in depth so far. > > Cheers, > Adrian > > > On May 25, 2010, at 21:48 , Carla F. Griggio wrote: > > > That annoyed me too. Shouldn't that option be checked by default? > > > > On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> > wrote: > >> World Menu -> System -> Software Update > >> Cheers,Laurent Laffont > >> > >> http://pharocasts.blogspot.com/ > >> http://magaloma.blogspot.com/ > >> > >> > >> 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> > >> > >> > >> I'm sorry but i can't find how to update my 1.1 image. Can I update my > image with this changes? Can someone enlight me? :) > >> > >> Guille, the newbie > >> > >> > >> > >> On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> 11371 > >> ----- > >> - Issue 1281: Button in TestRunner to fileout the test results. Thanks > Laurent. > >> - Issue 2468: Better method trailer method creation. Part One. Thanks > Igor. > >> - Issue 2406: MovieMorph should be removed from the core. Thanks Alain. > >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks > Laurent > >> - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. Thanks > Guillermo. > >> > >> Stef > >> _______________________________________________ > >> 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 >

May 25, 2010

Re: [Pharo-project] Issue 670: Should clean Morph menu

by StÃ©phane Ducasse

**EXCELLENT** truly excellent Yes we try to sort that and get some cleaning. > grab > copy to paste buffer > collapse > delete > copy text > go behind > add halo > duplicate > embed into-> > PasteUpMorph > SystemWindow > resize > change color... > drop shadow-> > show shadow > shadow color... > shadow offset... > layout-> > no layout > proportional layout > table layout > change layout inset... > child layout-> > disable layout in tables > horizontal resizing-> > rigid > shrink wrap > space fill > vertical resizing-> > rigid > shrink wrap > space fill > table layout-> > reverse table cells > clip to cell size > rubber band cells > change cell inset... > change min cell size... > change max cell size... > list direction-> > ... > wrap direction-> > ... > cell positioning-> > ... > list centering-> > ... > wrap centering-> > ... > list spacing-> > ... > cell spacing-> > ... > provide clipping > submorphs ?? > inspect > explore > browse hierarchy ?? > save morph in file > attach to resource ?? > show actions > debug-> > inspect morph > inspect owner chain > inspect model > explore morph > browse morph class > browse model class > explore view hierarchy > call #tempCommand ?? > define #tempCommand ?? > open editing > edit label... > > Cheers, > Guille > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] Timeline PBE 2

by StÃ©phane Ducasse

As alex says we do not have a specific target when we will have enough good chapters we will bundle them together Stef On May 25, 2010, at 6:33 PM, Torsten Bergmann wrote: > Hi, > > what is the plan for an offical PBE2 book? > Will it align with the Pharo 1.1. release? > > Thx > T. > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] Timeline PBE 2

by StÃ©phane Ducasse

Excellent please do :) Stef On May 25, 2010, at 6:37 PM, Gary Chambers wrote: > If not too late I can provide some content with respect to Polymorph... > > Regards, Gary > > ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> > To: <pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, May 25, 2010 5:33 PM > Subject: [Pharo-project] Timeline PBE 2 > > >> Hi, >> >> what is the plan for an offical PBE2 book? >> Will it align with the Pharo 1.1. release? >> >> Thx >> T. >> -- >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> >> _______________________________________________ >> 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

May 25, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by StÃ©phane Ducasse

thanks a lot denis for checking that. I should say thatI'm quite busy right now. :) Stef On May 25, 2010, at 7:05 PM, Denis Kudriashov wrote: > Ok, > > Eliot send some fix for code simulation in squeak list. > With it decompilation work good and my tests does not crach VM. But some of tests failed (they like infinit loop) > > I attach Eliot fix. > > 2010/5/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > http://code.google.com/p/pharo/issues/detail?id=2469 > > > > Stef > > > On May 23, 2010, at 4:18 PM, Denis Kudriashov wrote: > > > I found more bad cases with code simulation. And I think any manipulations with context (errors signals, simaphore, ...) not work in simulation mode. Transcript printing failed because of simaphore accessing (for thread safety) > > > > I create CodeSimulationTests (see attachement) with some tests which not work and which crash VM. > > > > Maybe this tests not correct. But I hope it helps to indicate and solve issues > > > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Thanks! > > > > Stef > > > > On May 23, 2010, at 11:13 AM, Denis Kudriashov wrote: > > > > > And If you replace Transcript code with > > > > > > self halt. > > > > > > You will see that debugging with through button does not work. Code simulation failure raised (but without VM crash) > > > > > > 2010/5/23 Denis Kudriashov <dionisiydk(a)gmail.com> > > > I has Pharo1.0 one click, Windows 7. > > > I attach class ClassWithTranscriptPrinting. > > > see class side method #debug > > > > > > > > > > > > > > > > > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > > > > Hi denis > > > > > > can you report clearly your bug > > > - image > > > - vm > > > - os > > > - scenario > > > > > > I could not compile > > > Transcript>>show:'something' > > > > > > so I do not know how you did it. > > > > > > > > > > > > On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: > > > > > > > Hello > > > > > > > > Just insert > > > > Transcript>>show:'something' > > > > at any method begin. > > > > > > > > Now debug sender of your method by debugger Through button. > > > > > > > > If no Transcript opened VM will crash! > > > > _______________________________________________ > > > > 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 > > > > <CodeSimulationTests.st>_______________________________________________ > > 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 > > <ContextPart-tryNamedPrimitiveInforwithArgs.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] [Metacello] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by StÃ©phane Ducasse

On May 25, 2010, at 6:55 PM, Dale Henrichs wrote: > StÃ©phane Ducasse wrote: >> I suggest that we avoid copy and paste. >> Why not having everything in the web pharo-book since we can - browse it on the web >> - generate latex and book for it >> - query it via help >> I do not see the point of having an ascii outdated version. We do not have the manpower for doing that. >> I'm already losing my time with svn since some people committed over my changes.... >> Stef > > I think this is a good approach ... right now I'm rethinking the metacello and glassdb wikis based on google project ... it has been convenient up to now, but I really think that having documentation that is created/editted on the web and then spawned programatically for inclusion as in image help is superior.... > > the advantage of in-image documentation is that doits can just be executed without the need for copy and paste. Also the in-image documentation will match the loaded code, while the online documentation will constantly be moving forward ... for that we should start to tag tests with proper tag this way we will have - better tests with nicer comment - help with always working and in sync code. Stef > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010