April 2019 - Pharo-dev - lists.pharo.org

keyboard events using Spec
by RaniOfTheRain April 29, 2019

April 29, 2019

Hey, I'm new to using Pharo and Spec and am currently trying to build a Text Editor for a university project. I was wondering how one would capture keyboard events in order to change the text on a Spec LabelPresenter. I know there is a TextPresenter however I'm not able to use this as I need to program my own selection code etc. Many thanks -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

image state saving TDD
by Ben Coman April 29, 2019

April 29, 2019

Just a thought on a dream feature... When doing TDD, it would be super cool if in a test method, the state of the image was saved just before an #assert: so if the assert fails the state is restored to just before the assert was called, so I don't have to <Restart> and multi-step <Over> through the whole method to get back to the message I want to step into. cheers -ben

2 1

[ANN] Pharo Consortium New Academic Member: LIFIA
by Marcus Denker April 29, 2019

April 29, 2019

The Pharo Consortium is very happy to announce that LIFIA has joined the Consortium as an Academic Member. About - LIFIA is a Research Center based at the Faculty of Informatics of the National University of La Plata, in Argentina. It is an associated center to the Scientific Research Commission of the Buenos Aires Province (CIC-PBA). LIFIA pioneered the use of OOP (and Smalltalk in particular) in Argentina's industry and academia. https://www.lifia.info.unlp.edu.ar/en/ - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

1 0

[Pharo 8.0] Build #247: 3214-Spec-synchronization
by ci-pharo-ci-jenkins2＠inria.fr April 29, 2019

April 29, 2019

There is a new Pharo build available! The status of the build #247 was: FAILURE. The Pull Request #3216 was integrated: "3214-Spec-synchronization" Pull request url: https://github.com/pharo-project/pharo/pull/3216 Issue Url: https://github.com/pharo-project/pharo/issues/3214 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #246: Fixes: #3245 to ensure that we cannot create an empty protocol.
by ci-pharo-ci-jenkins2＠inria.fr April 29, 2019

April 29, 2019

There is a new Pharo build available! The status of the build #246 was: FAILURE. The Pull Request #3270 was integrated: "Fixes: #3245 to ensure that we cannot create an empty protocol." Pull request url: https://github.com/pharo-project/pharo/pull/3270 Issue Url: https://github.com/pharo-project/pharo/issues/3245 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

How to convey that a message create a new instance
by ducasse April 28, 2019

April 28, 2019

Hi I was looking at the API of Color and it is really confusing to me and wrong For example beOpaque beOpaque "Set the transparency of the receiver to opaque, i.e. alpha to 1.0." ^ self alpha: 1.0 But alpha: aFloat "Answer a new Color with the given amount of opacity ('alpha')." ^ self class r: self red g: self green b: self blue alpha: aFloat Or adjustBrightness: brightness "Adjust the relative brightness of this color. (lowest value is 0.005 so that hue information is not lost)â but this creates a new color. I would really like to see how we can improve the fact that reading the method selector should let us understand whether a message is modifying or not the receiver. Since many methods such as darker, duller,â¦. do not show that they return a new instance but actually do it. May be we can make sure that modifying receiver methods are much better identified as doing so. beOpaque -> asOpaque adjustBrightness: -> colorWithBrigthness: Do you have any better ideas? Stef

7 12

[Pharo 8.0] Build #245: 3238-Cleaning-ClassDefinition-package
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2019

April 28, 2019

There is a new Pharo build available! The status of the build #245 was: SUCCESS. The Pull Request #3267 was integrated: "3238-Cleaning-ClassDefinition-package" Pull request url: https://github.com/pharo-project/pharo/pull/3267 Issue Url: https://github.com/pharo-project/pharo/issues/3238 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #244: 2184-contrastingColor-and-contrastingForegroundColor-should-be-merged-and-renamed
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2019

April 28, 2019

There is a new Pharo build available! The status of the build #244 was: SUCCESS. The Pull Request #3253 was integrated: "2184-contrastingColor-and-contrastingForegroundColor-should-be-merged-and-renamed" Pull request url: https://github.com/pharo-project/pharo/pull/3253 Issue Url: https://github.com/pharo-project/pharo/issues/2184 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #243: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr April 26, 2019

April 26, 2019

There is a new Pharo build available! The status of the build #243 was: SUCCESS. Could not extract further issue information from commit message: Update minimum-reviews.yml make changesThreshold 1... 100 is far too high as most changes are very small Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #242: 3225-RGPackage-should-be-RGPackageDefinition
by ci-pharo-ci-jenkins2＠inria.fr April 26, 2019

April 26, 2019

There is a new Pharo build available! The status of the build #242 was: SUCCESS. The Pull Request #3226 was integrated: "3225-RGPackage-should-be-RGPackageDefinition" Pull request url: https://github.com/pharo-project/pharo/pull/3226 Issue Url: https://github.com/pharo-project/pharo/issues/3225 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0