November 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] SUnit: history support and OB icons

by Alexandre Bergel

Hi simon, > SLICE-Issue338-SUnitHistoryAndIcons-simon_denier.6.mcz I loaded your file, but there is no icon in OB that show up. Sorry for last week end, I could not work as much as I wanted. Alexandre > > > On 22 nov. 08, at 18:33, StÃ©phane Ducasse wrote: > >> Ok I see so in that case removing the authorname can be a good >> compromised >> >> Stef >> On Nov 22, 2008, at 4:02 PM, Simon Denier wrote: >> >>> >>> On 22 nov. 08, at 13:08, Adrian Lienhard wrote: >>> >>>> The reason is that TestCase class >> #methodChanged: is executed >>>> each time a method is modified or compiled and it then creates >>>> for each test case class a new dictionary that stores the author >>>> name (and if not set, this will trigger the popup). This >>>> dictionary is then stored in another dictionary in a class >>>> variable... >>> >>> Actually this is something related. Whenever you browse a TestCase >>> class, OB scans the test history to look for previous results. If >>> test results are not present, then an empty dictionary of results >>> is sent back. But this dictionary is still initialized with a >>> timestamp and the author name, so the name box can raise. >>> >>> Do we need the author name in test results? It's good for >>> traceability, but too much hassle. Easy to fix anyway. >>> >>>> >>>> >>>> Adrian >>>> >>>> On Nov 22, 2008, at 12:43 , StÃ©phane Ducasse wrote: >>>> >>>>> simon, alex and others >>>>> can you check why the author name is asked while it should not? >>>>> This is annoying and I would like to see that fixed. >>>>> >>>>> Stef >>>>> >>>>> On Nov 19, 2008, at 10:02 PM, Simon Denier wrote: >>>>> >>>>>> Hi all >>>>>> >>>>>> Just to notify a new enhancement to review in the PharoInbox. >>>>>> >>>>>> SLICE-Issue338-SUnitHistoryAndIcons-simon_denier.2 >>>>>> >>>>>> >>>>>> Short doc: >>>>>> >>>>>> Add: >>>>>> - support history for test runs as well as progression filter >>>>>> to show test in progression, regression >>>>>> - support icons in OB to show the current state of a test: >>>>>> passed, failed, progressed, regressed... >>>>>> >>>>>> History support: >>>>>> - whenever some test cases run from the TestRunner, their >>>>>> results are stored in a class side variable TestResult >>>>>> class>>History >>>>>> - contextual menu for history in TestRunner>>error pane: >>>>>> 1) History: access submenu to TestRunner instance history: can >>>>>> save and show progress between results ran in the same >>>>>> TestRunner; lost when this particular instance of TestRunner is >>>>>> closed >>>>>> 2) Store results as progress reference: create/update a >>>>>> lastStoredRun method on the class side of each TestCase which >>>>>> have just been run, containing the results >>>>>> 3) Show progress: make a diff between the last run and the >>>>>> lastStoredRun, showing progress or regress in tests (new >>>>>> passed, new failures, new errors) >>>>>> >>>>>> The idea is that whenever you are satisfied with the current >>>>>> results of some of your tests, you can save this state as a >>>>>> reference point with the 'Store results...' action. >>>>>> This reference point can be compared with subsequent test >>>>>> results to show your progression or regression. >>>>>> >>>>>> Test results are stored in a class side variable some are kept >>>>>> local to your image. Reference results are stored in a special >>>>>> method for each TestCase, so that they are saved with their >>>>>> package and can be used as a common reference for package >>>>>> developers. So a good practice is to store the latest test >>>>>> results as reference before committing your changes. >>>>>> >>>>>> >>>>>> Icons support: >>>>>> OB Package browser now has icons for test methods in TestCase >>>>>> subclasses: >>>>>> - green circle: test has passed in the last run >>>>>> - red circle: test has failed >>>>>> - half green/half red circle: state unknown, test has no >>>>>> history or test has changed since last run >>>>>> - (no icon): test has raised an error >>>>>> - upside green arrow: test has progressed since last reference >>>>>> run >>>>>> - downside blue triangle: test has regressed since last >>>>>> reference run >>>>>> >>>>>> A test is in progression if it goes from error or failure to >>>>>> passed state. >>>>>> A test is in regression if it goes from passed to error or >>>>>> failure state. >>>>>> >>>>>> The last two icons have other meanings with methods not related >>>>>> to test, so we should change them whenever someone has better >>>>>> icons. >>>>>> >>>>>> Authors: Alexandre Bergel, Simon Denier, David RÃ¶thlisberger >>>>>> >>>>>> -- >>>>>> Simon >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > Simon > > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 25, 2008

