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

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

by Lukas Renggli

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

Dec. 22, 2009

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

by StÃ©phane Ducasse

What is a TestToken? Stef On Dec 22, 2009, at 6:27 PM, Adrian Kuhn wrote: > A first fork is available > > Gofer it > squeaksource: 'akuhn'; > package: 'SUnit'; > package: 'SUnitGUI'; > load > > it has two new behaviors, TAssertable and TestToken. > > In the old design class `TestCase` had two purposes: once as context of a > running test, and once as result of a test after having been run. The new > design separates these two roles, which had both different state and different > life time. No more nullifying of instance variables after a test has been run. > Also the outcome of tests (ie whether passed or not) has been moved from test > result to the tokens. > > Next up is to change test suites such that they contain tokens rather than test > cases, and establish tokens as unique identifiers of test cases (such that we > can compare aTestCase token with #==). > > Distribute source control ftw! > > --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

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

by Stan Shepherd

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.

Dec. 22, 2009

[Pharo-project] Issue 1658: EncoderForV3PlusClosures(EncoderForV3)>>genPushLiteral: doesNotUnderstand: #<

by Stan Shepherd

1.Ran full test suite (7266 run, 7223 passes, 21 expected failures, 9 failures, 13 errors, 0 unexpected passes) 2.store result as progress measurement 3.EncoderForV3PlusClosures throws above error. walkback attached to issue. -- View this message in context: http://n2.nabble.com/Issue-1658-EncoderForV3PlusClosures-EncoderForV3-genPu… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 22, 2009

[Pharo-project] SUnit forked, gofer it

by Adrian Kuhn

A first fork is available Gofer it squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load it has two new behaviors, TAssertable and TestToken. In the old design class `TestCase` had two purposes: once as context of a running test, and once as result of a test after having been run. The new design separates these two roles, which had both different state and different life time. No more nullifying of instance variables after a test has been run. Also the outcome of tests (ie whether passed or not) has been moved from test result to the tokens. Next up is to change test suites such that they contain tokens rather than test cases, and establish tokens as unique identifiers of test cases (such that we can compare aTestCase token with #==). Distribute source control ftw! --AA

Dec. 22, 2009

[Pharo-project] Issue 1657: Large test suites caused slow OB menu, fix attached.

by StÃ©phane Ducasse

Issue 1657: Large test suites caused slow OB menu, fix attached. from aKuhn Thanks adrian.

Dec. 22, 2009

Re: [Pharo-project] ImageSegment vs SmartRefStream

by StÃ©phane Ducasse

Read the class comment. There is a small comment. stef On Dec 22, 2009, at 2:06 PM, Mariano Martinez Peck wrote: > Sorry, and I forgot another one: > > 3) Which is the difference between ReferenceStream and SmartRefStream ? > > Cheers > > mariano > > On Tue, Dec 22, 2009 at 2:02 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi folks. I have been analyzing the code and trying to understand what ImageSegment does and how. After that, I came up to SmartRefStream and here is where I have some questions: > > 1) which is the difference between ImageSegment and SmartRefStream ? what does each of them do ? > > 2) Who uses who ? ImageSegment uses SmartRefStream or vice-versa? each one use the other? > > Thank you for any hints you can give me. > > Mariano > > _______________________________________________ > 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

[Pharo-project] getting started with sound

by Cameron Sanders

Not that I have finished any of the other projects that are of importance to me... but I am wondering how/where to get started with sound. I have no idea what capabilities already exist even though there is a long list of related classes. Can I record from a mic and get the list of notes? etc. thanks in advance, Cam

Dec. 22, 2009

Re: [Pharo-project] ImageSegment vs SmartRefStream

by Schwab,Wilhelm K

Re SmartReferenceStream, my understanding is that it tries to cope with instance variable layout changes, and perhaps does a better job of handling cycles than does ReferenceStream. It goes about these things VERY poorly. First, it assumes that a good response to a layout change is to display a walkback and offer to generate code to compensate for it. That's fine for a developer, but it has no place in a world with end users. Second, the conversion methods end up in a common location (class side of SRS, IIRCC) instead of being somewhow associated with the offending class. Finally, you might want to serialize some small objects and note the verbosity of the output. So far, SIXX appears to be a better choice. My opportunity to stress test it still requires a fair amount of porting, but offers 10k+ richly populated objects when I finally get there. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Tuesday, December 22, 2009 8:06 AM To: The general-purpose Squeak developers list Cc: Pharo Development Subject: Re: [Pharo-project] ImageSegment vs SmartRefStream Sorry, and I forgot another one: 3) Which is the difference between ReferenceStream and SmartRefStream ? Cheers mariano On Tue, Dec 22, 2009 at 2:02 PM, Mariano Martinez Peck <marianopeck(a)gmail.com<mailto:marianopeck@gmail.com>> wrote: Hi folks. I have been analyzing the code and trying to understand what ImageSegment does and how. After that, I came up to SmartRefStream and here is where I have some questions: 1) which is the difference between ImageSegment and SmartRefStream ? what does each of them do ? 2) Who uses who ? ImageSegment uses SmartRefStream or vice-versa? each one use the other? Thank you for any hints you can give me. Mariano

Dec. 22, 2009

Re: [Pharo-project] SUnit

by Adrian Kuhn

Julian Fitzell <jfitzell@...> writes: > > What is Grease/Slime? > > I don't know - we've become pseudo-experts for Seaside but it doesn't > seem to be that tough in our case - just a matter of avoiding lots of > things that aren't compatible. > > Grease is the light-weight compatibility layer we have ended up > developing out of the Seaside project. I also used it to port Magritte > and Pier to VA Smalltalk and Colin and I are now beginning to use it > for MC2. > > Slime is a set of lint rules - currently some of them are > Seaside-specific but others are essentially a counterpart to Grease - > detecting things that you cannot do if you want your code to be > portable. > > The hope is that others can leverage the experience we've developed > and our porters' efforts getting Grease running on their platforms. I > still need to finish a write-up on what Grease is and post it > somewhere - on my todo list for the holidays. Awesome. Looking forward to your post! Guess the best strategy is to go for a Pharo-only rewrite, and then added portability as the design stabilizes. --AA -- Follow me http://twitter.com/akuhn Follow me http://twitter.com/jexample Follow me http://twitter.com/codemap Follow me http://twitter.com/suite2010

Dec. 22, 2009