December 2018 - Pharo-dev - lists.pharo.org

[ANN] Pharo Newsletter December 2018
by Marcus Denker Dec. 13, 2018

Dec. 13, 2018

Hi, Last we the Pharo Newsletter December 2018 was send. You can find the archived version now here: https://mailchi.mp/pharo/pharo-newsletter-december-2018 Marcus

2 2

[ANN] Git Thermite integration with Iceberg
by Ronie Salgado Dec. 12, 2018

Dec. 12, 2018

Hello, Some time ago I presented Git Thermite in this mailing. Git Thermite is a tool for visualizing Git commits that I am making for my master thesis. Now I have managed to integrate Git Thermite with Iceberg. GitHub page: https://github.com/ronsaldo/pharo-git-thermite Demo video: https://www.youtube.com/watch?v=TdBHpdyFgZE Visualization learning material: https://github.com/ronsaldo/pharo-git-thermite/blob/master/doc/learning-mat… Feedback: https://docs.google.com/forms/d/e/1FAIpQLSeir6VlE3bR78oRsNAp9eHLkUn2Q016wEl… Pharo 7 installation doIt: Metacello new baseline: 'Thermite'; repository: 'github://ronsaldo/pharo-git-thermite/src'; load Please, I would love to get some usage feedback through the Google form :-) Best regards, Ronie

2 1

[Pharo 7.0] Build #34: 22753-RBParseErrorNode-should-pretty-print-the-faulty-text-if-it-has-it
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #34 was: SUCCESS. The Pull Request #2061 was integrated: "22753-RBParseErrorNode-should-pretty-print-the-faulty-text-if-it-has-it" Pull request url: https://github.com/pharo-project/pharo/pull/2061 Issue Url: https://pharo.fogbugz.com/f/cases/22753 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #33: 22755-Reflectivity-cleanups-tests-unify-variable-Naming
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #33 was: SUCCESS. The Pull Request #2063 was integrated: "22755-Reflectivity-cleanups-tests-unify-variable-Naming" Pull request url: https://github.com/pharo-project/pharo/pull/2063 Issue Url: https://pharo.fogbugz.com/f/cases/22755 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #32: 22750-Add-GTPlayground-classopenUrl
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

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

1 0

Multiline method definition in Tonel
by Mariano Martinez Peck Dec. 12, 2018

Dec. 12, 2018

Hi guys, I was reading the Tonel spec here [1] but it is not clear to me the case of the multiline method definitions. Are those allowed or not? Say I have a method like this: testWith: arg1 with: arg2 with: arg3 ^ 42 Is that valid as Tonel format? Or tonel expects to have method definition in a one liner like: testWith: arg1 with: arg2 with: arg3 ^ 42 Thanks in advance, [1] https://github.com/pharo-vcs/tonel -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

4 4

Fixed by reboot
by Ben Coman Dec. 12, 2018

Dec. 12, 2018

Just reporting a strange occurrence in case anyone sees the same. I was using PharoLauncher fine, then it wasn't. When trying to launch an image it started reporting with "ProcessWrapper newProcess failed..." First time I've ever seen that, and fixed by a reboot, but still strange. There are a couple of other troubles that get fixed by reboot. Anyone have insight into an underlying cause? cheers -ben

3 3

[Pharo 7.0] Build #31: 22752-cleanup-preamble-generation--test-for-method-Sequence
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #31 was: FAILURE. The Pull Request #2060 was integrated: "22752-cleanup-preamble-generation--test-for-method-Sequence" Pull request url: https://github.com/pharo-project/pharo/pull/2060 Issue Url: https://pharo.fogbugz.com/f/cases/22752 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

OSSubprocess equivalent in Pharo7?
by Hans-Martin Dec. 12, 2018

Dec. 12, 2018

Hello, I noticed that theOSSubprocess functionality for communicating with OS subprocesses depends on OSSAttachableFileStream which is a subclass of deprecated FileStream (incidentally, the project is not marked as being compatible with Pharo7). The popen()/fgetc() based examples in UNIXProcess are blocking, which is unusable for any but the most basic external command executions. Are there plans to implement a proper replacement in Pharo7? Cheers, Hans-Martin -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 7.0] Build #30: 22742 Package ManifestHiedra should be tagged
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #30 was: SUCCESS. The Pull Request #2051 was integrated: "22742 Package ManifestHiedra should be tagged" Pull request url: https://github.com/pharo-project/pharo/pull/2051 Issue Url: https://pharo.fogbugz.com/f/cases/22742 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Pharo FIleSystem Compatibility with Gemstone's FileSystemGs
by Guillermo Polito Dec. 12, 2018