Re: [Pharo-project] Pharo-dev logo :)

by Alexandre Bergel

I like this one :-) Alexandre On 25 Nov 2008, at 05:36, Igor Stasenko wrote: > Hope it not hurts anyone's feelings.. > Just for fun :) > > -- > Best regards, > Igor Stasenko AKA sig. > <Sketch-dev.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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 25, 2008

Re: [Pharo-project] Re: Pharo-dev logo :)

by Igor Stasenko

2008/11/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > :) > May be with a large truck and bulldozer :) > Will in a post-nuclear world Pharo still be there? :) http://picasaweb.google.com/lh/photo/FMOpf6VUl1NGPCOX3khypw?authkey=vUzr8JC… > Stef > > On Nov 25, 2008, at 9:39 AM, Igor Stasenko wrote: > >> 2008/11/25 Igor Stasenko <siguctua(a)gmail.com>: >>> >>> Hope it not hurts anyone's feelings.. >>> Just for fun :) >>> >> >> oops, image too big for mail list.. >> >> >> http://picasaweb.google.com/lh/photo/DUY5XdLy5mYiqceRp93mAA?authkey=vUzr8JC… >> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >> -- >> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Nov. 25, 2008

[Pharo-project] cannot loadOBalpha in 10166 dev

by StÃ©phane Ducasse

Hi David I cannot load...

Nov. 25, 2008

Re: [Pharo-project] Re: Pharo-dev logo :)

by StÃ©phane Ducasse

:) May be with a large truck and bulldozer :) Stef On Nov 25, 2008, at 9:39 AM, Igor Stasenko wrote: > 2008/11/25 Igor Stasenko <siguctua(a)gmail.com>: >> Hope it not hurts anyone's feelings.. >> Just for fun :) >> > > oops, image too big for mail list.. > > http://picasaweb.google.com/lh/photo/DUY5XdLy5mYiqceRp93mAA?authkey=vUzr8JC… > >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > > -- > 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 >

Nov. 25, 2008

[Pharo-project] Re: Pharo-dev logo :)

by Igor Stasenko

2008/11/25 Igor Stasenko <siguctua(a)gmail.com>: > Hope it not hurts anyone's feelings.. > Just for fun :) > oops, image too big for mail list.. http://picasaweb.google.com/lh/photo/DUY5XdLy5mYiqceRp93mAA?authkey=vUzr8JC… > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

Nov. 25, 2008

[Pharo-project] Pharo-dev logo :)

by Igor Stasenko

Hope it not hurts anyone's feelings.. Just for fun :) -- Best regards, Igor Stasenko AKA sig.

Nov. 25, 2008

Re: [squeak-dev] Re: [Pharo-project] Alien FFI

by John M McIntosh

On 24-Nov-08, at 6:37 AM, David Pennell wrote: > John, > > Its probably worthwhile to find a place to post Eliot's > documentation files for Alien. > > -david Documentation files and a start on a wiki page is at: http://wiki.squeak.org/squeak/6100 -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Nov. 24, 2008

Re: [Pharo-project] New sensor code

by Igor Stasenko

