- Pharo-dev - lists.pharo.org

Reviewing Changes ?
by Sven Van Caekenberghe Feb. 8, 2018

Feb. 8, 2018

Hi, With pull requests, it is relatively easy to see what changed in GitHub. Eg. Marcus' latest fix: https://github.com/pharo-project/pharo/pull/797 shows 6 files/classes changed, reasonably readable diff. How does one review such a PR in an image, to test it out ? Has someone written a guide on how to do this best/most-easily ? How is/can this be related to contributing ? Sven

7 12

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?
by Sven Van Caekenberghe Feb. 8, 2018

Feb. 8, 2018

Starting/restarting with a running server in the image works OK for me (macOS) and recent Pharo 7. What is different for you ? > On 8 Feb 2018, at 12:51, Maximiliano Tabacman via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Maximiliano Tabacman <mtabacman(a)yahoo.com> > Subject: Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ? > Date: 8 February 2018 at 12:51:15 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Up until Pharo build 382 (sha 115e95c) you could load Seaside by using: > Metacello new > > > baseline:'Seaside3' > ; > > repository: 'github://SeasideSt/Seaside:master/repository' > ; > load > > If you adapt the baselineOf to include Pharo 7.x > > BUT, from build 383 onwards, and tested again just now with 509 (sha 1276a3f) the following happens: > - Download Pharo -- OK > - Load Seaside master -- OK > - Save and quit image -- OK > - Start image again -- Hangs and never completes starting > > In Ubuntu, this manifests as the main Pharo window opening, but never displaying anything inside it. > In Windows, the VM starts and closes without any warning, and no logs are created. > > I have no idea why this is happening, and I am not sure if the tests in Travis cover this scenario. > On Wednesday, February 7, 2018, 4:14:24 PM GMT-3, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > Thanks for pushing this. > I plan to work on migrating the seaside book to pillar when I'm done > with the moose book and the magritte booklet. > > Stef > > On Wed, Feb 7, 2018 at 1:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > > > Using [ https://github.com/SeasideSt/Seaside/pull/979 ] (I attach a manually modified BaselineOfSeaside3 that I used), I managed to load Seaside 3.2 (GitHub.1516790362) in Pharo 7 (Pharo-7.0+alpha.build.493.sha.d53a70bc946ed83b046f61ac35f00c67fa77269a (32 Bit)) and at least the load and some quick testing with ZnZincSeasideAdaptor (via the spec based Seaside Control Panel) seems to indicate no direct problems. > > > > Metacello new > > baseline:'Seaside3'; > > repository: 'github://SeasideSt/Seaside:master/repository'; > > load. > > > > Why don't we integrate this so that others can load Seaside 3.2 in Pharo 7 too ? > > > > This is _really_ important to make progress, IMHO. > > > > I changed WABrowser>>#updateUrl: to send #name instead of #fullName to the selected class of the model. I am not sure that is entirely correct, but it seemed to work. Apart from that, the WAImageStatus web app worked fine. > > > > Sven > > > >> On 6 Nov 2017, at 09:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> OK, Max, thanks for the reply. > >> > >> I will ask on the Pharo ML as well. > >> > >> I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well. > >> > >>> On 6 Nov 2017, at 09:40, Max Leske <maxleske(a)gmail.com> wrote: > >>> > >>> Hi Sven, > >>> > >>> We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend. > >>> > >>> How urgent is the situation for you? > >>> > >>> Cheers, > >>> Max > >>> > >>> > >>> On 5 November 2017 at 19:22:03, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: > >>> > >>>> Hi, > >>>> > >>>> I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency: > >>>> > >>>> project: 'Bootstrap' with: [ > >>>> spec > >>>> className: 'ConfigurationOfBootstrap'; > >>>> repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; > >>>> versionString: #stable ] > >>>> > >>>> I also tried the following: > >>>> > >>>> Metacello new > >>>> baseline:'Seaside3'; > >>>> repository: 'github://SeasideSt/Seaside:master/repository'; > >>>> load. > >>>> > >>>> What is the right/recommended way to do it ? > >>>> > >>>> Thx, > >>>> > >>>> Sven > >>>> > >>>> _______________________________________________ > >>>> seaside-dev mailing list > >>>> seaside-dev(a)lists.squeakfoundation.org > >>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > >>> _______________________________________________ > >>> seaside-dev mailing list > >>> seaside-dev(a)lists.squeakfoundation.org > >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > >> > > > > > >

1 0

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?
by Sven Van Caekenberghe Feb. 8, 2018

Feb. 8, 2018

