- Pharo-dev - lists.pharo.org

ANN - Techtalk - Pharo Status May 2020
by tesonep＠gmail.com May 4, 2020

May 4, 2020

Techtalk: Pharo Status May 2020 Abstract: Pharo is moving fast, and sometimes it looks it is doing it in a chaotic way. However, we have a plan and a lot of things that we have accomplished in the past months. The idea of this talk is to present what has been done, where we are, and what are the things that we are working on. The idea of this talk is to be an open talk, where we can share the state but also listen to different ideas about what is important for the community. For so, I am attaching a presentation with the detail of the status, so we can start from it the conversation. When: Wednesday 6th May, 17h00 Paris Time / 15h00 UTC Where: #Techtalk channel in Pharo Discord Server. -- Pablo Tesone. tesonep(a)gmail.com

1 0

[Pharo 9.0] Build #283: Small cleanups in Kernel-Traits
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2020

May 4, 2020

There is a new Pharo build available! The status of the build #283 was: FAILURE. The Pull Request #6291 was integrated: "Small cleanups in Kernel-Traits" Pull request url: https://github.com/pharo-project/pharo/pull/6291 Issue Url: https://github.com/pharo-project/pharo/issues/6290 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #282: remove OCKeyedSet
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2020

May 4, 2020

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

1 0

[Mm10s] 2020-05-04
by Esteban Lorenzano May 4, 2020

May 4, 2020

### Last week: (In fact, this is âlast weekâ plus what I did during holidays, but well... ;) ) * [Spec2] fix a bug while try to assign alignment in a paned layout. * [spec2] code presenter now allow lineNumbers (maybe others to come?) * [spec2] syles can not be added/removed dinamically * [spec2] fix double print of shortcuts on morphic (not sure is correct, but it will work) * Idle-VM: revamp debugger in callback mechanism * [spec2] fixed a regression (https://github.com/pharo-spec/Spec/issues/869 <https://github.com/pharo-spec/Spec/issues/869>) * [NewTools-Playground] playground needs to save last size used * [spec2] fix GtkMorphicUIManager. Now it should select correctly the manager. * [NewTools-Playground] fix bug: menus are showing incorrect shortcut (they were duplicated) * [spec2] added methods required by syntax highlight to code presenter (it was not working properly) * [spec2] added a new SpPresenterSelectorPresenter (ugly name, but descriptive) to allow containers that will change its contents depending on a condition. * [spec2] bugfix: SpWindowResizing needs to inform old and new sizes in SpWindow (morphic). * [spec2] calling #asPresenter in #add:constraints to make sure dynamic-added presenters are actually presenters (since we can add also strings) * [NewTools-Playground] add bindings menu and fix bindings access. Add "shared" bindings concept. * [NewTools-Playground] documentation * [spec2] merged work on RichText (pillar) from Norbert * [spec2] created specdocs project to generate pillar docs (maybe this needs to be part of spec itself?) ### This week (starting 2020-05-04): * fixes on SpMenuPresenter and keybingdings for Gtk backend * new spec2 merge with Pharo 9. * work on new tools playground.

1 0

[Pharo 9.0] Build #281: 6293 opal ast mapping cache produces errors and freezes image when creating accessors method from the debugger after a dnu
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2020

May 4, 2020

There is a new Pharo build available! The status of the build #281 was: FAILURE. The Pull Request #6294 was integrated: "6293 opal ast mapping cache produces errors and freezes image when creating accessors method from the debugger after a dnu" Pull request url: https://github.com/pharo-project/pharo/pull/6294 Issue Url: https://github.com/pharo-project/pharo/issues/6293 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #280: Cleanup FuzzyMatcher packages
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2020

May 4, 2020

There is a new Pharo build available! The status of the build #280 was: SUCCESS. The Pull Request #6272 was integrated: "Cleanup FuzzyMatcher packages" Pull request url: https://github.com/pharo-project/pharo/pull/6272 Issue Url: https://github.com/pharo-project/pharo/issues/6271 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #279: DeadCodeCleanup: Rules
by ci-pharo-ci-jenkins2＠inria.fr May 3, 2020

May 3, 2020

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

1 0

FullBlockClosure - How to create one...
by Sean P. DeNigris May 2, 2020

May 2, 2020

What am I not understanding about FullBlockClosure? I have a clean block that I'd like to turn into a FullBlockClosure so that I can serialize it without dragging (unneeded methods) into my object graph. However, documentation and in-image example usages seem severely limited. Here was one experiment that ended with a primitive failure. It seems like a receiver is needed and it can't be a dummy value (see commented "receiver: 1"). But what would the receiver be in the absence of an outer context?! aBlockClosure := [ :a :b | 1 + a + b ]. fbc := (FullBlockClosure outerContext: nil startpc: aBlockClosure startpc numArgs: aBlockClosure argumentCount copiedValues: Array new) "receiver: 1; yourself". fbc value: 2 value: 3. "PrimitiveFailed: primitive #value:value: in FullBlockClosure failed" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 10

[Pharo 9.0] Build #278: DeadCodeCleanup: Rules
by ci-pharo-ci-jenkins2＠inria.fr May 2, 2020

May 2, 2020

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

1 0

[Pharo 9.0] Build #277: Categorize classes in Reflectivity-Tests
by ci-pharo-ci-jenkins2＠inria.fr May 2, 2020

May 2, 2020

There is a new Pharo build available! The status of the build #277 was: FAILURE. The Pull Request #6281 was integrated: "Categorize classes in Reflectivity-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/6281 Issue Url: https://github.com/pharo-project/pharo/issues/6268 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0