- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by Alexandre Bergel

> I will integrate it. > I was thinking that WindowOpened is not that english but it has the advantage that all the events of a certain kinds are grouped. Yes, this is why I first used SUAnnouncement and SUTestBegin... Alexandre > > Stef > > > On Aug 2, 2010, at 12:08 PM, Alexandre Bergel wrote: > >> hi! >> >> In PharoInbox there is: SLICE-Issue-2721-AnnouncementsForSUnit-Alexandre_Bergel.2 >> The comment of this slice is: >> -=-=-=-=-=-=-=-=-=-=-=-= >> Renamed the event classes into: >> TestCaseAnnouncement >> -- TestCaseStarted >> -- TestCaseEnded >> >> Event are also emitted in TestResult>>runCase: like this, the result of the test execution is accessible from the event. >> (Thanks Laurent Laffon for these suggestions) >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> Cheers, >> Alexandre >> >> On 29 Jul 2010, at 22:22, laurent laffont wrote: >> >>> On Thu, Jul 29, 2010 at 7:42 PM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> On 29.07.2010 17:45, Alexandre Bergel wrote: >>> Wow ! Fast !. >>> >>> That means it should be easy now to do a lot of exciting stuff. Show tests progression, errors/failures as soon as they occur, log several things, drink cocktails, meet beautiful girls ....that's really cool. >>> I will be in winter time in 1 week time. We have to enjoy now >>> >>> Alexandre >>> Nice! >>> Maybe it's just me, or could we not add Announcement to the end of every Announcement subclass name though? >>> Like with the window announcement, I like them better as verbs describing the event, f.ex. >>> someAnnouncer on: TestStarted do: [] >>> someAnnouncer on: TestEnded send: #x to: y >>> >>> +1. I propose >>> TestCaseAnnouncement >>> -- TestCaseStarted >>> -- TestCaseEnded >>> >>> >>> Shouldn't we put announce in TestResult>>runCase: instead of TestCase>>runCase ? This way we can pass the result to the Annoucement object. >>> >>> >>> Actually, self announce: SUTestEndAnnouncement. is not in the ensure: block. So if the test fails there's no annoucement sent. >>> >>> >>> Cheers, >>> >>> Laurent >>> >>> >>> >>> Cheers, >>> Henry >>> >>> >>> _______________________________________________ >>> 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 >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

Re: [Pharo-project] List of possible actions for busy pharoers

by StÃ©phane Ducasse

Thanks alex this is cool Stef On Aug 2, 2010, at 12:33 PM, Alexandre Bergel wrote: > Hi Stef, > >> http://code.google.com/p/pharo/issues/detail?id=1767 Issue 1767: Method Finder gives UndefinedObject error on search > > SLICE-Issue-1767-FixInMethodFinder-Alexandre_Bergel.1 in the inbox > >> http://code.google.com/p/pharo/issues/detail?id=2296 Issue 2296: Point>>closeTo > > SLICE-Issue-2296-PointCloseTo-Alexandre_Bergel.1 in the inbox > > I update the google site. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 2, 2010

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by StÃ©phane Ducasse

