June 2013 - Pharo-dev - lists.pharo.org

For 2.0: links point to latest build on pharp-project.org
by Marcus Denker June 10, 2013

June 10, 2013

Hi, I changed all links to point to the latest 2.0 build on files.pharo.org Reason: -> We are fixing bugs, yet people downloading 2.0 do not see the fix -> We had multiple times that people wasted quite some effort re-reporting bugs that are already fixed. Notes -> the file name "latest.zip" is not good for the image. It should encode that it is the image only and the version number maybe? -> I did not change any VM related download links, but I think we should do the same there. Marcus

5 9

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 10, 2013

June 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 1 regressions found. Tests.Release.ReleaseTest.testObsoleteBehaviors

1 0

[update 3.0] #30191
by Marcus Denker June 10, 2013

June 10, 2013

30191 ----- 10854 AlainTreeModel: keyboard navigation broken https://pharo.fogbugz.com/f/cases/10854 10872 Add more date and time tests https://pharo.fogbugz.com/f/cases/10872 10874 The memory FileSystem has a problem copying files https://pharo.fogbugz.com/f/cases/10874 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.195… http://smalltalkhub.com/mc/Pharo/Pharo30/main/KernelTests-MarcusDenker.520.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1474.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Tests-Core-MarcusD… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Memory-MarcusDenke…

1 0

Re: [Pharo-dev] Tabs
by Stephan Eggermont June 10, 2013

June 10, 2013

I've taken a more detailed look at the tabs. I like the clean look and the functionality very much. To make multi-selecting tabs perfect: - I would like to be able to shift-click to multi-select; - if I command-click on a already selected tab, I would like it to be removed from the set of selected tabs; - I would like the horizontal line below the selected tabs to go away, to make clearer that I'm looking at multiple tabs; - when I resize a column, I would like the relative size to stay when I add another one; - I'm not sure making the order of the panes dependent on the order in which the tabs are selected is a good idea, especially when you allow reordering tabs by drag-and-drop; I think position based ordering is easier to understand; - one way of showing what pane belongs to which tab, would be to draw a thin colored line from the tab to the pane; there is some vertical space you could use for that; - another would be to put a (opaque) icon with an arrow (in a circle?) pointing at the center of the pane over the tab. Stephan

2 1

fogbugz subcases
by Camillo Bruni June 10, 2013

June 10, 2013

I have seen different strategies on using subcases on fogbugz and to me only one way makes sense: Subcases are dependencies Only if all the subcases are finished you can resolve a parent case. I think that comes implicitly from the fact that you cannot have more than one parent. Additionally the typical use-case for me is that you have to split up a complex bug / task into manageable subparts. what do you think?

2 1

Re: [Pharo-dev] FogBugz (Case [Issue]10840) Collection - WeakSet>>#size utterly broken
by Camille Teruel June 10, 2013

June 10, 2013

On 7 juin 2013, at 11:19, Pharo Issue Tracker wrote: > A FogBugz case was edited by Stephane Ducasse. > > Case ID: 10840 > Title: WeakSet>>#size utterly broken > Status: Resolved (Fix Review Needed) > Category: Bug > Project: Collection > Area: Misc > Priority: 3 - Must Fix > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Camille Teruel > > URL: https://pharo.fogbugz.com/f/cases/10840 > > Last message: > Please can you send a mail to the mailing-list so that we all discuss this problems. Hello everyone, WeakSet>>#size is broken as demonstrated by the following snippet: set := WeakSet new. set add: Object new. Smalltalk garbageCollect. set size. "answers 1 instead of 0" That is because a WeakSet has no mean to know when its items get garbage collected, and thus the tally cannot be updated. So we need to override #size in Weak, I propose: size | counter | counter := 0. self do: [ :e | counter := counter + 1 ]. ^ counter But that it rather inefficient for such a simple query. Any proposition? The bug entry is: https://pharo.fogbugz.com/f/cases/10840 > > > If you do not want to receive automatic notifications anymore, change your preferences in the Options screen. (https://pharo.fogbugz.com/default.asp?pg=pgPrefs)

5 8

[update 3.0] #30190
by StÃ©phane Ducasse June 10, 2013

June 10, 2013

30190 ----- 10779 - Parsing faulty method ends with incorrect ast. Thanks Gisela https://pharo.fogbugz.com/default.asp? 10801 - Use UTF8 encoding in MC snapshot source.st https://pharo.fogbugz.com/default.asp?10801 Thanks nicolas cellier and sven. Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Installers-StephaneDuc… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-StephaneDucasse.81… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compression-StephaneDucasse.1… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Tests-Core-StephaneDucass… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Core-StephaneDucasse.166.…

1 0

Necessity of TDD with Smalltalk
by Paul Davidowitz June 10, 2013

June 10, 2013

It seems to me that a big reason for developing via writing tests first (Test Driven Development) is that the tests serve as a debugging tool -- if a test breaks, then the last piece of (non-test) code that change is likely the culprit. But with the powerful debugging environment that comes with Smalltalk, I am wondering of the utility of TDD (TDD is big in the Ruby camp perhaps for a reason). After all, writing and re-writing the tests becomes quite a non-trivial chore (not to mention that the tests themselves could be buggy). So my question: Is it ok in Smalltalk to write tests afterwards? Is it even perhaps recommended? - Paul

7 11

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 10, 2013

June 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 2 regressions found. Tests.Monticello.MCMczInstallerTest.testInstallFromFile Tests.Monticello.MCMczInstallerTest.testInstallFromStream

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 10, 2013

June 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 2 regressions found. Tests.Monticello.MCMczInstallerTest.testInstallFromFile Tests.Monticello.MCMczInstallerTest.testInstallFromStream

1 0