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

[Pharo-project] SeasideXUL demo

by Pavel Krivanek

Hi, I created a short demonstration video with SeasideXUL http://www.youtube.com/watch?v=pkfSh4pAbdM Cheers, -- Pavel

Dec. 22, 2009

[Pharo-project] pharo headless on windows, one problem and one question

by Esteban Lorenzano

Hi, I'm trying to run an application on windows (aggggg), which is a seaside application, but I'm running it as a "desktop application", using xulrunner. This is a migration from an application who was already running, but on squeak (i'm slowly migrating all my squeak applications to pharo, he). I have an "Application executer class", called CDIRunner, who understands #startUp: method. This method is properly registered by doing Smalltalk addToStartupList: CDIRunner. This is the problem: if I run @start Pharo.exe -headless the #startUp: method is not executed! (if I run Pharo in usual way, the method is executed normally). And the question: I would like to hide the pharo try icon... is this possible without recompile the vm? Thanks, Esteban

Dec. 22, 2009

Re: [Pharo-project] SUnit

by Julian Fitzell

On Tue, Dec 22, 2009 at 2:17 PM, Martin McClure <martin(a)hand2mouse.com> wrote: > But if > there can be "one true SUnit" for all Smalltalk, that seems like a > better answer. Agreed. Julian

Dec. 22, 2009

Re: [Pharo-project] SUnit

by Martin McClure

Julian Fitzell wrote: > > It would be really nice to have *one* SUnit that worked everywhere > with only minor platform-dependent pieces (like Seaside) where > necessary. This would be much more sustainable than the forked > situation we have currently, but that's a whole different battle. Yes. > Although now I've said it, why not just start from scratch? There's > not a lot of code there... implement something that works the way you > want, build it using Grease/Slime so we can port it easily to > everywhere else, and that's something Seaside could use (assuming it > was compellingly better). And suddenly we'd have a test framework that > *did* run everywhere with a common code base. Some months ago Niall Ross took over maintainership of SUnit. IIRC he had the blessing of the previous maintainers, who hadn't been able to actually do much with it in recent years. At ESUG in Brest, Niall was actively working on SUnit and talking to folks from various Smalltalk implementations to try to get stuff into the next "official" release that would make everyone happy. So there is work going on to attempt to make the situation better. I'd think you'd want to at least discuss this with Niall and look at what he's done before starting over from scratch. If what's there doesn't meet Pharo's needs, starting from scratch might be appropriate. But if there can be "one true SUnit" for all Smalltalk, that seems like a better answer. Regards, -Martin

Dec. 22, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Alexandre Bergel

Looks good! Alexandre On 22 Dec 2009, at 21:35, Frederic Pluquet wrote: > Good idea. Too easy finally :) Done in the last version (see the > screenshot)! > > For Form and Color instances. Parametrizable by blocks or method > overridding (#niIcon or #niIconName) :) > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > 2009/12/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Fred > > this is cool !! > > Now I was thinking if you could not reuse this block and use it to > add the visual before the [1] : Form... > as int he explorer > > Stef > > > > > > > > Form allInstances > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > <Forms with > Icons !.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 22, 2009

Re: [Pharo-project] SUnit forked, gofer it

by Yanni Chiu

Adrian Kuhn wrote: > A first fork is available > > Gofer it > squeaksource: 'akuhn'; > package: 'SUnit'; > package: 'SUnitGUI'; > load Is it too late to call it SUnit2, SUnit3, whatever? When I see SUnit, I expect only the "standard" SUnit (i.e. TestCase, TestSuite, test resources, and various #assert: methods). Am I the only one that has a problem with calling this new direction "SUnit", without qualifying it with some version. I see a parallel with JUnit 3 vs 4 in the Java world. JUnit4 uses annotations to indicate test cases - no "test" prefix needed. When these test cases are run against JUnit3, nothing fails (and it appears to have passed) - but the tests have not been run at all, since without the "test" prefix, they're not recognized as test cases. Maybe nothing similar will happen with the new SUnit. What happens is that people start writing test cases assuming the newer version. Then at some point there's a conflict, and you either have to re-write your old or your new test cases. Maybe it's okay to be forced to update your old test cases, but it would be good know which version of the "SUnit API" is available or required. -- Yanni Chiu

Dec. 22, 2009

Re: [Pharo-project] Issue 1659: WACallSuperImplementationRule>>checkClass: on a SmalllintContext ObjectTracer causes walkback

by Lukas Renggli

Ahh, I found out that this is in the WebDev image, not in PharoCore. Fixed in the latest Seaside code. 2009/12/22 Lukas Renggli <renggli(a)gmail.com>: > I cannot reproduce that problem. > > That would be a bug in Seaside anyway (it is a lint rule of Seaside). > > Lukas > > 2009/12/22 Stan Shepherd <stan.shepherd414(a)gmail.com>: >> >> VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: >> #10074] >> Image: PharoCore1.0rc1 [Latest update: #10500] >> >> SystemBrowser default = Â Browser >> Steps to reproduce: >> 1.From Browser, right click any class >> 2.refactor > code critics >> 3.opens Code Critics: All checks on Smalltalk >> 4. walkback occurs checking ObjectTracer - no superclass >> -- >> View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on… >> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 22, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Frederic Pluquet

Good idea. Too easy finally :) Done in the last version (see the screenshot)! For Form and Color instances. Parametrizable by blocks or method overridding (#niIcon or #niIconName) :) FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet 2009/12/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Fred > > this is cool !! > > Now I was thinking if you could not reuse this block and use it to add the > visual before the [1] : Form... > as int he explorer > > Stef > > > > > > > > Form allInstances > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 22, 2009

Re: [Pharo-project] SUnit forked, gofer it

by StÃ©phane Ducasse

Ok so why don't you use a better name SingleTestResult because Token does not talk to me. On Dec 22, 2009, at 8:23 PM, Adrian Kuhn wrote: > StÃ©phane Ducasse <stephane.ducasse@...> writes: > >> What is a TestToken? > > TestToken store the result of a single test case, whereas TestResult stores the > result of an entire test suite. The life time of tokens may possible be > persistent. While the life time of TestCase instances is strictly limited to > the duration of one test run. > > --AA > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 22, 2009

Re: [Pharo-project] SUnit forked, gofer it

by Adrian Kuhn

StÃ©phane Ducasse <stephane.ducasse@...> writes: > What is a TestToken? TestToken store the result of a single test case, whereas TestResult stores the result of an entire test suite. The life time of tokens may possible be persistent. While the life time of TestCase instances is strictly limited to the duration of one test run. --AA

Dec. 22, 2009