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

Re: [Pharo-project] update to OCompletion

by Levente Uzonyi

On Mon, 2 Aug 2010, Romain Robbes wrote: > Hi All, > > I just committed: > http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz > > the changes are: > > -incorporated Lukas' smart characters algorithm (thanks Lukas!) > -removed enter to insert a completion; only tab works now. > -delayed the switch to eCompletion's completion algorithm, hence the slowdown when using the down arrow happens only after the third time pressing it (after OCompletion's all of OCompletion's menu items). Cool. Does it work in Squeak? Levente > > Cheers, > Romain > > -- > Romain Robbes > http://romain.robb.es > rrobbes(a)dcc.uchile.cl > > > _______________________________________________ > 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] Poll: missing libraries to support business

by Levente Uzonyi

On Mon, 2 Aug 2010, Michael Roberts wrote: > =Platform integration= > -multiple host windows > -deeper platform look 'n feel wxSqueak is a perfect match. Too bad it's not finished and it uses ToolBuilder. > > =Documentation= Nobody likes to write documentation. Levente > > cheers > Mike > > On Mon, Aug 2, 2010 at 8:50 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> with the experience around the XMLRPC project, ESUG wants to change strategy to help growing business at the technical >> level. So what are the key areas where you think that effort should be supported to help you making business in smalltalk? >> >> 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 >

Aug. 2, 2010

Re: [Pharo-project] update to OCompletion

by Alexandre Bergel

Excellent! Alexandre On 3 Aug 2010, at 00:38, Romain Robbes wrote: > Hi All, > > I just committed: > http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz > > the changes are: > > -incorporated Lukas' smart characters algorithm (thanks Lukas!) > -removed enter to insert a completion; only tab works now. > -delayed the switch to eCompletion's completion algorithm, hence the slowdown when using the down arrow happens only after the third time pressing it (after OCompletion's all of OCompletion's menu items). > > Cheers, > Romain > > -- > Romain Robbes > http://romain.robb.es > rrobbes(a)dcc.uchile.cl > > > _______________________________________________ > 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

[Pharo-project] update to OCompletion

by Romain Robbes

Hi All, I just committed: http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz the changes are: -incorporated Lukas' smart characters algorithm (thanks Lukas!) -removed enter to insert a completion; only tab works now. -delayed the switch to eCompletion's completion algorithm, hence the slowdown when using the down arrow happens only after the third time pressing it (after OCompletion's all of OCompletion's menu items). Cheers, Romain -- Romain Robbes http://romain.robb.es rrobbes(a)dcc.uchile.cl

Aug. 2, 2010

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

by Alexandre Bergel

> event := anAnnouncementClass isBehavior > ifTrue: [ anAnnouncementClass new ] > ifFalse: [ anAnnouncementClass ]. > > Why anAnnouncementClass would not be a class? True. I wasn't sure. SLICE-Issue-2721-AnnouncementsForSUnit-Alexandre_Bergel.3 in the inbox. I also use #asAnnouncement, as suggested by Lukas. Cheers, Alexandre > > > announce: anAnnouncementClass withResult: result > | event | > self shouldAnnounce ifFalse: [ ^ self ]. > > event := anAnnouncementClass isBehavior > ifTrue: [ anAnnouncementClass new ] > ifFalse: [ anAnnouncementClass ]. > event testCase: self. > event testSelector: testSelector. > event result: result. > self announcer announce: event. > > > > On Aug 2, 2010, at 12:47 PM, StÃ©phane Ducasse wrote: > >> 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 >> >> >> _______________________________________________ >> 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] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by Alexandre Bergel

> Then why do you have several announcers and keep them in a classVariable? An alternative solution would be to have an instance variable in the meta-class. This is what I did first. But you need to recompile the more than 500 unit tests in that case to add the iv. We can go that way. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

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

by GermÃ¡n Arduino

2010/8/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Aug 2, 2010, at 11:40 PM, GermÃ¡n Arduino wrote: > >> 2010/8/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Thanks a lot and also for the discussions (see my other notes). >>> >> >> Published. >> >>> Stef (today I fixed my cactus collection :)) >>> >> >> :S DNU > > I collect cactuses and they need my love from time to time to change pots, kill bugs.... :) > > Ahh, ok! I fly rc models (and build and repair (of course :) them) as my hobby....but now in winter, not very nice to go to the fly field. You will come to Argentina again (told me Gabriela) to Smalltalks 2010!? That's good!! Cheers. GermÃ¡n.

Aug. 2, 2010

Re: [Pharo-project] about ToolBuilder

by Esteban Lorenzano

Oh, I'm using it for Mars... but I can remove it anyway, just let me know. Cheers, Esteban On 2010-08-02 17:05:58 -0300, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> said: >> I agree that it should be removed, but this means that many tools need >> to be rewritten in plain morphic. > > do you know which ones? > Because a lot of buildwith: methods are not used in fact. > >> Lukas >> >> 2010/8/2 Richard Durr <richard.durr(a)googlemail.com>: >>> +1. >>> See Gilad's text about least common denominator in UI-widgetery >>> >>> On Fri, Jul 30, 2010 at 12:20 PM, stephane ducasse >>> <stephane.ducasse(a)free.fr> wrote: >>>> >>>> Hi guys >>>> >>>> during the sprint I discussed with Gary about ToolBuilder and we think >>>> that it would be better to remove it >>>> since a lot of new widgets are not covered so this means that we will be >>>> constantly limiting ourselves. >>>> Of course ToolBuilder is a nice idea (if we would have several UI >>>> framework). So far we got only one >>>> and we would have several we would have to take the smallest common >>>> denominator. >>>> Another idea would be to extend toolBuilder to support new widgets. >>>> So what do you think? >>>> >>>> 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 >>> >> >> >> >> -- >> 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

Aug. 2, 2010

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

by Alexandre Bergel

> I'm currently playing with annoucements in TestResult. Indeed what I want to set in the TestCaseEnded: > - is the test has #pass, #failure or #error > - for failure and error, store the Exception so we can now why. In the second version, there is hasPassed, hasFailures, hasError. It simply delegates to the testResult Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 2, 2010

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

by StÃ©phane Ducasse

On Aug 2, 2010, at 11:40 PM, GermÃ¡n Arduino wrote: > 2010/8/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Thanks a lot and also for the discussions (see my other notes). >> > > Published. > >> Stef (today I fixed my cactus collection :)) >> > > :S DNU I collect cactuses and they need my love from time to time to change pots, kill bugs.... :) > > _______________________________________________ > 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