I will integrate it. I was thinking that WindowOpened is not that english but it has the advantage that all the events of a certain kinds are grouped. Stef On Aug 2, 2010, at 12:08 PM, Alexandre Bergel wrote: > hi! > > In PharoInbox there is: SLICE-Issue-2721-AnnouncementsForSUnit-Alexandre_Bergel.2 > The comment of this slice is: > -=-=-=-=-=-=-=-=-=-=-=-= > Renamed the event classes into: > TestCaseAnnouncement > -- TestCaseStarted > -- TestCaseEnded > > Event are also emitted in TestResult>>runCase: like this, the result of the test execution is accessible from the event. > (Thanks Laurent Laffon for these suggestions) > -=-=-=-=-=-=-=-=-=-=-=-= > > Cheers, > Alexandre > > On 29 Jul 2010, at 22:22, laurent laffont wrote: > >> On Thu, Jul 29, 2010 at 7:42 PM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> On 29.07.2010 17:45, Alexandre Bergel wrote: >> Wow ! Fast !. >> >> That means it should be easy now to do a lot of exciting stuff. Show tests progression, errors/failures as soon as they occur, log several things, drink cocktails, meet beautiful girls ....that's really cool. >> I will be in winter time in 1 week time. We have to enjoy now >> >> Alexandre >> Nice! >> Maybe it's just me, or could we not add Announcement to the end of every Announcement subclass name though? >> Like with the window announcement, I like them better as verbs describing the event, f.ex. >> someAnnouncer on: TestStarted do: [] >> someAnnouncer on: TestEnded send: #x to: y >> >> +1. I propose >> TestCaseAnnouncement >> -- TestCaseStarted >> -- TestCaseEnded >> >> >> Shouldn't we put announce in TestResult>>runCase: instead of TestCase>>runCase ? This way we can pass the result to the Annoucement object. >> >> >> Actually, self announce: SUTestEndAnnouncement. is not in the ensure: block. So if the test fails there's no annoucement sent. >> >> >> Cheers, >> >> Laurent >> >> >> >> Cheers, >> Henry >> >> >> _______________________________________________ >> 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 > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 2, 2010

Re: [Pharo-project] List of possible actions for busy pharoers

by Alexandre Bergel

Hi Stef, > http://code.google.com/p/pharo/issues/detail?id=1767 Issue 1767: Method Finder gives UndefinedObject error on search SLICE-Issue-1767-FixInMethodFinder-Alexandre_Bergel.1 in the inbox > http://code.google.com/p/pharo/issues/detail?id=2296 Issue 2296: Point>>closeTo SLICE-Issue-2296-PointCloseTo-Alexandre_Bergel.1 in the inbox I update the google site. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by Alexandre Bergel

> TestResult when: TestCaseStarts do: [:event | do some stuff ]. > > TestResult when: TestCaseEnds do: [:event | do some stuff ]. Currently, the announcer is stored in TestCase. For me, it looks more intuitive to do MyTestCase announcer on: TestCaseAnnouncement do: [:ann | ... ]. than dealing with TestResult. I am okay to move the announcer in TestResult, but that's look a bit to me. Don't you feel? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by Alexandre Bergel

hi! In PharoInbox there is: SLICE-Issue-2721-AnnouncementsForSUnit-Alexandre_Bergel.2 The comment of this slice is: -=-=-=-=-=-=-=-=-=-=-=-= Renamed the event classes into: TestCaseAnnouncement -- TestCaseStarted -- TestCaseEnded Event are also emitted in TestResult>>runCase: like this, the result of the test execution is accessible from the event. (Thanks Laurent Laffon for these suggestions) -=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre On 29 Jul 2010, at 22:22, laurent laffont wrote: > On Thu, Jul 29, 2010 at 7:42 PM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > On 29.07.2010 17:45, Alexandre Bergel wrote: > Wow ! Fast !. > > That means it should be easy now to do a lot of exciting stuff. Show tests progression, errors/failures as soon as they occur, log several things, drink cocktails, meet beautiful girls ....that's really cool. > I will be in winter time in 1 week time. We have to enjoy now > > Alexandre > Nice! > Maybe it's just me, or could we not add Announcement to the end of every Announcement subclass name though? > Like with the window announcement, I like them better as verbs describing the event, f.ex. > someAnnouncer on: TestStarted do: [] > someAnnouncer on: TestEnded send: #x to: y > > +1. I propose > TestCaseAnnouncement > -- TestCaseStarted > -- TestCaseEnded > > > Shouldn't we put announce in TestResult>>runCase: instead of TestCase>>runCase ? This way we can pass the result to the Annoucement object. > > > Actually, self announce: SUTestEndAnnouncement. is not in the ensure: block. So if the test fails there's no annoucement sent. > > > Cheers, > > Laurent > > > > Cheers, > Henry > > > _______________________________________________ > 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

Re: [Pharo-project] ProgressDisplay package released

by Alexandre Bergel

