September 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Using Pharo from the command-line

by Damien Cassou

Hi Stefan, On Tue, Sep 1, 2009 at 8:38 PM, Stefan Marr<pharo(a)stefan-marr.de> wrote: > However as a thank you and for my own records, a small tutorial for > your google code wiki: I've put your text to http://code.google.com/p/pharo/wiki/CommandLine. Thank you very much -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 7, 2009

Re: [Pharo-project] The better debugger support by extending an Object protocol

by StÃ©phane Ducasse

good idea! We will add that in pharo if you open a bug item ticket. Stef On Sep 7, 2009, at 5:02 PM, Igor Stasenko wrote: > Hello guys, > i'd like to discuss with you an idea of having a specific methods in > Object class for a better and more clever behavior when debugging. > > For those of you who are using different kinds of proxies, the main > problem with them that you should override the #printOn: > or #printString methods in order to behave them similar to what > original(proxied) object should be, > but from other side, especially for debugging purposes, this incurs a > major inconvenience, because you often need to differentiate between > the real object and object proxy while debugging. Because if proxy > behaves similar to proxied object while printing, you can't really > make a difference when looking at it. > > So, i thought that a nice solution would be to extend an Object > protocol especially for debugging purposes by adding > #debugPrintOn: > method > and change the debugger to use this message, instead of #printOn: for > displaying objects in inspector panels. > > Here is the default implementation of > > Object>>debugPrintOn: aStream > ^ self printOn: aStream > > And, as you may guess, now the proxy could choose to behave > differently depending on context. > > P.S. Maybe i'm missing a point, and there are already the existing > good practices how to get around this.. if so, then please tell me. > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 7, 2009

[Pharo-project] [update] 10440

by Marcus Denker

10440 ----- Issue 897: MethodPragmaTest>>testReformat failure Issue 1164: test failure: #testClassWithInvalidClassVariablesShouldNotBeReferencedByItsSuperclass -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Sept. 7, 2009

[Pharo-project] The better debugger support by extending an Object protocol

by Igor Stasenko

Hello guys, i'd like to discuss with you an idea of having a specific methods in Object class for a better and more clever behavior when debugging. For those of you who are using different kinds of proxies, the main problem with them that you should override the #printOn: or #printString methods in order to behave them similar to what original(proxied) object should be, but from other side, especially for debugging purposes, this incurs a major inconvenience, because you often need to differentiate between the real object and object proxy while debugging. Because if proxy behaves similar to proxied object while printing, you can't really make a difference when looking at it. So, i thought that a nice solution would be to extend an Object protocol especially for debugging purposes by adding #debugPrintOn: method and change the debugger to use this message, instead of #printOn: for displaying objects in inspector panels. Here is the default implementation of Object>>debugPrintOn: aStream ^ self printOn: aStream And, as you may guess, now the proxy could choose to behave differently depending on context. P.S. Maybe i'm missing a point, and there are already the existing good practices how to get around this.. if so, then please tell me. -- Best regards, Igor Stasenko AKA sig.

Sept. 7, 2009

Re: [Pharo-project] problem with running Pharo under Solaris 10 9/05

by StÃ©phane Ducasse

first you should try squeak to run on solaris because there was a release on the new squeak vm. Then solaris this is 10 years I do not touch one :) Stef On Sep 7, 2009, at 3:58 PM, ivaylo.ganchev(a)univ-paris8.fr wrote: > Hello. > > I can't manage to run the virtual machine under solaris 10. I have > permanently the following output: > > -bash: ./squeak: Invalid argument > > Here is the output when I try to run the image with the vm of squeak: > > iconv_open: Invalid argument > This interpreter (vers. 6502) cannot read image file (vers. > 1746468864). > Press CR to quit... > > Could someone provide me with a solution or with instructions to > compile a > vm for Solaris 10? The makefile is somewhat obscure with plenty of > includes at /home/bryce/squeak/exupery without knowing whatś in > there. > > Help would be much appreciated. > > Thanks in advance, > Ivaylo > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 7, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by StÃ©phane Ducasse

On Sep 7, 2009, at 2:37 PM, nullPointer wrote: > > > >> What do you mean? >> That you use Announcements? > > I use #triggerEvent: mechanism, but hided. I dont know of > Announcements ; > what is the difference? with announcement you get an object around and not just a symbol. For the future use announcement since it is the new standard for notification in Smalltalk > > Basically the control when want launch a event (for example the > click) call > the message #raiseOnClick:args: > where the first parameter is the sender of event, and the second > parameter > is the click event.That is always works of that way in the widgets > events. > > Regards > -- > View this message in context: http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3597137.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 7, 2009

[Pharo-project] problem with running Pharo under Solaris 10 9/05

by ivaylo.ganchev＠univ-paris8.fr

Hello. I can't manage to run the virtual machine under solaris 10. I have permanently the following output: -bash: ./squeak: Invalid argument Here is the output when I try to run the image with the vm of squeak: iconv_open: Invalid argument This interpreter (vers. 6502) cannot read image file (vers. 1746468864). Press CR to quit... Could someone provide me with a solution or with instructions to compile a vm for Solaris 10? The makefile is somewhat obscure with plenty of includes at /home/bryce/squeak/exupery without knowing whatś in there. Help would be much appreciated. Thanks in advance, Ivaylo

Sept. 7, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by nullPointer

>What do you mean? >That you use Announcements? I use #triggerEvent: mechanism, but hided. I dont know of Announcements ; what is the difference? Basically the control when want launch a event (for example the click) call the message #raiseOnClick:args: where the first parameter is the sender of event, and the second parameter is the click event.That is always works of that way in the widgets events. Regards -- View this message in context: http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3597137.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 7, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by Gary Chambers

Better off doing UITheme builder alert: 'a message' title: 'Alert!'. Regards, Gary ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Monday, September 07, 2009 12:45 PM Subject: [Pharo-project] CLFramework-UIBuilder >i published the CLFramework package Nice! First bug report: In CLBuilderMainForm>>createNewView you send #alert:text:title: to the current UI theme but this message is not in the latest core image. Bye Torsten -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 7, 2009

[Pharo-project] CLFramework-UIBuilder

by Torsten Bergmann

>i published the CLFramework package Nice! First bug report: In CLBuilderMainForm>>createNewView you send #alert:text:title: to the current UI theme but this message is not in the latest core image. Bye Torsten -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

Sept. 7, 2009