- Pharo-dev - lists.pharo.org

Nautilus running tests and expected failures

by Holger Hans Peter Freyther

Hi, I used Nautilus to browse some code and make myself familiar with a foriegn codebase. I inserted some code and pressed the button in the browser to execute the test. The button turned green, I got the test finished notification but my code was not executed. It took me a bit to figure out that this test is in the expected failure list and only by stepping through the exception handling and looking at the 'TestResult' returned from TestResult>>#runTest. Is there any color (not equal to green) that could be used to indicate expected failures? kind regards holger

July 22, 2013

Re: [Pharo-dev] [update 3.0] #30290

by Martin Dias

Note this change improved a lot the loading time of Monticello packages in general. The bench showed 3x speed-up loading Pier3 (from more than 10 minutes to less than 4 minutes!) Thanks Esteban! MartÃn On Mon, Jul 22, 2013 at 9:42 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30290 > ----- > > 10393 Add RPackageSet cache > https://pharo.fogbugz.com/f/cases/10393 > > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-Core-MarcusDenker.24… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.839.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Metacello-Platform.pharo20-Ma… > >

July 22, 2013

Re: [Pharo-dev] [update 3.0] #30285

by Martin Dias

On Sat, Jul 20, 2013 at 8:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On Fri, Jul 19, 2013 at 2:27 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: >> >> 30285 >> ----- >> >> 10823 Kill old list model >> https://pharo.fogbugz.com/f/cases/10823 >> >> 11136 RadioButtonGroupExample new openWithSpec is not working >> https://pharo.fogbugz.com/f/cases/11136 >> >> 11174 Add support for sync position of multiple widgets with just one >> scroll bar >> https://pharo.fogbugz.com/f/cases/11174 > > > How does this work? Do you have an example at hand? Ben showed me how to sync a side bar morph with the scroll bar of a spec widget. We added a new announcement for listening scroll changes, and we decided to publish an example. You can see: ScrollSyncExample new openWithSpec Martin > > Doru > > > >> >> >> >> >> Diff information: >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Examples-MarcusDenker.33… >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.48.… >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

July 22, 2013

Re: [Pharo-dev] About abuse of inheritance

by Denis Kudriashov

2013/7/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > This is not because we have a dynamically typed language that we should > not use subtyping. > Have a look at my lecture there are slides on subtyping. > > Compare: > > OrderedCollection subclass: #Poem > of course a poem is a collection of word. Now it is not a subtype of > collection!!! > OrderedCollection subclass: #UniqueOrderedCollection > > > or compare > > OrderedCollection subclass: #Stack > > vs. > > Stack subclass: #HanoiStack > > Think in terms of API and polymorphic objects > I agree with your examples. And I never build my domain "container like classes" as subclass of OrderedCollection (or friends). But Announcer to me is different concern. It is like subclassing Object as Tudor said. What is all api of Announcer? > > Announcer allSelectors > It should be "Announcer selectors" (it is 16 methods). And I think it is wrong to name all methods of class as API. And I think Announcer API can be reduced to just 5 methods: #announce:, #on:do, #subscribe:send:to:, #unsubscribe:and #week. All others are private or just convenient aliases (maybe already deprecated). And this 5 methods is exactly what I need to subscribe on "event service" with enough flexibility. So when I implement my domain "event source" I need superclass which will supply to my service such nice API. And now there is only Announcer class for this. I were look at Announcer hierarchy. What do you think about SystemAnnouncer class? It has strange implementation. It is subclass of Announcer and it has another announcer instance named "private".

July 22, 2013

Re: [Pharo-dev] [2.0] One Issue left!

by Marcus Denker

On Jul 22, 2013, at 10:06 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > https://pharo.fogbugz.com/default.asp?10234#76081 > https://github.com/pharo-project/pharo-core/releases/tag/30088 > > and the diff > https://github.com/pharo-project/pharo-core/commit/f797f401aa4c50db5cc30b91… > > and I think it is the first change on the Morph.cls itself > Thanks! I have submitted a fix. Marcus

July 22, 2013

Re: [Pharo-dev] [2.0] One Issue left!

by Camillo Bruni

https://pharo.fogbugz.com/default.asp?10234#76081 https://github.com/pharo-project/pharo-core/releases/tag/30088 and the diff https://github.com/pharo-project/pharo-core/commit/f797f401aa4c50db5cc30b91… and I think it is the first change on the Morph.cls itself On 2013-07-22, at 09:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > After checken/recategorizing, there is just one issue left to be evaluated for back porting > to 2.0: > > 10860 option click on list in TestRunner and others: freeze system > https://pharo.fogbugz.com/f/cases/10860 > > I know that this was fixed in Pharo3 already, but i can't find the issueâ¦ > > Marcus

July 22, 2013

[2.0] One Issue left!

by Marcus Denker

Hi, After checken/recategorizing, there is just one issue left to be evaluated for back porting to 2.0: 10860 option click on list in TestRunner and others: freeze system https://pharo.fogbugz.com/f/cases/10860 I know that this was fixed in Pharo3 already, but i can't find the issueâ¦ Marcus

July 22, 2013

[update 3.0] #30290

by Marcus Denker

30290 ----- 10393 Add RPackageSet cache https://pharo.fogbugz.com/f/cases/10393 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-Core-MarcusDenker.24… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.839.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Metacello-Platform.pharo20-Ma…

July 22, 2013

Re: [Pharo-dev] About abuse of inheritance

by StÃ©phane Ducasse

On Jul 21, 2013, at 9:27 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2013/7/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > And what I should do if I want Customer which can trigger events? > > then ask yourself about the API of your customer > Do you want the full API of Announcer? I doubt. > > > Do you think "EventSource subclass: #Customer" make any difference? Or do you think we should never use inheritance to make domain announcer classes? What the existed alternative? I don't want always add announcer instance and couple equal methods any time I need it. > > Think about API not about code reuse. > Think about polymorphic objects. > Each time you subclass from Announcer ALL the API should make sense. > > What is all api of Announcer? Announcer allSelectors > It is just two methods: #announce: and #on:send:to:. No!! this is exactly my point. When you inherit from a class you get its API merged into the one of your class. > When I need "object with events" I always need this methods. What problem? We should not use subclassing for code reuse but use subclassing for subtyping (= polymorphic interface). This is not because we have a dynamically typed language that we should not use subtyping. Have a look at my lecture there are slides on subtyping. Compare: OrderedCollection subclass: #Poem of course a poem is a collection of word. Now it is not a subtype of collection!!! OrderedCollection subclass: #UniqueOrderedCollection or compare OrderedCollection subclass: #Stack vs. Stack subclass: #HanoiStack Think in terms of API and polymorphic objects Stef

July 22, 2013

[update 3.0] #30289

by Marcus Denker

30289 ----- 11204 Crash if changes file is not writable https://pharo.fogbugz.com/f/cases/11204 11198 Update Pharo with latest Opal https://pharo.fogbugz.com/f/cases/11198 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke…

July 22, 2013