November 2019 - Pharo-dev - lists.pharo.org

Integer #byteAt: #digitAt: portability
by Sven Van Caekenberghe Nov. 7, 2019

Nov. 7, 2019

Hi, Recently, #digitAt: was renamed to #byteAt: in Pharo 8. I totally agree that this is better. However, how does one write a library that needs to use this selector and wants portability with at least Pharo 7 ? That requires quite some effort from my side (either an ugly dynamic hack, or different source code packages, just for one method). Can we back port #byteAt: at least as an alias to Pharo 7 ? Sven

2 2

[Pharo 8.0] Build #951: 5073-HandMorphposition-is-not-safe
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2019

Nov. 7, 2019

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

1 0

[Pharo 8.0] Build #950: Compiler: Document Plugin AST copying
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #950 was: SUCCESS. The Pull Request #5065 was integrated: "Compiler: Document Plugin AST copying" Pull request url: https://github.com/pharo-project/pharo/pull/5065 Issue Url: https://github.com/pharo-project/pharo/issues/CompilerPluginCopy Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #949: 5062-includesKey-does-not-work-after-garbage-collect-in-WeakValueDictionary
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #949 was: FAILURE. The Pull Request #5067 was integrated: "5062-includesKey-does-not-work-after-garbage-collect-in-WeakValueDictionary" Pull request url: https://github.com/pharo-project/pharo/pull/5067 Issue Url: https://github.com/pharo-project/pharo/issues/5062 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #948: 5063-testInstSize-fails
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

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

1 0

[Pharo 8.0] Build #947: Kernel dependencies cleanup
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

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

1 0

[Pharo 8.0] Build #946: remove CrLfExchangeTable
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #946 was: SUCCESS. The Pull Request #5061 was integrated: "remove CrLfExchangeTable" Pull request url: https://github.com/pharo-project/pharo/pull/5061 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…

1 0

[Pharo 8.0] Build #945: Remove-Deprecated70
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #945 was: SUCCESS. The Pull Request #5006 was integrated: "Remove-Deprecated70" Pull request url: https://github.com/pharo-project/pharo/pull/5006 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…

1 0

[Pharo 8.0] Build #944: Prepare Epicea for latest Spec2
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #944 was: SUCCESS. The Pull Request #5057 was integrated: "Prepare Epicea for latest Spec2" Pull request url: https://github.com/pharo-project/pharo/pull/5057 Issue Url: https://github.com/pharo-project/pharo/issues/5056 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #943: Fix-protocol-and-remove-useless-method
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #943 was: SUCCESS. The Pull Request #5055 was integrated: "Fix-protocol-and-remove-useless-method" Pull request url: https://github.com/pharo-project/pharo/pull/5055 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…

1 0

[Pharo 8.0] Build #942: type-for-the-entries-is-not-a-good-name
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #942 was: SUCCESS. The Pull Request #5058 was integrated: "type-for-the-entries-is-not-a-good-name" Pull request url: https://github.com/pharo-project/pharo/pull/5058 Issue Url: https://github.com/pharo-project/pharo/issues/type Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #941: Completion: Sorter should be Instance
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

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

1 0

[Pharo 8.0] Build #940: 2282-ProcessorScheduler-method-comment-refers-to-DelayScheduler-class-comment
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2019

Nov. 6, 2019

There is a new Pharo build available! The status of the build #940 was: FAILURE. The Pull Request #5053 was integrated: "2282-ProcessorScheduler-method-comment-refers-to-DelayScheduler-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/5053 Issue Url: https://github.com/pharo-project/pharo/issues/2282 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #939: 2283-WorldState-refers-to-missing-class-DelayScheduler
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2019

Nov. 5, 2019

There is a new Pharo build available! The status of the build #939 was: SUCCESS. The Pull Request #5054 was integrated: "2283-WorldState-refers-to-missing-class-DelayScheduler" Pull request url: https://github.com/pharo-project/pharo/pull/5054 Issue Url: https://github.com/pharo-project/pharo/issues/2283 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #938: Use-platform-visitor-in-native-browser
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2019

Nov. 5, 2019

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

1 0

Pharo 7 Release Update
by Sven Van Caekenberghe Nov. 5, 2019

Nov. 5, 2019

Hi, As reported (by Jonathan and checked by me), the launcher now creates an Pharo 7.0 images from version Pharo7.0.4 build: 172, commit: ecc855d. This build correctly loads the Zinc baseline ! This is very good news. Thanks again Pablo. Now this version has to be released so that it is served by the ZeroConf tools (get.pharo.org) which is a manual process, IIUC. Do we have to go to 7.0.5 ? Can someone do the necessary steps please ? Sven

2 1

[Pharo 8.0] Build #937: FileSystem>>copyFileAndDelete:to: don't raise a FileDoesNotExistException if the destination doesn't exist
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2019

Nov. 5, 2019