Dec. 12, 2018

Hi Reg, Thanks for your email, improving FileSystem is a cool thing ^^. On Tue, Dec 11, 2018 at 8:39 PM Reg Krock via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hi, > > I am working on making changes to FileSystemGs to make it work in Gemstone. > > Who is or the the persons to talk to about changes on the Pharo side. > Well, I don't know if there is a single maintainer. I think that myself, Alistair, Sven, and many others can answer to questions on different aspects of file system. Anyways, I'd suggest you just send your emails to this mailing list, the person concerned/interested will answer when possible ;) > > Areas of exploration to date have been: > > 1. Replacement of File with GsFile - in Gemstone we want to use the > native file class. > > How have you made it pluggable? This maybe requires the introduction of a backend or a separate store "GSFileSystemStore"? Does Gemstone require different kind of implementations for different platforms like linux/windows/osx or just a unix-like one is enough? > > 1. Introduction of a FileMode class hierarchy to replace the passing > of they symbols #read and #write. > - Added the proof of concept of FileMode with subclasses to be > passed instead of #write and #read. The classes which have been introduced > are: > > > FileMode > FileAppendMode > FileAppendAndReadMode > FileAppendAndReadBinaryMode > FileAppendBinaryMode > FileReadMode > FileReadBinaryMode > FileReadWriteMode > FileReadWriteMode > FileReadWriteBinaryMode > FileReadWriteTruncatedMode > FileReadWriteTruncatedBinaryMode > FileWriteMode > FileWriteBinaryMode > I like the introduction of objects :) What is the difference between the binary and non binary modes? How do you specify encoding for non binary ones? Or you assume ascii? Also, the fact that the "binary" aspect is repeated all over the hierarchy makes me think they could be composable aspects of a file mode. > > - These classes return the appropriate mode string, (ex: âw+â) and > know if the file is writable.Example of change - the text in blue shows the > change. > > > Exiting format: > (filesystem open: aFileReference path writable: #write) > Well, AFAIU, this is not public API (and it uses booleans to indicate "mode"). Usually end users would simply do: aFileReference writeStream. aFileReference binaryWriteStream. aFileReference readStream. aFileReference binaryReadStream. But yes, I like also to model modes such as truncated, append, "force new". > Proposed format: > (filesystem open: aFileReference path writable: self store > readWriteTruncatedMode) > > The #readWriteTruncatedMode method would return an instance of > FileReadWriteTruncatedMode > > If a form of this proposal were to be adopted, then the appropriate > methods should be renamed to have mode. > As an example, #open:writeable: would become #open:mode: > Well, we could keep the old API and build a higher level one on top, don't we? Do you have your code in a repository we could check? > Thanks for your help. > Thanks to you! Guille > Reg >

2 1

[ANN] Next Pharo Sprint: Dec 21
by Marcus Denker Dec. 12, 2018

Dec. 12, 2018

We will organize a Pharo sprint / Moose dojo Dec 21, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973628

1 0

[Pharo 7.0] Build #29: 22751-Improve-RFLiteralVariableNode-printing
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

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

1 0

[Pharo 7.0] Build #28: 22703-Block-execution-arguments-reification
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #28 was: SUCCESS. The Pull Request #2059 was integrated: "22703-Block-execution-arguments-reification" Pull request url: https://github.com/pharo-project/pharo/pull/2059 Issue Url: https://pharo.fogbugz.com/f/cases/22703 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #27: 22736-Clean-PharoWelcomePage
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #27 was: SUCCESS. The Pull Request #2047 was integrated: "22736-Clean-PharoWelcomePage" Pull request url: https://github.com/pharo-project/pharo/pull/2047 Issue Url: https://pharo.fogbugz.com/f/cases/22736 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Playground "remote publish" feedback from discord
by Ben Coman Dec. 11, 2018

Dec. 11, 2018