Hi, Using [ https://github.com/SeasideSt/Seaside/pull/979 ] (I attach a manually modified BaselineOfSeaside3 that I used), I managed to load Seaside 3.2 (GitHub.1516790362) in Pharo 7 (Pharo-7.0+alpha.build.493.sha.d53a70bc946ed83b046f61ac35f00c67fa77269a (32 Bit)) and at least the load and some quick testing with ZnZincSeasideAdaptor (via the spec based Seaside Control Panel) seems to indicate no direct problems. Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load. Why don't we integrate this so that others can load Seaside 3.2 in Pharo 7 too ? This is _really_ important to make progress, IMHO. I changed WABrowser>>#updateUrl: to send #name instead of #fullName to the selected class of the model. I am not sure that is entirely correct, but it seemed to work. Apart from that, the WAImageStatus web app worked fine. Sven > On 6 Nov 2017, at 09:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > OK, Max, thanks for the reply. > > I will ask on the Pharo ML as well. > > I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well. > >> On 6 Nov 2017, at 09:40, Max Leske <maxleske(a)gmail.com> wrote: >> >> Hi Sven, >> >> We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend. >> >> How urgent is the situation for you? >> >> Cheers, >> Max >> >> >> On 5 November 2017 at 19:22:03, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: >> >>> Hi, >>> >>> I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency: >>> >>> project: 'Bootstrap' with: [ >>> spec >>> className: 'ConfigurationOfBootstrap'; >>> repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; >>> versionString: #stable ] >>> >>> I also tried the following: >>> >>> Metacello new >>> baseline:'Seaside3'; >>> repository: 'github://SeasideSt/Seaside:master/repository'; >>> load. >>> >>> What is the right/recommended way to do it ? >>> >>> Thx, >>> >>> Sven >>> >>> _______________________________________________ >>> seaside-dev mailing list >>> seaside-dev(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >

3 3

Improve "Senders of"
by Marcus Denker Feb. 8, 2018

Feb. 8, 2018

Hi, I tried to improve the âsenders ofâ behaviour in the case where you just put a selector (e.g. in the playground). needs some testing: https://pharo.fogbugz.com/f/cases/21251/Improve-Senders-of <https://pharo.fogbugz.com/f/cases/21251/Improve-Senders-of> https://github.com/pharo-project/pharo/pull/810 <https://github.com/pharo-project/pharo/pull/810> Marcus

1 0

Iceberg - creating virgin repos
by Ben Coman Feb. 8, 2018

Feb. 8, 2018

If in the System Browser I do <Add Package...> and work a bit on it, then later want to push it to a new github repo, what is the recommended procedure? As a rough guess I tried the "New repository" button, then added the package and a remote, but then trying to push gives me an error... LGit_GIT_EUNBORNBRANCH: Reference 'refs/heads/master' not found At the moment I've only had success first creating the repo on github, then cloning it - so I/m not sure how the "New repository" button is useful. cheers -ben

2 1

How to force a BaselineOf to load ?
by Sven Van Caekenberghe Feb. 8, 2018

Feb. 8, 2018

Hi, I have a Pharo 4 (#40627) image that already contains P3. Now I want to update P3, without completely rebuilding this image from scratch. It seems as if an expression like Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load. executed like $ ../bin/pharo build-trackit.image eval --save "Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load" does not really reload the code. How can I force it to (re)load ? Thx, Sven

2 2

[Pharo 7.0-dev] Build #509: 20254-Playground-should-ask-to-create-class-for-non-Existing-Globals
by ci-pharo-ci-jenkins2＠inria.fr Feb. 7, 2018

Feb. 7, 2018

There is a new Pharo build available! The status of the build #509 was: SUCCESS. The Pull Request #806 was integrated: "20254-Playground-should-ask-to-create-class-for-non-Existing-Globals" Pull request url: https://github.com/pharo-project/pharo/pull/806 Issue Url: https://pharo.fogbugz.com/f/cases/20254 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

another file reference question
by Stephane Ducasse Feb. 7, 2018

Feb. 7, 2018

HI I have the following scenario: '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' asFileReference / 'book.pillar' >>> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" ok it works. I want to update the contents of a target folder only if a file is missing or too old compared to a source. The idea is that I have a target folder and I need to know if a file located in the source tree should be copied under the target. So I compute the difference from the root of the source to the file and I want to apply this path to the target to check some file properties. now I do not understand how I can get the following working: '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' asFileReference / ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/book.pillar' asFileReference path) relativeTo: ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo' asFileReference path) Stef

3 8

[Pharo 7.0-dev] Build #508: 21248-Add-possibility-to-skip-some-tests-on-CI
by ci-pharo-ci-jenkins2＠inria.fr Feb. 7, 2018

Feb. 7, 2018

There is a new Pharo build available! The status of the build #508 was: SUCCESS. The Pull Request #808 was integrated: "21248-Add-possibility-to-skip-some-tests-on-CI" Pull request url: https://github.com/pharo-project/pharo/pull/808 Issue Url: https://pharo.fogbugz.com/f/cases/21248 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #507: 21247--TraitMethodDescription-is-missing-isNotEmpty
by ci-pharo-ci-jenkins2＠inria.fr Feb. 7, 2018

Feb. 7, 2018

There is a new Pharo build available! The status of the build #507 was: FAILURE. The Pull Request #807 was integrated: "21247--TraitMethodDescription-is-missing-isNotEmpty" Pull request url: https://github.com/pharo-project/pharo/pull/807 Issue Url: https://pharo.fogbugz.com/f/cases/21247 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0