There is a new Pharo build available! The status of the build #937 was: FAILURE. The Pull Request #5041 was integrated: "FileSystem>>copyFileAndDelete:to: don't raise a FileDoesNotExistException if the destination doesn't exist" Pull request url: https://github.com/pharo-project/pharo/pull/5041 Issue Url: https://github.com/pharo-project/pharo/issues/copyFileAndDeleteto Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #936: close all windows like this
by ci-pharo-ci-jenkins2＠inria.fr Nov. 4, 2019

Nov. 4, 2019

There is a new Pharo build available! The status of the build #936 was: SUCCESS. The Pull Request #5046 was integrated: "close all windows like this" Pull request url: https://github.com/pharo-project/pharo/pull/5046 Issue Url: https://github.com/pharo-project/pharo/issues/toolbar Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #935: 4829-SugsNautilusContext-can-be-removed
by ci-pharo-ci-jenkins2＠inria.fr Nov. 4, 2019

Nov. 4, 2019

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

1 0

[Pharo 8.0] Build #934: Cleanup: #wantsRecompilationProgressReported
by ci-pharo-ci-jenkins2＠inria.fr Nov. 4, 2019

Nov. 4, 2019

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

1 0

[Pharo 8.0] Build #933: Completion: use #hasEntries instead of isEmpty/notEmpty
by ci-pharo-ci-jenkins2＠inria.fr Nov. 4, 2019

Nov. 4, 2019

There is a new Pharo build available! The status of the build #933 was: SUCCESS. The Pull Request #5047 was integrated: "Completion: use #hasEntries instead of isEmpty/notEmpty" Pull request url: https://github.com/pharo-project/pharo/pull/5047 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionHasEntries Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Git URL issues
by Sven Van Caekenberghe Nov. 4, 2019

Nov. 4, 2019

Hi, I asked this before, but I still have trouble with this. What I ultimately want is what I used for years now: use the zero config tools to point to my private repo and install my code and all its dependencies from a single Metacello config. Basically, $vm $image config _CONFIG_REPO_ _CONFIG_NAME_ --username=_CONFIG_USER_ --password=_CONFIG_PASS_ --install=_CONFIG_VERSION_ --group=_CONFIG_GROUP_ towards a private server. In the new world of git(hub)/tonel/iceberg I am trying the following (not using the 'config' but the new 'metacello' command line handler): $ uname -a Linux audio359 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ curl get.pharo.org/64/70+vm | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3054 100 3054 0 0 57622 0 --:--:-- --:--:-- --:--:-- 57622 Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo64.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/get-files/70/pharo64-linux-stable.zip pharo-vm/pharo Creating starter scripts pharo and pharo-ui $ ./pharo Pharo.image printVersion [version] 'Pharo7.0.4' 'Pharo-7.0.4+build.168.sha.ccd1f6489120f58ddeacb2cac77cd3a0f0dcfbe6 (64 Bit)' $ ./pharo Pharo.image save build $ ./pharo build.image metacello install github://svenvc/ztimestamp BaselineOfZTimestamp 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) I will try to clone the HTTPS variant. Fetched -> BaselineOfZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- https://github.com/svenvc/ztimestamp.git[master] Loaded -> BaselineOfZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- https://github.com/svenvc/ztimestamp.git[master] Loading baseline of BaselineOfZTimestamp... Fetched -> ZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- https://github.com/svenvc/ztimestamp.git[master] Loaded -> ZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- cache ...finished baseline $ ./pharo build.image eval ZTimestamp now 2019-10-25T12:28:34Z So although it gave a warning, it worked fine. The warning said, using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) I will try to clone the HTTPS variant. so let's try that after cleaning everything: $ rm -rf pharo-local/ build.* $ ./pharo Pharo.image save build $ ./pharo build.image metacello install https://github.com/svenvc/ztimestamp.git BaselineOfZTimestamp ...RETRY->BaselineOfZTimestamp ...RETRY->BaselineOfZTimestamp ...FAILED->BaselineOfZTimestampCould not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /home/sven/pharo7/pharo-local/package-cache https://github.com/svenvc/ztimestamp.git MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: WTF ? Why does this not work (I can perfectly git clone that URL) ? Of course, this would just be the first step, eventually I want to use my own private server with a URL like https://deploy:secret@bitbucket.myserver.be/scm/xyz/xyz-pharo.git How do you build/deploy non-public production code using the command line ? Help would be much appreciated. Sven

4 12

I love this idea: learning by doing...
by ducasse Nov. 3, 2019

Nov. 3, 2019

https://github.com/danistefanovic/build-your-own-x I would love to get some pharo there. Thanks sebastian for the pointer. Stef

2 2

[Pharo 8.0] Build #932: Put each executable comment in its own comment
by ci-pharo-ci-jenkins2＠inria.fr Nov. 3, 2019

Nov. 3, 2019

