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

Re: [Pharo-project] Aida/Web now loads and runs well on Pharo 1.1

by Janko MivÅ¡ek

Hi StÃ©phane, On 31. 07. 2010 17:38, StÃ©phane Ducasse wrote: > janko > excellent news. > Did you create and publish configurationOfSwazoo.... Aida? > Because this is the way to go :) Yep, thanks to Dale's initial effort there are Metacello packages for: ConfigurationOfSPort2 "Sport portability layer" ConfigurationOfSwazoo2 ConfigurationOfAida FYI, during syncing of Aida to Squeak/Pharo I'm just writing a "Pharo 1.1. impressions and suggestions" email, which will be released soon. I hope I can help that way the Pharo effort a bit :) Best regards Janko > > Stef > > On Jul 28, 2010, at 11:15 PM, Janko MivÅ¡ek wrote: > >> Hi guys, >> >> I just made Aida ready on new and wonderfull Pharo 1.1. and now Aida >> installs and run nicelly and even side by side with Seaside. You can >> even run both on the same Swazoo web server, which is also included. >> >> Just evulate DEVImageWorkspaces openExternalProjectWorkspace then >> evaluate loads of both Seaside and Aida, then start both, for Aida evaluate: >> >> SwazooAida demoStart >> "open http://localhost:8888 in your web browser" >> >> Best regards >> Janko >> >> >> -- >> Janko MivÅ¡ek >> AIDA/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> >> _______________________________________________ >> 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 > -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

Aug. 2, 2010

Re: [Pharo-project] Pharo 1.1 host menu os x

by Michael Roberts

Hi, i am trying to publish a fix, but I get MC error can't find HostMenus-LaurentLaffont.53. It is the ancestor of HostMenus-MarcusDenker.54 but does not seem to be in the /Pharo package. Where did it go? thanks, Mike

Aug. 2, 2010

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

by GermÃ¡n Arduino

2010/8/1 StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr>: > hi guys > > I know that some of you would like to contribute but are busy, scared ... > I spent three hours to go over the bug entries. Feel free to pick one and fix it: > So now you can easily contribute. Just do it. > > Stef > > Some easy fixes: > -------------- > for the fixes based on squeak changed, it often requires to check the code and run pharo tests. > > http://code.google.com/p/pharo/issues/detail?id=2603 Â Issue 2603 isRunningCog I worked on this issue. Added the tests to check if is running under Cog and adapted the tests to guard TestObjectsAsMethods against a Cog crash. On the page issue I attached the SLICE and the packages. But may be I did a mistake, because them were generated local (I had my package cache selected when saved it) but also saved on PharoInbox. That is ok? Is the default behaviour? Please correct me any mistake, then I can help with other issues. Cheers. GermÃ¡n.

Aug. 2, 2010

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

by Henrik Johansen

I added some comments/slices wrt. to the extent: method. Cheers, Henry On Aug 2, 2010, at 12:48 41PM, StÃ©phane Ducasse wrote: > 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 > > > _______________________________________________ > 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 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