Yep, a screenshot will be cool Alexandre On 2 Aug 2010, at 10:52, StÃ©phane Ducasse wrote: > Cool > > Can you tell us some of the added features? > > Stef > >> I recently released the first draft of my package ProgressDisplay to >> SqueakSource. >> It is like SystemProgressMorph et. al. but with a lot of bells and >> whistles added. >> It is not a suitable replacement for SystemProgressMorph though because it is >> too large and specific for that. SystemProgressMorph could be made a subclass >> of one of its classes though. >> >> It is designed largely to meet my specific needs but since it's MIT anyone may >> use it, steal components, or move components of it to Squeak/Pharo. >> It has a utility class category with useful classes for things like >> array permutation generation and array multiset permutation >> generation, numeric partitioning of a number, and a class RangeList >> (which I will be expanding upon later). All of these classes will be >> removed when the package meant to contain them is ready (not soon). >> There are also a number of utility methods that could be stolen or put >> into Squeak/Pharo proper. >> >> It probably has lots of bugs, so bug reports appreciated. >> Comments on its function, design, and implementation most welcome. >> Proposals for improvements or extensions will be considered but no promises. >> If you need access to make changes let me know. >> If Levente Uzonyi likes it but feels compelled to rewrite it >> completely from scratch, thats okay too. :-) >> >> ONE OF MY REASONS FOR RELEASING IT IS BECAUSE OF A >> BUG I COULD NOT FIX. >> It is supposed to be possible to turn on the ability to catch user interrupts >> but when this feature is turned on and an interrupt generated while >> the progress bar is displayed the interrupt is caught but not processed >> until the progress bar closes. :-( >> Of course the interrupt was meant to be processed immediately. >> If anyone can tell me how to fix this bug (or better still send me the >> code or add the code to the package) that would be great! >> >> Regards, >> >> Ralph Boland >> >> -- >> Quantum Theory cannot save us from the tyranny of a deterministic universe >> but it does give God something to do >> >> _______________________________________________ >> 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

Re: [Pharo-project] ProgressDisplay package released

by Serge Stinckwich

Yes sell you work ! Not everyone has time to test ;-) On Mon, Aug 2, 2010 at 3:58 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > Yep, a screenshot will be cool > > Alexandre > > > On 2 Aug 2010, at 10:52, StÃ©phane Ducasse wrote: > >> Cool >> >> Can you tell us some of the added features? >> >> Stef >> >>> I recently released the first draft of my package ProgressDisplay to >>> SqueakSource. >>> It is like SystemProgressMorph et. al. but with a lot of bells and >>> whistles added. >>> It is not a suitable replacement for SystemProgressMorph though because it is >>> too large and specific for that. SystemProgressMorph could be made a subclass >>> of one of its classes though. >>> >>> It is designed largely to meet my specific needs but since it's MIT anyone may >>> use it, steal components, or move components of it to Squeak/Pharo. >>> It has a utility class category with useful classes for things like >>> array permutation generation and array multiset permutation >>> generation, numeric partitioning of a number, and a class RangeList >>> (which I will be expanding upon later). Â All of these classes will be >>> removed when the package meant to contain them is ready (not soon). >>> There are also a number of utility methods that could be stolen or put >>> into Squeak/Pharo proper. >>> >>> It probably has lots of bugs, so bug reports appreciated. >>> Comments on its function, design, and implementation most welcome. >>> Proposals for improvements or extensions will be considered but no promises. >>> If you need access to make changes let me know. >>> If Levente Uzonyi likes it but feels compelled to rewrite it >>> completely from scratch, thats okay too. :-) >>> >>> ONE OF MY REASONS FOR RELEASING IT IS BECAUSE OF A >>> BUG I COULD NOT FIX. >>> It is supposed to be possible to turn on the ability to catch user interrupts >>> but when this feature is turned on and an interrupt generated while >>> the progress bar is displayed the interrupt is caught but not processed >>> until the progress bar closes. :-( >>> Of course the interrupt was meant to be processed immediately. >>> If anyone can tell me how to fix this bug (or better still send me the >>> code or add the code to the package) that would be great! >>> >>> Regards, >>> >>> Ralph Boland >>> >>> -- >>> Quantum Theory cannot save us from the tyranny of a deterministic universe >>> but it does give God something to do >>> >>> _______________________________________________ >>> 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 > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Aug. 2, 2010