On discord a user provided some feedback... when you post anything to ws.stfx.eu - e.g. here: http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use "ZnWorkspace openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it. However, there is no class called "ZnWorkspace" in Pharo 6.1 so this should probably be updated. "Remote publish" button is located fairly prominently in the top right corner of Pharo Playground window so Pharo beginners will probably see it fairly soon after they start experimenting and try clicking on it. The text should be updated so the instructions actually work. Also the footer of the page says copyright is 2013, and it would look better to newcomers if the copyright date was more recent. ---------- cheers -ben

2 6

Pharo FIleSystem Compatibility with Gemstone's FileSystemGs
by Reg Krock Dec. 11, 2018

Dec. 11, 2018

Hi, I am working on making changes to FileSystemGs to make it work in Gemstone. Who is or the the persons to talk to about changes on the Pharo side. Areas of exploration to date have been: Replacement of File with GsFile - in Gemstone we want to use the native file class. Introduction of a FileMode class hierarchy to replace the passing of they symbols #read and #write. Added the proof of concept of FileMode with subclasses to be passed instead of #write and #read. The classes which have been introduced are: FileMode FileAppendMode FileAppendAndReadMode FileAppendAndReadBinaryMode FileAppendBinaryMode FileReadMode FileReadBinaryMode FileReadWriteMode FileReadWriteMode FileReadWriteBinaryMode FileReadWriteTruncatedMode FileReadWriteTruncatedBinaryMode FileWriteMode FileWriteBinaryMode These classes return the appropriate mode string, (ex: âw+â) and know if the file is writable.Example of change - the text in blue shows the change. Exiting format: (filesystem open: aFileReference path writable: #write) Proposed format: (filesystem open: aFileReference path writable: self store readWriteTruncatedMode) The #readWriteTruncatedMode method would return an instance of FileReadWriteTruncatedMode If a form of this proposal were to be adopted, then the appropriate methods should be renamed to have mode. As an example, #open:writeable: would become #open:mode: Thanks for your help. Reg

1 0

[Pharo 7.0] Build #26: 22741 Cleanups for SystemVersionTest (lint)
by ci-pharo-ci-jenkins2＠inria.fr Dec. 11, 2018

Dec. 11, 2018

There is a new Pharo build available! The status of the build #26 was: FAILURE. The Pull Request #2050 was integrated: "22741 Cleanups for SystemVersionTest (lint)" Pull request url: https://github.com/pharo-project/pharo/pull/2050 Issue Url: https://pharo.fogbugz.com/f/cases/22741 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Tonel>>sourceDir
by Ben Coman Dec. 11, 2018

Dec. 11, 2018

For Exercism we are using Tonel in Pharo 6.1. We are getting an error "Instance of TonelWriter did not understand #sourceDir:" but the same code works fine on Pharo 7. The 6.1 image had been updated to latest Iceberg per https://github.com/pharo-vcs/iceberg#for-pharo-61, so I used ICeberg to updated to latest "master" of pharo-vcs/tonel but no avail. In Pharo 7 I see TonelWriter>>sourceDir in protocol "accessing" but if I search for "sourceDir" in the pharo-vcs/tonel repo it doesn't find it... https://github.com/pharo-vcs/tonel/search?q=sourcedir&unscoped_q=sourcedir I'm having trouble understanding where the #sourceDir method comes from in Pharo 7. Which repo/branch can I load that from into another system? cheers -ben

4 7

[Pharo 7.0] Build #25: 22735-ZipArchive-classisZipArchive-is-broken-in-P7
by ci-pharo-ci-jenkins2＠inria.fr Dec. 10, 2018

Dec. 10, 2018

There is a new Pharo build available! The status of the build #25 was: SUCCESS. The Pull Request #2046 was integrated: "22735-ZipArchive-classisZipArchive-is-broken-in-P7" Pull request url: https://github.com/pharo-project/pharo/pull/2046 Issue Url: https://pharo.fogbugz.com/f/cases/22735 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: halos
by John Kimber Dec. 10, 2018

Dec. 10, 2018

shift-control click works for me on 1384. HTH, john -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

Esteban's ChangeLog week of 3 December 2018
by estebanlm＠gmail.com Dec. 10, 2018

Dec. 10, 2018