There is a new Pharo build available! The status of the build #932 was: SUCCESS. The Pull Request #5045 was integrated: "Put each executable comment in its own comment" Pull request url: https://github.com/pharo-project/pharo/pull/5045 Issue Url: https://github.com/pharo-project/pharo/issues/executable_comments Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #931: 3695-Epicea-shows-a-Change-that-is-not-a-change
by ci-pharo-ci-jenkins2＠inria.fr Nov. 2, 2019

Nov. 2, 2019

There is a new Pharo build available! The status of the build #931 was: SUCCESS. The Pull Request #4996 was integrated: "3695-Epicea-shows-a-Change-that-is-not-a-change" Pull request url: https://github.com/pharo-project/pharo/pull/4996 Issue Url: https://github.com/pharo-project/pharo/issues/3695 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #930: Spec based find & replace dialog
by ci-pharo-ci-jenkins2＠inria.fr Nov. 2, 2019

Nov. 2, 2019

There is a new Pharo build available! The status of the build #930 was: SUCCESS. The Pull Request #5042 was integrated: "Spec based find & replace dialog" Pull request url: https://github.com/pharo-project/pharo/pull/5042 Issue Url: https://github.com/pharo-project/pharo/issues/findReplace1 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #929: executable comments
by ci-pharo-ci-jenkins2＠inria.fr Nov. 2, 2019

Nov. 2, 2019

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

1 0

[Pharo 7.0] Build #172: 4764-Change-is-ZnBuffered-are-breaking-something-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 2, 2019

Nov. 2, 2019

There is a new Pharo build available! The status of the build #172 was: FAILURE. The Pull Request #5030 was integrated: "4764-Change-is-ZnBuffered-are-breaking-something-" Pull request url: https://github.com/pharo-project/pharo/pull/5030 Issue Url: https://pharo.fogbugz.com/f/cases/4764 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #928: Executable comments
by ci-pharo-ci-jenkins2＠inria.fr Nov. 2, 2019

Nov. 2, 2019

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

1 0

[Pharo 8.0] Build #927: exacutable comments for asBit method
by ci-pharo-ci-jenkins2＠inria.fr Nov. 2, 2019

Nov. 2, 2019

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

1 0

Re: [Pharo-dev] FOSDEM rooms are available
by Santiago Bragagnolo Nov. 1, 2019

Nov. 1, 2019

Hi Offray!! I have no clue if there are scholarships. To be honest i don't think so, since it is completely free. but still, don't take my word. Check it. I can do some research on it tomorrow. If not the case, we can do the proposal together, and if they accept the talk we do an intensive couching / course and i present it :) El miÃ©., 30 oct. 2019 a las 0:02, Offray Vladimir Luna CÃ¡rdenas (< offray.luna(a)mutabit.com>) escribiÃ³: > > On 29/10/19 4:24 a. m., Santiago Bragagnolo wrote: > > > [...] > > *Communication *( > https://fosdem.org/2020/schedule/track/collaborative_information_and_conten… > https://fosdem.org/2020/schedule/track/coding_for_language_communities/ ) > *Offray*! I think there is space for graphoscope in here. If you can > give a talk, great, if not, i propose my self to be the speaker (of course > in that case i will need some couching and teaching on the usage). > > I will love to be in Brussels for early February to give the talk, but if > the event has no scholarships or travel funding, I can couch you about what > we have being doing with Grafoscopio since 2015 and giving some overview of > explanatory materials including the mind maps, projects, prototypes, and > docs I use for the presentations. > > Thanks for keeping and eye on this and thinking in the way the wider > community can participate on this, > > Offray > >

2 2

Re: [Pharo-dev] FOSDEM rooms are available
by Santiago Bragagnolo Nov. 1, 2019

Nov. 1, 2019

Offray! Here a link for submitting the talk. I think is better if you do it your self. Like that you get in touch with the organisers and you can ask directly about any possible scholarship. https://penta.fosdem.org/submission/FOSDEM20 El miÃ©., 30 oct. 2019 a las 0:02, Offray Vladimir Luna CÃ¡rdenas (< offray.luna(a)mutabit.com>) escribiÃ³: > > On 29/10/19 4:24 a. m., Santiago Bragagnolo wrote: > > > [...] > > *Communication *( > https://fosdem.org/2020/schedule/track/collaborative_information_and_conten… > https://fosdem.org/2020/schedule/track/coding_for_language_communities/ ) > *Offray*! I think there is space for graphoscope in here. If you can > give a talk, great, if not, i propose my self to be the speaker (of course > in that case i will need some couching and teaching on the usage). > > I will love to be in Brussels for early February to give the talk, but if > the event has no scholarships or travel funding, I can couch you about what > we have being doing with Grafoscopio since 2015 and giving some overview of > explanatory materials including the mind maps, projects, prototypes, and > docs I use for the presentations. > > Thanks for keeping and eye on this and thinking in the way the wider > community can participate on this, > > Offray > >

1 0