2008/11/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > I saw signs of that problem in the recent past. > me too. Its because the interface which managing .changes file stream is not protected by synchronizing object. > stef > > On Nov 24, 2008, at 12:25 PM, Gary Chambers wrote: > >> Perhaps two processes are *writing* to the change log at the same time >> then (shudders). >> >> Regards, Gary. >> >> ----- Original Message ----- From: "Marcus Denker" <denker(a)iam.unibe.ch> >> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Monday, November 24, 2008 11:13 AM >> Subject: Re: [Pharo-project] New sensor code >> >> >> >> On 24.11.2008, at 12:09, Gary Chambers wrote: >> >>> Unexplained SyntaxErrors are often, in my experience, a sign of multiple >>> processes concurrently trying to access the changes file... Have the >>> improvements we supplied for RemoteString been applied? >>> >> >> Yes. >> >> Marcus >> >>> Regards, Gary. >>> >>> ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> >>> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >>> Sent: Saturday, November 22, 2008 6:20 PM >>> Subject: Re: [Pharo-project] New sensor code >>> >>> >>>> and looks like >>>> InputEventFetcher>>eventLoop contains syntax errors, a window variable >>>> shown in red color by my browser. :) >>>> >>>> >>>> 2008/11/22 Igor Stasenko <siguctua(a)gmail.com>: >>>>> >>>>> 2008/11/22 Igor Stasenko <siguctua(a)gmail.com>: >>>>>> >>>>>> I just loaded your changeset and have something to report :) >>>>>> >>>>>> It looks like it having bigger poll periods than old sensor, or works >>>>>> slower. >>>>>> An overall performance feels a bit more sluggish comparing to old >>>>>> implementation. >>>>>> Just open a window with long text and hold down the up/down key and >>>>>> see the difference. >>>>>> Or try to resize browser window - you can notice its not so smooth as >>>>>> in old image. >>>>>> >>>>> >>>>> ... which can be fixed easily by reducing poll period from 100ms to >>>>> 10ms in >>>>> InputEventPollingFetcher>>eventLoop >>>>> >>>>>> 2008/11/22 Michael Rueger <m.rueger(a)acm.org>: >>>>>>> >>>>>>> StÃ©phane Ducasse wrote: >>>>>>>> >>>>>>>> so how do we proceed? >>>>>>>> We try to load it, play with it then? >>>>>>>> integrate it into pharo and you continue hacking and fixing? >>>>>>> >>>>>>> this version is really meant to be smoke tested, it needs some work >>>>>>> on the >>>>>>> comments and on the user interrupt handling. >>>>>>> >>>>>>> So please load it into your images, make sure you always have >>>>>>> backups and >>>>>>> see how it holds up. If it turns out to be reasonably stable we can >>>>>>> push it. >>>>>>> >>>>>>> >>>>>>>> 1- Here I have a question >>>>>>>> =================== >>>>>>>> in this comment EventSensor = InputEventSensor? >>>>>>> >>>>>>> the comment is only a copy from EventSensor, needs to be rewritten. >>>>>>> If somebody has a better suggestion for naming this class I'm open >>>>>>> to >>>>>>> suggestions. >>>>>>> >>>>>>>> 2- I saw a method defined on Controller >>>>>>>> But there are no reference to this class in pharo. So we could >>>>>>>> remove >>>>>>>> Controller I imagine >>>>>>> >>>>>>> It is superclass of other classes, so I'm not sure. >>>>>>> >>>>>>>> 3- could you tell me >>>>>>>> what kind of code we would have to change? >>>>>>> >>>>>>> Not sure what you mean? For now no code in the image needs to be >>>>>>> changed. >>>>>>> >>>>>>> >>>>>>> Michael >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Igor Stasenko AKA sig. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>>>> >>>> >>>> >>>> >>>> -- >>>> 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 >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Marcus Denker -- denker(a)iam.unibe.ch >> http://www.iam.unibe.ch/~denker >> >> >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Nov. 24, 2008

Re: [squeak-dev] Re: [Pharo-project] Alien FFI

by John M McIntosh

Ok, well asAlien seems to be used as conversion methods to ensure a passed object is an alien. What would you like to do instead? I'll integrate the primitive Error code changes this week and do any clean up. If you would like to suggest which variable bindings can be deleted I'll correct that. On 24-Nov-08, at 9:49 AM, Vassili Bykov wrote: > On Mon, Nov 24, 2008 at 12:13 AM, John M McIntosh > <johnmci(a)smalltalkconsulting.com> wrote: >> I would suggest someone with an eye towards "Compiler, CompileMethod, >> ParseNode" carefully look at the changes in "Alien-Core" to ensure >> I've not >> trashed some important part of the Pharo Compiler or Traits. I >> can't say if >> the changes are destructive or passive? > > Many of those have to do with primitive errorCode support, and it > would be nice to categorize them separately. I didn't look closely, > but those that have to do with variable bindings are likely to be > irrelevant. > > And sorry, but adding #asAlien to True, False and UndefinedObject is > just wrong. Nor should have it been in String from the start. > > Cheers, > > --Vassili > -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Nov. 24, 2008