January 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #412: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 7, 2018

Jan. 7, 2018

There is a new Pharo build available! The status of the build #412 was: SUCCESS. Could not extract further issue information from commit message: https://github.com/pharo-project/pharo/pull/617 https://pharo.fogbugz.com/f/cases/20875/ Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

PrimitiveOSError class name
by Alistair Grant Jan. 7, 2018

Jan. 7, 2018

Hi Eliot, I'm just preparing a fogbugz issue and PR to add PrimitiveOSError to Pharo and was wondering about the class name. As you say in the class comments, errorName is typically set to #'operating system error' (I haven't seen anything else), which makes the class name and errorName somewhat redundant. What do you think of renaming the class to PrimitiveError, which will make it a bit more general and extensible in future? Thanks, Alistair

1 0

(Morph>>#asDraggableMorph) isPrimitive
by Norbert Hartl Jan. 6, 2018

Jan. 6, 2018

Can anyone explain why (Morph>>#asDraggableMorph) isPrimitive. returns true? Norbert

4 4

Calling primitiveFailed
by Norbert Hartl Jan. 6, 2018

Jan. 6, 2018

Looking through primitive methods I can see two cases. Most methods seem to call self primitiveFailed at the end of the method. But some as Object>>#at:put: do not. Can I assume that all primitive methods should call primitiveFailed at the end? Norbert

2 1

New Year Wishlist (2018) ?
by Esteban Lorenzano Jan. 6, 2018

Jan. 6, 2018

Hi everybody, This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. Features, improvements, radical changes, etcâ¦. whatever you want. Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) So, letâs those wishes come! cheers, Esteban

19 50

extract method refactoring with assignment
by Eliot Miranda Jan. 5, 2018

Jan. 5, 2018

Hi All, I tried an extract to method refactoring yesterday that failed. The method looked like | ... v1 v2 v3 | .... v1 := self m1. v2 := self m2. v3 := v3 collect: [:e| ...]. .... such that v1 and v2 were only used in the block, and the block was complex enough and did something useful e Pugh that I wanted to refactor as | ... v1 v2 v3 | .... v3 := self complexCollect: v3. .... complexCollect: a | v1 v2 | v1 := self m1. v2 := self m2. ^a collect: [:e| ...] So I was forced by the fact that assignment is written with the variable on the LHS to include "v3 := " in the selection to extract to method, even though my intent was for it not to be included. And of course the refactoring attempt fails precisely because the assignment /is/ included :-) Shouldn't this case be specially handled do that and trailing assignment is left behind in the refactored original method? Ifso, how would one go about it? Note that part of the prerequisite checks should also check that the variables v1 & v2 are not used elsewhere in the origins nail method and whether the refactoring is smart enough to remove them from the refactored origins nap is optional but definitely preferred. _,,,^..^,,,_ (phone)

2 1

[Pharo 7.0-dev] Build #411: 20925 Super setUp need to be called in UnifiedFFI tests
by ci-pharo-ci-jenkins2＠inria.fr Jan. 5, 2018

Jan. 5, 2018

There is a new Pharo build available! The status of the build #411 was: FAILURE. The Pull Request #645 was integrated: "20925 Super setUp need to be called in UnifiedFFI tests" Pull request url: https://github.com/pharo-project/pharo/pull/645 Issue Url: https://pharo.fogbugz.com/f/cases/20925 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #410: 20926-Super-setUp-need-to-be-called-in-MCWorkingCopyBrowserTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 5, 2018

Jan. 5, 2018

There is a new Pharo build available! The status of the build #410 was: SUCCESS. The Pull Request #646 was integrated: "20926-Super-setUp-need-to-be-called-in-MCWorkingCopyBrowserTest" Pull request url: https://github.com/pharo-project/pharo/pull/646 Issue Url: https://pharo.fogbugz.com/f/cases/20926 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #409: 20924 Fix unused var tutorial in TutorialPlayerTestWithMockTutorial>>setUp
by ci-pharo-ci-jenkins2＠inria.fr Jan. 5, 2018

Jan. 5, 2018

There is a new Pharo build available! The status of the build #409 was: SUCCESS. The Pull Request #644 was integrated: "20924 Fix unused var tutorial in TutorialPlayerTestWithMockTutorial>>setUp" Pull request url: https://github.com/pharo-project/pharo/pull/644 Issue Url: https://pharo.fogbugz.com/f/cases/20924 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

gtInspector+FastTable enhancement requests
by Ben Coman Jan. 5, 2018

Jan. 5, 2018

Feedback for GT'ers... I'm probably ab-using FastTable support in gtInspector, but as a quick hack during initial prototyping it was *very* nice to be able review retrieved data as a table of instances with a column per instance variable. Some enhancements that would make this even better... 1. Horizontal scroll bar - There are columns past the right margin that I can't get to for lack of one. 2. Column resizing to shift subsequent columns, which could provide another path to seeing the hidden columns. 3. Individual column width auto-fit - like in Excel where you double-click the edge https://www.youtube.com/watch?v=Yeb8emsjtf4 4. All columns auto-fit 5. Auto-fit columns prior to first opening. 6. Being able to split column labels over two lines - to allow for thinner columns For a demonstration, could you please load the attached ST fileout (its small), and also... Gofer it smalltalkhubUser: 'SvenVanCaekenberghe' project: 'Neo'; configurationOf: 'NeoJSON'; loadStable. Then inspect.... BittrexMarket getAll. cheers -ben

3 4