July 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #512: ReTemporaryVariableCapitalizationRule-check-Args

by ci-pharo-ci-jenkins2＠inria.fr

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

July 17, 2020

[Pharo 9.0] Build #511: NewTools 0.4.1 - fix-immediate-newtools-0.4-problems

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #511 was: SUCCESS. The Pull Request #6879 was integrated: "NewTools 0.4.1 - fix-immediate-newtools-0.4-problems" Pull request url: https://github.com/pharo-project/pharo/pull/6879 Issue Url: https://github.com/pharo-project/pharo/issues/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 17, 2020

[Pharo 9.0] Build #510: Ring2-cleanup-remove-isVariableDefinition

by ci-pharo-ci-jenkins2＠inria.fr

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

July 17, 2020

[Pharo 9.0] Build #509: merge-newtools-0.4

by ci-pharo-ci-jenkins2＠inria.fr

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

July 17, 2020

[ANN] NewTools 0.4 integrated into Pharo 9 (New Playground and New Debugger)

by Esteban Lorenzano

Hi all, Today we have integrated (finally!) the first version of our Spec2 based NewTools. While this is a fairly long process that will lead to all tools in Pharo to be written with the same framework and following the same design guidelines, we started with the easiest one (the playground) and one of the most complex (the debugger) to start fleshing out what we want to achieve. Next weeks we will release the new inspector, which for now resides only inside the new debugger and it is just a proof of concept for the moment. In general, for any tool to be a fair replacement to some other tool, it needs to fulfill this two criteria: it needs to solve all the problems the previous tool solved, and it needs to solve problems the previous tool did not. What do you have to expect from the integrated new tools? The new debugger: Allows /object centric debugging./ Enhances extensibility, making adding plugins a lot easier than before. Enables /scripting/. The new playground Enables /sharing variables/between playgrounds Enhances visibility of binding variables by embedding an inspector Enhances visibility of saved pages Both tools should cover already most of the functionality the older tools but there are still some missing features and for sure a good amount of bugs you will find it and we will gladly fix :) Do you want to know more? Object centric debugging tutorial: <https://thepharo.dev/2020/07/16/object-centric-breakpoints-a-tutorial/> Sindarin scripting API: <https://hal.archives-ouvertes.fr/hal-02280915> Playground help file: <https://github.com/pharo-spec/NewTools/blob/master/docs/playground.md> Enjoy! Esteban

July 17, 2020

[Pharo 9.0] Build #508: 6836-DefinitionForNautilus-is-deprecated-so-we-should-remove-it-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #508 was: FAILURE. The Pull Request #6857 was integrated: "6836-DefinitionForNautilus-is-deprecated-so-we-should-remove-it-" Pull request url: https://github.com/pharo-project/pharo/pull/6857 Issue Url: https://github.com/pharo-project/pharo/issues/6836 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 17, 2020

[Pharo 9.0] Build #507: remove-PharoCriticRules

by ci-pharo-ci-jenkins2＠inria.fr

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

July 17, 2020

Re: [Pharo-dev] Parsing and navigating Html

by Sean P. DeNigris

StÃ©phane Ducasse wrote > Now a question, I tried to write a comment for and I was wondering why not > returning '' instead of nil in string. Ten years after your question, I stumbled upon a SO answer [1] that seems to explain this behavior. Apparently `string` returns a string-like object *that retains tree navigation ability* e.g. sibling, parent, where `text` returns a bare string. From this perspective, `nil` seems appropriate to indicate that such a navigable object was not available. That said, it certainly can make the library harder to deal with. What about a Null Object Pattern that returns an object polymorphic with SoupString and that implements appropriate no-ops? 1. https://stackoverflow.com/a/25328374 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

July 16, 2020

[Pharo 9.0] Build #506: Simplify-MetalinkTargetResolver-resolvingBlocForOption

by ci-pharo-ci-jenkins2＠inria.fr

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

July 16, 2020

[Pharo 9.0] Build #505: MoreSmallRulesCleanups

by ci-pharo-ci-jenkins2＠inria.fr

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

July 16, 2020