October 2017 - Pharo-dev - lists.pharo.org

Probably stupid... question about string printString.
by Stephane Ducasse Oct. 24, 2017

Oct. 24, 2017

Hi I would like to really understand why 'foo' printString >>> '''foo''' and not why this is not 'foo' itself. Stef

4 9

Iceberg - viewing uncommitted changes
by Ben Coman Oct. 24, 2017

Oct. 24, 2017

When the Iceberg [Packages] tab shows "Uncommitted changes", how do you view what those changes are? For example... $ curl get.pharo.org/70+vm | bash $ ./pharo-ui * Open System > Settings > Include system repositories by default = enabled * Open Tools > Iceberg > "pharo" * Click <Clone> button > enter "git@github.com:pharo-project/pharo.git" * Close and reopen Iceberg so the four tabs show * Select [Packages] tab and sort by "Name" so dirty packages are at top (btw, GT-Spotter and Reflectivity packages are dirty, but ignore that for now) * Open System Browser, randomly select AST-Core > NumberParser > allowPlusSign * Change the comment, save, enter author details. * Not sure how to refresh [Packages] tab, so close and reopen Iceberg and select [Packages] tab, sorted by "Name" ==> "AST_Core" shows "Uncomitted changes" So from here, how can I view what the uncommitted changes of that package are? I partly expect it in the context menu of AST_Core package. cheers -ben P.S. Currently, when I open Iceberg I'm habitually first selecting the [Packages] and [Branches] tabs. If I first select [Remotes] & "origin" followed by... * [Packages] ==> Instance of IceScpRemote did not understand #entity * [Branches] ==> Instance of IceScpRemote did not understand #isBranchModel

2 1

[Pharo 7.0-dev] Build #222: 20575-TextMorph-cannot-work-without-code-completion-temporary-solution
by ci-pharo-ci-jenkins2＠inria.fr Oct. 24, 2017

Oct. 24, 2017

There is a new Pharo build available! The status of the build #222 was: SUCCESS. The Pull Request #387 was integrated: "20575-TextMorph-cannot-work-without-code-completion-temporary-solution" Pull request url: https://github.com/pharo-project/pharo/pull/387 Issue Url: https://pharo.fogbugz.com/f/cases/20575 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

System Update Failure from #60510 -> #60513
by Sean P. DeNigris Oct. 24, 2017

Oct. 24, 2017

It complained of missing "Pharo-Help-TorstenBergmann.53". When I copied it from the Inbox to my package cache, the update succeeded. I'm assuming it should be copied to Pharo60/main, but wanted to confirmâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 3

[Pharo 7.0-dev] Build #221: 20573-BaselineOfMorphic-should-include-System-Identification
by ci-pharo-ci-jenkins2＠inria.fr Oct. 24, 2017

Oct. 24, 2017

There is a new Pharo build available! The status of the build #221 was: SUCCESS. The Pull Request #384 was integrated: "20573-BaselineOfMorphic-should-include-System-Identification" Pull request url: https://github.com/pharo-project/pharo/pull/384 Issue Url: https://pharo.fogbugz.com/f/cases/20573 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Iceberg. Uncommited changes just after loading code from a repo?
by Thomas Dupriez Oct. 24, 2017

Oct. 24, 2017

Hello, After cloning a repo with Iceberg, loading the code and before doing any change, iceberg sees a lot of additions to the code in the "Synchronize Repository" window. Here are the steps I followed: - Load fresh Pharo7 image - Delete the previous clone of my repo in /home/dupriez/Pharo/vms/70-x86/pharo-local/iceberg (to start afresh) - Open Iceberg: Â Â Â - Click on "Clone Repository", to clone git@github.com:dupriezt/Calypso.git Â Â Â - Right-click on the repo in the list, Metacello/install baseline of Calypso (default) Â Â Â - Switch to dev branch, creating a local dev branch in the process as prompted Â Â Â - Without making any change, if I right-click on the Calypso repo in the list and click 'Synchronize Repository', there is a significant list of additions ready to be commited. Can someone shed some light on this? How can I get the code of the dev branch of this repo as is in my image? Cheers, Thomas Dupriez

1 0

[ANN] SeasideTesting recovered from oblivion
by Esteban Lorenzano Oct. 24, 2017

Oct. 24, 2017

Hi, I spend some days last week woking with the guys of AFI (http://afi-sa.fr <http://afi-sa.fr/>, yes they also use Pharo in some of their projects) and together we recovered SeasideTesting from Davis Shaffer to be used for their TDD experience. you can check it out here: https://github.com/Afibre/SeasideTesting <https://github.com/Afibre/SeasideTesting> Whatâs SeasideTesting? A package to test Seaside components. Why we do not use Parasol? Because it is based on selenium and that makes the process slow. Where can I know more? - there is some documentation here (for VW, I think): http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingCo… <http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingCo…> - some slides here (on squeak): http://esug.org/data/ESUG2005/Wednesday/2005-ESUG-Shaffer.pdf <http://esug.org/data/ESUG2005/Wednesday/2005-ESUG-Shaffer.pdf> but all that is old. Best way is to just install and see the tests, as always, cheers! Esteban

3 2

Re: [Pharo-dev] [Seaside] [ANN] SeasideTesting recovered from oblivion
by Johan Brichau Oct. 23, 2017

Oct. 23, 2017

I donât know... we maintained SeasideTesting at http://smalltalkhub.com/#!/~Seaside/SeasideTesting/ until we developed Parasol because it just covers some bare-bones html page testing. Forget about JavaScript and css influence on your tests in seaside testing. I think we prefer a slower but accurate testing proces, using Parasol. Johan > On 23 Oct 2017, at 22:22, Jon Paynter <kittle31(a)gmail.com> wrote: > > Great to hear! > > I use this on some older projects, and found the documentation helpful, but also sketchy. Hopefully you can update things. > > Will your resurected version work with Visualworks? > >> On Mon, Oct 23, 2017 at 3:04 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> I spend some days last week woking with the guys of AFI (http://afi-sa.fr, yes they also use Pharo in some of their projects) and together we recovered SeasideTesting from Davis Shaffer to be used for their TDD experience. >> >> you can check it out here: https://github.com/Afibre/SeasideTesting >> >> Whatâs SeasideTesting? A package to test Seaside components. >> Why we do not use Parasol? Because it is based on selenium and that makes the process slow. >> Where can I know more? >> - there is some documentation here (for VW, I think): http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingCo… >> - some slides here (on squeak): http://esug.org/data/ESUG2005/Wednesday/2005-ESUG-Shaffer.pdf >> but all that is old. Best way is to just install and see the tests, as always, >> >> >> cheers! >> Esteban >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

1 0

XPath chapter...
by Stephane Ducasse Oct. 23, 2017

Oct. 23, 2017

Hi I'm fully convinced that we can have the best language if we do not let people find their way super easily to do what they want to do we will fail. Documentation is KEY and I feel a bit alone. Since I always wanted to learn XPath I started to write a chapter on XPath. I hope that I did not write too many mistakes. Pull requests are welcome here https://github.com/SquareBracketAssociates/Booklet-Scraping I would love to have one booklet on SAX and DOM handling. Stef

7 11

[Pharo 7.0-dev] Build #220: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2017

Oct. 23, 2017

There is a new Pharo build available! The status of the build #220 was: SUCCESS. Could not extract further issue information from commit message: Should good to me. Like that we can have something symmetrical. Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0