Hello! This is my weekly ChangeLog, from 3 December 2018 to 9 December 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=3/12/2018&to=9/12/2018 ChangeLog ========= 6 December 2018: ---------------- * I made a small [PR](https://github.com/pharo-ide/Calypso/pull/375) on Calypso to better expose the contextual spotter that helps to find available Calypso commands. 5 December 2018: ---------------- * Ok, finally I finished next stop on automation of releases, which made us to change the default development branch (to "Pharo7.0" for the moment). This will allow us to keep different active "development" branches. One thing I would like to achieve eventually is to keep: * A current development version (it will be Pharo8.0 soon). * A maintained stable version (Pharo7.0 and potential Pharo7.1, etc.). * A Long term support (LTS) version that will continue incorporating critic systems. So well, this are the steps to arrive there :) cheers! Esteban

1 0

Calypso equivalent <nautilusGlobalPackageMenu>
by Ben Coman Dec. 9, 2018

Dec. 9, 2018

What is the Calypso equivalent of <nautilusGlobalPackageMenu> ? I need to add an extra menu item to the Packages context menu. cheers -ben

2 1

Release candidate version numbers
by Ben Coman Dec. 9, 2018

Dec. 9, 2018

In PharoLauncher under "Pharo 7 (development version)" opening template Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit then System > System Report shows... Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227d22bc32f1c4e93b710 (32 Bit) but under "Official distributions" I see Pharo 7.0 - 32bit (development version) then System > System Report shows... Pharo-7.0.0+rc1.build.24.sha.41c89eb7dd9f362ca1ba874f1d9a42602396e002 (32 Bit) Why using such a different and small number "24", and a long way from 1433 ? cheers -ben

2 2

Which version of libfreetype.dll?
by Alistair Grant Dec. 7, 2018

Dec. 7, 2018

Hi Esteban, If I zeroconf Pharo 7 on Windows (in cygwin): $ curl get.pharo.org/70+vmLatest | bash And then move to a dos box: C:\cygwin\tmp\p7>pharo-vm\PharoConsole.exe --headless Pharo.image eval "FT2Library current libraryVersion" 2.6.5 Is this what you expect? Thanks, Alistair

1 0

[Pharo 7.0] Build #24: 22738-Remove-Window-color-option
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2018

Dec. 7, 2018

There is a new Pharo build available! The status of the build #24 was: SUCCESS. The Pull Request #2048 was integrated: "22738-Remove-Window-color-option" Pull request url: https://github.com/pharo-project/pharo/pull/2048 Issue Url: https://pharo.fogbugz.com/f/cases/22738 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #23: 22740 system settings should be system settings core
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2018

Dec. 7, 2018

There is a new Pharo build available! The status of the build #23 was: SUCCESS. The Pull Request #2049 was integrated: "22740 system settings should be system settings core" Pull request url: https://github.com/pharo-project/pharo/pull/2049 Issue Url: https://pharo.fogbugz.com/f/cases/22740 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Fwd: Announcing Repl.it Multiplayer
by Santiago Bragagnolo Dec. 7, 2018

Dec. 7, 2018

Would this be interesting to have in pharo?? What do you think? ---------- Forwarded message --------- From: Amjad from Repl.it <contact(a)repl.it> Date: jue., 6 de dic. de 2018 21:55 Subject: Announcing Repl.it Multiplayer To: <santiagobragagnolo(a)gmail.com> The official release of Repl.it Multiplayer, the collaborative coding experience. [image: Repl.it Logo] <http://url1361.repl.it/wf/click?upn=LLQySNMYKcsdrD3Xpw6uy0-2F0rOvSNWPLVoxcc…> Hey Santiago, Professional programmers all know that software development is a fundamentally social experience. But coding remains a single-player experience by default â today, we're changing this! As part of our mission to make computing more accessible, we believe connecting coders, learners, and teachers together in real time, in the development environment, is a big piece of the puzzle. That's why we're proud to announce *Multiplayer*. Multiplayer lets you code with friends in the same editor, execute programs in the same interpreter, interact with the same terminal, chat in the IDE, edit files and share the same system resources, and ship applications from the same interface! We've redesigned every part of our infrastructure to work in multiplayer mode -- from the filesystem to the interpreter. [image: Repl.it Multiplayer] <http://url1361.repl.it/wf/click?upn=LLQySNMYKcsdrD3Xpw6uy2nGqoz6hoT3s1h4Iok…> Read more about it here <http://url1361.repl.it/wf/click?upn=LLQySNMYKcsdrD3Xpw6uy2nGqoz6hoT3s1h4Iok…>, or, better yet, hop in <http://url1361.repl.it/wf/click?upn=LLQySNMYKcsdrD3Xpw6uy7y9lyv5Ff-2FoVbyQr…>, invite your friends and start coding! Amjad from Repl.it 767 Bryant St, #210, San Francisco, CA 94107 Unsubscribe <http://url1361.repl.it/asm/unsubscribe/?user_id=8107274&data=346ff9QOfXR57C…> - Unsubscribe Preferences <http://url1361.repl.it/asm/?user_id=8107274&data=USDh4jRtVtwga9cUFmXIXfBZ19…>

7 8

[Pharo 7.0] Build #22: 22745 ManifestHermes and HEBinaryReader should be tagged
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2018

Dec. 7, 2018

There is a new Pharo build available! The status of the build #22 was: FAILURE. The Pull Request #2053 was integrated: "22745 ManifestHermes and HEBinaryReader should be tagged" Pull request url: https://github.com/pharo-project/pharo/pull/2053 Issue Url: https://pharo.fogbugz.com/f/cases/22745 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #21: 22733-Some-menubar-cleaning
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2018

Dec. 6, 2018

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

1 0

[Pharo 7.0] Build #20: 22313-Packages-are-created-for-extension-methods-that-does-not-are-exactly-the-package-name
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2018

Dec. 6, 2018

There is a new Pharo build available! The status of the build #20 was: SUCCESS. The Pull Request #1741 was integrated: "22313-Packages-are-created-for-extension-methods-that-does-not-are-exactly-the-package-name" Pull request url: https://github.com/pharo-project/pharo/pull/1741 Issue Url: https://pharo.fogbugz.com/f/cases/22313 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Minheadless trial
by Ben Coman Dec. 5, 2018

Dec. 5, 2018

wow time flies, its been 18 months since Ronie announced his Minheadless VM branch... [1] http://forum.world.st/Minheadless-VM-flavour-status-update-td4928091.html I've been meaning this whole time to try it out. Recently in my meandering thoughts on FreeRTOS port, I guessed Minheadless might make a good starting basis to experiment with. So a quick test on Ubuntu16.04.3(Windows10-WSL)... Long ago I'd already done... git clone git@github.com:OpenSmalltalk/opensmalltalk-vm.git so I now did... cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout MinimalisticHeadless ./scripts/updateSCCSVersions cd build.minheadless.cmake/x64/pharo.stack.spur/ ./mvm VM=`pwd`/release/dist/pharo ls $VM ==> confirmed it exists cd ~/pharo wget http://files.pharo.org/image/70/latest-minimal-64.zip unzip latest-minimal-64.zip sudo $VM Pharo7.0-metacello-64bit-65cff7b.image eval "19 + 23" ==> 42 yay Particularly interesting from [1] is "using the same CMake scripts for building on the three platforms: Windows, Linux and OS X." So I thought I'd also give it a try under Windows10-VisualStudio2017. I hardly used VS before, so I'll detail what I did as a reminder for myself (and also in case someone might be able to help if I get stuck). Under a windows cmd.exe prompt (having installed git and cloned opensmalltalk-vm a long time ago) cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout -b MinimalisticHeadless ronie/MinimalisticHeadless I watched video [2] about CMake integration with Visual Studio 10. and checked the VS workloads configuration specified [2@1:13] using [3]. There is a CMakeLists.txt file in the git root folder, so.. started VS > File > Open > Folder... C:\Repos\OpenSmalltalk\opensmalltalk-vm The CMake command run ([2]@2:13) was... C:\...\cmake.exe -G "Ninja" -DCMAKE_INSTALL_PREFIX:PATH="C:\Users\Ben\CMakeBuilds\...\x86-Debug" -DCMAKE_CXX_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_C_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_MAKE_PROGRAM="C:\...\CMAKE\Ninja\ninja.exe" "C:\Repos\OpenSmalltalk\opensmalltalk-vm" I changed the cmake configuration [2@2:27] to "x64-Debug". For debug target [2@3:00] I chose "pharo.exe" Hey, thats pretty cool [2@4:05] that switching between targets changes the highlighting of #ifdef code. I had a moment when I was missing the "Debug and Launch Settings" menu item [2@4:40-4:55] and mentioned at [4], but maybe there was some clash with previously experimenting with git cloning opensmalltalk-vm from inside VS. After closing VS and reopening my cmd.exe git'd opensmalltalk-vm it showed up, but I didn't change any settings there. Then (with x64-Debug & pharo.exe selected) I went Cmake > Build All ==> 10 Errors, 9 Warnings, which I'll discuss in a followup post. cheers -ben [2] https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-… [3] https://docs.microsoft.com/en-us/visualstudio/install/modify-visual-studio [4] https://blogs.msdn.microsoft.com/vcblog/2016/12/20/cmake-support-in-visual-… [5] https://developercommunity.visualstudio.com/content/problem/234808/cmake-de…

6 22

[Pharo 7.0] Build #19: 22731-notification-mail-has-an-error-on-version
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2018

Dec. 5, 2018

There is a new Pharo build available! The status of the build #19 was: SUCCESS. The Pull Request #2043 was integrated: "22731-notification-mail-has-an-error-on-version" Pull request url: https://github.com/pharo-project/pharo/pull/2043 Issue Url: https://pharo.fogbugz.com/f/cases/22731 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo .0] Build #18: 22726 pharo icon in menus is larger than other icons 20 pix instead of 16 making its row height different
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2018

Dec. 5, 2018

There is a new Pharo build available! The status of the build #18 was: SUCCESS. The Pull Request #2037 was integrated: "22726 pharo icon in menus is larger than other icons 20 pix instead of 16 making its row height different" Pull request url: https://github.com/pharo-project/pharo/pull/2037 Issue Url: https://pharo.fogbugz.com/f/cases/22726 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[IMPORTANT] Development branch changed to "Pharo7.0"
by Esteban Lorenzano Dec. 5, 2018

Dec. 5, 2018

Hi, Working on Pharo7.0 release, I finally changed the default branch. âDevelopment" does not exists anymore, now all Pull Requests needs to be done against âPharo7.0â. This will allow us to : - Continue working on Pharo7.0 release - Open a Pharo8.0 branch (hopefully next week) Iâm sorry for the mess I can cause to someones, there should not be a problem for most of you but some may need to update their scripts. Cheers! Esteban

1 1

[Pharo .0] Build #17: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2018

Dec. 5, 2018

There is a new Pharo build available! The status of the build #17 was: SUCCESS. Could not extract further issue information from commit message: restore uploads Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo .0] Build #16: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2018

Dec. 5, 2018

There is a new Pharo build available! The status of the build #16 was: SUCCESS. Could not extract further issue information from commit message: dix sources when converting to 64bit too Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1436: Improving comment of class DebugSession
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2018

Dec. 5, 2018

There is a new Pharo build available! The status of the build #1436 was: SUCCESS. The Pull Request #2040 was integrated: "Improving comment of class DebugSession" Pull request url: https://github.com/pharo-project/pharo/pull/2040 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo .0] Build #15: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2018

Dec. 5, 2018

There is a new Pharo build available! The status of the build #15 was: FAILURE. Could not extract further issue information from commit message: fix inclusion of sources suspend upload for the moment = Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo .0] Build #14: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Dec. 4, 2018

Dec. 4, 2018

There is a new Pharo build available! The status of the build #14 was: SUCCESS. Could not extract further issue information from commit message: groovy is zero based :( Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1435: 22727-NonInteractiveTranscript-is-broken-with-files
by ci-pharo-ci-jenkins2＠inria.fr Dec. 4, 2018

Dec. 4, 2018

There is a new Pharo build available! The status of the build #1435 was: SUCCESS. The Pull Request #2039 was integrated: "22727-NonInteractiveTranscript-is-broken-with-files" Pull request url: https://github.com/pharo-project/pharo/pull/2039 Issue Url: https://pharo.fogbugz.com/f/cases/22727 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

InterruptedContext vs suspendedContext
by Thomas Dupriez Dec. 4, 2018

Dec. 4, 2018

Hello, Instances of DebugSession have an "interruptedContext" and an "interruptedProcess" instance variable. Instances of Process have a "suspendedContext" instance variable. Does someone know if there is a relation between the interruptedContext of a DebugSession and the suspendedContext of its interruptedProcess? At first glance it seems like these two variables are redundant and store the same Context. Thomas Dupriez

3 3

[Pharo 7.0-dev] Build #1434: 22687-Update-Tonel
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

There is a new Pharo build available! The status of the build #1434 was: SUCCESS. The Pull Request #2028 was integrated: "22687-Update-Tonel" Pull request url: https://github.com/pharo-project/pharo/pull/2028 Issue Url: https://pharo.fogbugz.com/f/cases/22687 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Migrate PetitParser (1) on GitHub under moosetechnology organisation?
by Julien Dec. 3, 2018

Dec. 3, 2018

Hello, Iâd like to migrate PetitParser (1) on GitHub under moosetechnology organisation. I have a project depending on it and there are some stuff Iâd like to fix on PetitParser 1 ConfigurationOf (which will become a baseline on GitHub). Is it ok to migrate it? Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

2 3

can I get Pharo7 release candidate images in PharoLauncher
by Ben Coman Dec. 3, 2018

Dec. 3, 2018

I updated PharoLauncher by... loading ConfigurationOfPharoLauncher-ChristopheDemarey.92 running ```ConfigurationOfPharoLauncher load``` then in settings clicked "Hard reset persistent state" But I'm not seeing any of the release candidate images. Should I be? cheers -ben

2 2

[Pharo 7.0-dev] Build #1433: 22720-add-more-tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

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

1 0

[Pharo 7.0-dev] Build #1432: 22718-argumentNames-should-not-use-propertyValueAt
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

There is a new Pharo build available! The status of the build #1432 was: SUCCESS. The Pull Request #2029 was integrated: "22718-argumentNames-should-not-use-propertyValueAt" Pull request url: https://github.com/pharo-project/pharo/pull/2029 Issue Url: https://pharo.fogbugz.com/f/cases/22718 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1431: 22716-testDefaultWorkingDirectory-does-a-wrong-assertion
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

There is a new Pharo build available! The status of the build #1431 was: SUCCESS. The Pull Request #2027 was integrated: "22716-testDefaultWorkingDirectory-does-a-wrong-assertion" Pull request url: https://github.com/pharo-project/pharo/pull/2027 Issue Url: https://pharo.fogbugz.com/f/cases/22716 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1430: Revert "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding"
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

There is a new Pharo build available! The status of the build #1430 was: FAILURE. The Pull Request #2035 was integrated: "Revert "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding"" Pull request url: https://github.com/pharo-project/pharo/pull/2035 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Ann] Fog 1.0.0-beta
by Santiago Bragagnolo Dec. 3, 2018

Dec. 3, 2018

Hi All! I have being working on releasing versions (i should do it more often). I am happy to announce Fog v1.0.0-beta. I think I found a API that i like enough. So, i took the courage to pass to 1. Thew new version changes many things: Redefines the roll of the session, it minimize the roll of the connection, it cleans up the code, it defines a more verbose but less magic API. It generates proxies for the contracts. It supports now all the types including: maps and arrays. Goodnight :) Santiago Fog Pharo Ethereum Driver Fog is a library that allows the user to connect to an ethereum based blockchain data base. Is based on the Javascript canonical implementation done by Ethereum community Ethereum Javascript API <https://github.com/ethereum/wiki/wiki/JavaScript-API>. <https://github.com/smartanvil/Fog#dependencies> Download code <https://github.com/smartanvil/Fog#iceberg--baseline>Iceberg / Baseline Metacello new baseline: 'Fog'; repository: 'github://sbragagnolo/Fog/src'; load.

2 3

Version control of Playground scripts
by Christopher Fuhrman Dec. 2, 2018

Dec. 2, 2018

Hello, In Pharo 6.1 I have got Iceberg working and love the interface to GitHub. Thanks to the Rmod folks for all the patient answers to my newbie questions. However, most of my development remains in playground scripts, and as far I understand, it's not possible to put them under version control with Iceberg. My scripts *could* be turned into classes eventually (some already have been and are under Iceberg). But it feels frustrating to rush it, just to get the versioning. I know how to save Playground files to the web, which is useful, but of course not version control per se. Knowing Playground files are saved on local disk, I got to thinking... What would be the risk(s) of using git outside Pharo, on the Playground files' directory? Has anyone tried that before? Cheers, Christopher

5 6