- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #513: Use ifNil: ifNotNil: and ifNil:ifNotNil: instead of isNil and ifTrue/â¦
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2019

July 17, 2019

There is a new Pharo build available! The status of the build #513 was: FAILURE. The Pull Request #3967 was integrated: "Use ifNil: ifNotNil: and ifNil:ifNotNil: instead of isNil and ifTrue/â¦" Pull request url: https://github.com/pharo-project/pharo/pull/3967 Issue Url: https://github.com/pharo-project/pharo/issues/useIfNilOnASTPackages Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #512: ifNil usage on Debugger-Model
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2019

July 17, 2019

There is a new Pharo build available! The status of the build #512 was: SUCCESS. The Pull Request #3970 was integrated: "ifNil usage on Debugger-Model" Pull request url: https://github.com/pharo-project/pharo/pull/3970 Issue Url: https://github.com/pharo-project/pharo/issues/ifNilOnDebugging Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[issue tracker] reduced the "days until stale" for issues
by Marcus Denker July 17, 2019

July 17, 2019

Hi, The issues used to have a stale range of 240 days, I reduced it to 180. This way people get a reminder before the release for all the issues that they opened early in the development phase. After around half a year, the stale bot will put a label on the issue and add a comment: To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 8 months. It will be closed in 1 month if no further activity occurs. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions. Then 30 days later the issue will be closed if there is no update. (see for the config of the bot: https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/stale.yml )

1 0

[Pharo 8.0] Build #511: ifNil usage on Kernel
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2019

July 17, 2019

There is a new Pharo build available! The status of the build #511 was: FAILURE. The Pull Request #3974 was integrated: "ifNil usage on Kernel" Pull request url: https://github.com/pharo-project/pharo/pull/3974 Issue Url: https://github.com/pharo-project/pharo/issues/ifNilOnKernel Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ESUG19: Camp Smalltalk 24/25 August
by Marcus Denker July 17, 2019

July 17, 2019

As usual at ESUG, we will be holding an informal âCamp Smalltalkâ the weekend before the conference. The idea is to meet, hack, discuss. - location: ZWEIDENKER, Luxemburger Str. 72, 50674 KÃ¶ln (see https://zweidenker.de/kontakt/ <https://zweidenker.de/kontakt/> ) - dates & times: - Saturday, 24.8.2019 from 11:00 AM to 6:00 PM - Sunday, 25.8.2019 from 11:00 AM to 6:00 PM To have and idea who is coming, please fill out this doodle https://doodle.com/poll/ffkt7rqm4sfi62df <https://doodle.com/poll/ffkt7rqm4sfi62df> (just select when you will attend). FYI: Gamescom takes place in Cologne from 21.-24. August 2019. Cologne will be crowded and Hotels are expensive until the 24th.

1 0

[Pharo 8.0] Build #510: Fix Fully #3410- [Trait] Impossible to use from a classTrait a method that is also defined in a subclass of Behavior even when following the doc
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2019

July 17, 2019

There is a new Pharo build available! The status of the build #510 was: SUCCESS. The Pull Request #3904 was integrated: "Fix Fully #3410- [Trait] Impossible to use from a classTrait a method that is also defined in a subclass of Behavior even when following the doc" Pull request url: https://github.com/pharo-project/pharo/pull/3904 Issue Url: https://github.com/pharo-project/pharo/issues/4310 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #509: ifNil usage on BlueInk packages
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2019

July 17, 2019

There is a new Pharo build available! The status of the build #509 was: SUCCESS. The Pull Request #3968 was integrated: "ifNil usage on BlueInk packages" Pull request url: https://github.com/pharo-project/pharo/pull/3968 Issue Url: https://github.com/pharo-project/pharo/issues/useIfNilOnBlueInk Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Website] Newsletter subscription more prominent
by Marcus Denker July 17, 2019

July 17, 2019

Hi, After we removed the annoying popup, new subscriptions to the newsletter slowed down to almost none. To counter that, I added a signup form more prominently on the front page: https://pharo.org Marcus

1 0

[Pharo 8.0] Build #508: 3965-Minimal-image-calls-but-doesnt-include-SmalltalkImageplatformName
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2019

July 17, 2019

There is a new Pharo build available! The status of the build #508 was: FAILURE. The Pull Request #3966 was integrated: "3965-Minimal-image-calls-but-doesnt-include-SmalltalkImageplatformName" Pull request url: https://github.com/pharo-project/pharo/pull/3966 Issue Url: https://github.com/pharo-project/pharo/issues/3965 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] "whenSelectedItemChanged:" in Spec
by Ben Coman July 17, 2019

July 17, 2019

Following on from something I noticed commenting on "[Pharo-users] "whenSelectedItemChanged:" in Spec"... On Wed, 17 Jul 2019 at 08:38, Ben Coman <btc(a)openinworld.com> wrote: > Looking at ListPresenter>>whenSelectedItemChanged: aBlock > it is registering aBlock on selectionHolder using #whenChangedDo: > Reviewing selectionHolder "Code search...>References to it" I see that > selectionHolder is initialized as an instance of SelectionHolderClass. > > So it seems you are expecting whenSelectedItemChanged: to be called > every time the-selection-is-changed > when actually it is only called once (by your application) to register > the block-to-be-called when the-selection-is-changed. > You don't seem to have done any such registration. It seems awkward that the SelectionValueHolder used by ListPresenter allows #index: and #selection: to be set independently making it too easy to get insistent state. Multi-selection also has a completely different basis using IdentityDictionary with the boolean "multiSelection" indicating some widget specific handling to distinguish between the two selection-types that may be duplicated a lot elsewhere. It might be nice to have a generic SelectionWrapper class that behaved a bit like a PositionableStream to encapsulate any "collection" as its first instance variable, with "positions" as its only other instance variable. Selected-values would be a derivation of those two instance variables. "positions" is used rather than "index" since the latter feels 1-dimensional and it should work just as well with a 2-dimensional grid/table. For an event-driven facility it might subclass Model, or it may be simpler to have its own Announcer. WDYT? Would such a class be worthwhile? Where in the system might this reduce code duplication? (which would define its requirements) Are there any existing candidates? (Reviewing Spotter('selection') doesn't indicate anything. The closest is SelectionMorph which has baggage and works with items rather than positions) cheers -ben

1 0