Re: [Pharo-project] cog-based image crashes on mac

by StÃ©phane Ducasse

thanks for the explanation and code. On Aug 2, 2010, at 3:43 AM, Henrik Johansen wrote: > > On Aug 1, 2010, at 10:40 53AM, Lukas Renggli wrote: > >> The changes I submitted are the ones of Eliot adapted to work in >> Pharo. I don't understand what Henrik writes, if he has something >> better he should attach the change. >> >> Lukas > > Not better, just simpler code. > > If I'm not mistaken, if primitive 38 fails in Cog, so will primitive 60. > Primitive 38 will always fail in a non-cog vm. > The failure handling code after the ec == nil check is the same in Float>>basicAt: and Object basicAt: > > Thus, writing > Float>>basicAt: index > <primitive:38> > ^super basicAt: index > > would yield the exact same result, with the difference that you will have an extra primtive 60 failure in Cog vm's, an ec = nil check less in non-cog VM's, and no duplication of the fallback-handling code. > > The alternate code was attached, in issue 2581. > > Cheers, > Henry > >> >> On Sunday, August 1, 2010, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> lukas >>> >>> could you have a look at >>> http://code.google.com/p/pharo/issues/detail?id=2579 >>> because henrik mentioned that we missed something or could do it better. >>> >>> Stef >>> >>> >>> On Jul 26, 2010, at 1:32 PM, Lukas Renggli wrote: >>> >>>>>>> The image I got is based on the sources from 27.06.2010. >>>>>> >>>>>> You may be missing some image-side changes. The CogVM was open sourced on >>>>>> 20.06.2010. >>>>> >>>>> Actually, where should I get the complete image-side changes from? I have >>>>> those prepared by Lukas a while ago. >>>> >>>> Yeah, these are the complete ones from the repository adapted to Pharo. >>>> >>>> Maybe these same socket related crashes that randomly appear with >>>> Seaside images? >>>> >>>> nanosleep: Invalid argument >>>> Exited with exit code: 1 >>>> >>>> Lukas >>>> >>>> -- >>>> 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 >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 2, 2010

Re: [Pharo-project] ProgressDisplay package released

by StÃ©phane Ducasse

Cool Can you tell us some of the added features? Stef > I recently released the first draft of my package ProgressDisplay to > SqueakSource. > It is like SystemProgressMorph et. al. but with a lot of bells and > whistles added. > It is not a suitable replacement for SystemProgressMorph though because it is > too large and specific for that. SystemProgressMorph could be made a subclass > of one of its classes though. > > It is designed largely to meet my specific needs but since it's MIT anyone may > use it, steal components, or move components of it to Squeak/Pharo. > It has a utility class category with useful classes for things like > array permutation generation and array multiset permutation > generation, numeric partitioning of a number, and a class RangeList > (which I will be expanding upon later). All of these classes will be > removed when the package meant to contain them is ready (not soon). > There are also a number of utility methods that could be stolen or put > into Squeak/Pharo proper. > > It probably has lots of bugs, so bug reports appreciated. > Comments on its function, design, and implementation most welcome. > Proposals for improvements or extensions will be considered but no promises. > If you need access to make changes let me know. > If Levente Uzonyi likes it but feels compelled to rewrite it > completely from scratch, thats okay too. :-) > > ONE OF MY REASONS FOR RELEASING IT IS BECAUSE OF A > BUG I COULD NOT FIX. > It is supposed to be possible to turn on the ability to catch user interrupts > but when this feature is turned on and an interrupt generated while > the progress bar is displayed the interrupt is caught but not processed > until the progress bar closes. :-( > Of course the interrupt was meant to be processed immediately. > If anyone can tell me how to fix this bug (or better still send me the > code or add the code to the package) that would be great! > > Regards, > > Ralph Boland > > -- > Quantum Theory cannot save us from the tyranny of a deterministic universe > but it does give God something to do > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 2, 2010