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

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] Contribute to pharo8.0 ?
by Ritesh Saini Feb. 24, 2020

Feb. 24, 2020

Having the same issue. Canât fix! Tried everything :( Regards, Ritesh adsense high paying keywords <https://www.digitalkube.com/highest-paying-adsense-niches/>

3 2

Testing "Weekly Digest" for GitHub
by Marcus Denker Sept. 30, 2019

Sept. 30, 2019

Hi, There is a ProBot that creates an issue with a weekly summary. By installing it for testing, we got the first report: Weekly Digest (1 July, 2019 - 8 July, 2019) https://github.com/pharo-project/pharo/issues/381 I will do some fine-tuning (e.g. disable commits and star-gazers) later. We then can let it run for some weeks and see if it is useful or not. Marcus

1 7

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by monty Sept. 10, 2019

Sept. 10, 2019

I will move it to github, if that makes things easier for everyone else. ___ montyos.wordpress.com > Sent: Wednesday, January 30, 2019 at 3:13 PM > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > > > > On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: > > > > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. > > Has there been any progress in this area ? > > It would be really great if this important project moved to GitHub. > > Sven > >

8 11

possible Windows Update "1903" Iceberg problem
by Ben Coman Sept. 9, 2019

Sept. 9, 2019

IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? A few other recent reports are noted here... https://github.com/pharo-project/pharo/issues/3418 cheers -ben

7 18

[ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)
by tesonep＠gmail.com Sept. 5, 2019

Sept. 5, 2019

TL;DR; ====== For the anxious, you can get real headless vm and image from zero-conf. $ wget get.pharo.org/64/80+vmHeadlessLatest | bash Zero conf scripts remain unchanged for users. However, if you are launching the VM by hand from the executable instead of the launcher scripts (pharo and pharo-ui) as in $ ./pharoexecutable Pharo.image the image will launch in headless mode and will not open a window. To launch it in headfull, you can use the --interactive argument after the image, which will make the image open a window using SDL2. $ ./pharoexecutable Pharo.image --interactive Long version ============ Hi, this mail is the happy intermediate result of the work that us, the Pharo Consortium Team, has been doing in the last couple of months. Our main objective is to have a real headless implementation of Pharo where all the responsibility to open or not a World window (or other) is handled by the image. For doing so we have done a series of modifications in the image and the VM side. We consider this is the path that Pharo 8 and following versions should follow, as it will severely improve server-side and command line Pharo and in building custom desktop applications. These modifications are available only in 64-bits machines (Windows, OSX, and Linux). ARM32 and 64bits headless is in the roadmap, but it is delayed because we have prioritized our three major platforms for this first couple of months. All this work is based in Opensmalltalk-VM and Ronnie's initial work on headless. We are really grateful to all the contributors in the history of this nice product. To achieve a real headless VM we have brought modifications in the source tree because most of the platform code to open and manipulate windows is not required anymore. Instead, we use the SDL2 library that implements a nice layer on top of the OS and allows us to manage on the image side through FFI. So this mail is now an open call for (beta?)testing. The sources of the current VM we are building are in the headless branch in https://github.com/pharo-project/opensmalltalk-vm And we have set up a CI that is both building and testing the VM in https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ For the future we have a lot of ideas, that will wait for another long email or a beer-talk @ESUG. We want to hear your ideas!! Image-Side Improvements ======================= - The image handles the creation or not of the main world window. - We incorporated the idea of World renderer, where different backends are used to render the world. - We have 3 backends: VM support (compatibility with non-headless VMs), and OSWindow with two backends: SDL and GTK3+. - The modifications in the image are fully backward compatible with the non-headless VM and are pushed since weeks in the latest 8.0 image. - We move the handling of events to the image side when using SDL and GTK3+, opening the door to a richer set of events and finer-grained control over them. - SDL and GTK versions are implemented using FFI calls. VM-Side Improvements ==================== - VMMaker code migrated to Tonel thanks to Feenk and included in the repository of the VM. - Making VMMaker execute in Pharo 7 and 8. - Removing GPL code from the VM repository (GDB). - Slowly adding new tests for the JIT / Slang and VMGeneration. - Restructuring of the source code. - A new simpler CMake build. - Generate VM code from Slang on each build. - A CI process to validate (including the run of the tests in Pharo and the ones adding to the VM). - Simplification of the codebase. - Maximize the reuse of code between the platforms (preferring the standard versions over the platform-specific). - Cleaning up duplicated code. - All the plugins are now external plugins. - The VM is now a dynamic library. This is a first step towards embedding Pharo into other applications. - The main executable is a thin frontend (you can change it or implement your own). - Removing unused plugins. - Improved crash dump. Especially the crash dump works now in Windows 64bits. - Dummy implementation of Security plugin (it is going away.... eventually). - Cleanup of SSL, UUID, and Socket plugin. - Cleanup of conditional code (Still to improve). - Improving the types used in the functions (we have to be neat to be multiplatform/multi-arch). - Improving the lookup of modules - Improving the logging of the VM - Improving the handling of VM arguments Thanks a lot for reading so long!! We hope you enjoy the VM and please tell us all the problems you find!! Pablo, Guille, and Esteban

7 12

Epicea Feedback
by Sean P. DeNigris Sept. 4, 2019

Sept. 4, 2019

Not complaining at all and appreciate everyone's hard (mostly-unpaid) work, but providing raw feedback in case it's helpful... - Browser awkward: filters disappear whenever left selection changed; no multi-select of sessions, which led to a host of difficulties described below. - What is the heuristic to find API access points? Epicea package has no comment, 'Browser' tag doesn't seem to have an XyzBrowser class, no particular class in the 'Model' tag jumps out at me as an access point; as above Browser about text not set. I finally bring up Morphic halos on the browser and after flopping around, find subclasses of EpLogNode; I browse it and find EpLogNodeGraphModel, which sounds interesting and turns out to be a spec. I figure out how to list the log files, but not how to get the entries - I was expecting a term like that and the relevant method (#log it turns out) has no comment to indicate it's what I'm looking for. Now that I'm starting to understand the project organization, back to the browser to explore EpUnifiedBrowserModel. After a bit of poking around, I suspect (correctly) that #log is what I'm after. Based on code I extract from the browsers and a bit of experimenting in GT, I come up with the following seemingly very complex script: nodes := EpFileLogNode fromAllLogsIn: EpMonitor current sessionStore baseLocator. nodes do: [ :node | node populateReferencedNodesWith: nodes ]. nodes flatCollect: [ :n | n log events select: [ :e | e affectedPackageName beginsWith: 'Magritte' ] ] I now run into a series of problems because, although EpCodeChange declares #affectedPackageName as an abstract method, not all events are EpCodeChanges. I exclude EpUndos. Easy enough. Now I come to an EpGenericRefactoring. This one is harder because p.s. <rant>Code names for internal projects seem extremely counterproductive. Hiedra tells me absolutely nothing about functionality. It might as well be called XyzWidgetThing</rant> ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 4

CMake StackInterpreter Headless build
by Ben Coman Sept. 3, 2019

Sept. 3, 2019

How can I build the StackInterpreter with the Pharo Headless build? I tried... -DCOG_JIT:BOOL="False" but get the message... [CMake] CMake Warning: Manually-specified variables were not used by the project: COG_JIT The following with the new binary doesn't distinguish it for me... $ build/vm/pharo --version my.image Pharo 8.1.0 built on Aug 30 2019 18:06:20 Compiler: 7.4.0 Built from: acaeef692 - Commit: acaeef692 - Date: 2019-08-28 22:49:49 +0800 Is there anyway to check that a particular binary is a StackInterpreter? Can this be added to "--version" ? Here is the full log... Found cmake executable at /usr/bin/cmake. 1> /usr/bin/cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Debug" -DCOG_JIT:BOOL="False" -DCMAKE_INSTALL_PREFIX="/mnt/c/Users/Ben/Source/Repos/opensmalltalk-vm/out/install/WSL-Debug" "/mnt/c/Users/Ben/Source/Repos/opensmalltalk-vm/CMakeLists.txt"; 1> [CMake] -- acaeef692 - Commit: acaeef692 - Date: 2019-08-28 22:49:49 +0800 1> [CMake] -- int 4 1> [CMake] -- long 8 1> [CMake] -- long long 8 1> [CMake] -- void* 8 1> [CMake] -- C Compiler: /usr/bin/cc 1> [CMake] -- C++ Compiler: /usr/bin/c++ 1> [CMake] -- Resource Compiler: 1> [CMake] -- Adding plugin: SecurityPlugin 1> [CMake] -- Adding plugin: FilePlugin 1> [CMake] -- Adding plugin: FileAttributesPlugin 1> [CMake] -- Adding plugin: UUIDPlugin 1> [CMake] -- Adding plugin: SocketPlugin 1> [CMake] -- Adding plugin: SurfacePlugin 1> [CMake] -- Adding plugin: LargeIntegers 1> [CMake] -- Adding plugin: JPEGReaderPlugin 1> [CMake] -- Adding plugin: JPEGReadWriter2Plugin 1> [CMake] -- Adding plugin: MiscPrimitivePlugin 1> [CMake] -- Adding plugin: B2DPlugin 1> [CMake] -- Adding plugin: LocalePlugin 1> [CMake] -- Adding plugin: SqueakSSL 1> [CMake] -- Adding plugin: DSAPrims 1> [CMake] -- Adding plugin: UnixOSProcessPlugin 1> [CMake] Adding third-party libraries for linux: pthreadedPlugin-0.0.1 1> [CMake] Adding third-party libraries for linux: libffi-3.3-rc0 1> [CMake] Adding third-party libraries for linux: libgit2-0.25.1 1> [CMake] Adding third-party libraries for linux: libssh2-1.7.0 1> [CMake] Adding third-party libraries for linux: openssl-1.0.2q 1> [CMake] Adding third-party libraries for linux: SDL2-2.0.7 1> [CMake] -- Configuring done 1> [CMake] -- Generating done 1> [CMake] CMake Warning: 1> [CMake] Manually-specified variables were not used by the project: 1> [CMake] COG_JIT 1> [CMake] -- Build files have been written to: /mnt/c/Users/Ben/Source/Repos/opensmalltalk-vm/out/build/WSL-Debug 1> Starting CMake target info extraction ... 1> CMake server connection made. 1> Extracted includes paths. 1> Extracted CMake variables. 1> Extracted source files and headers. 1> Extracted global settings. 1> Extracted code model. 1> Collating data ... 1> Warning: CMake 3.11 or newer is required for install target integration 1> Target info extraction done. 1> CMake generation finished. cheers -ben P.S. btw, the -DCOG_JIT:BOOL="False" comes from first trying-the-simplest-thing of unticking "COG_JIT" in this Visual Studio configuration dialog... [image: image.png]

2 1

[Pharo 8.0] Build #686: 4422-DNU-in-finder-searching-for-print-this-invalid-selector
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2019

Aug. 31, 2019

There is a new Pharo build available! The status of the build #686 was: FAILURE. The Pull Request #4444 was integrated: "4422-DNU-in-finder-searching-for-print-this-invalid-selector" Pull request url: https://github.com/pharo-project/pharo/pull/4444 Issue Url: https://github.com/pharo-project/pharo/issues/4422 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #685: Revert "4401-ZipArchive-should-not-convert-FileReference-to-paths"
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2019

Aug. 31, 2019

There is a new Pharo build available! The status of the build #685 was: SUCCESS. The Pull Request #4449 was integrated: "Revert "4401-ZipArchive-should-not-convert-FileReference-to-paths"" Pull request url: https://github.com/pharo-project/pharo/pull/4449 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #684: Add refactoring to remove method and the ones in subclasses
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2019

Aug. 30, 2019

There is a new Pharo build available! The status of the build #684 was: FAILURE. The Pull Request #4427 was integrated: "Add refactoring to remove method and the ones in subclasses" Pull request url: https://github.com/pharo-project/pharo/pull/4427 Issue Url: https://github.com/pharo-project/pharo/issues/RemoveMethodsInHierarchy Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #683: 4401-ZipArchive-should-not-convert-FileReference-to-paths
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2019

Aug. 30, 2019

There is a new Pharo build available! The status of the build #683 was: FAILURE. The Pull Request #4402 was integrated: "4401-ZipArchive-should-not-convert-FileReference-to-paths" Pull request url: https://github.com/pharo-project/pharo/pull/4402 Issue Url: https://github.com/pharo-project/pharo/issues/4401 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

SequenceableCollection>>#allButFirst: inconsistence across subclasses
by Julien Aug. 30, 2019

Aug. 30, 2019

Hello, I opened that issue: https://github.com/pharo-project/pharo/issues/4442 <https://github.com/pharo-project/pharo/issues/4442> And I think to fix it we need to actually discuss about what we want. #allButFirst: behaves differently depending on the actual type of sequenceable collection when argument is greater than collection size. For instance: #(1 2) allButFirst: 3. "PrimitiveFailed signaled" (LinkedList with: 1 with: 2) allButFirst: 3. "PrimitiveFailed signaled" (OrderedCollection with: 1 with: 2) allButFirst: 3. "an OrderedCollection() Â» The question is then, who is right? Should #allButFirst: with an argument greater than the collection size raise an error Or Should #allButFirst: with an argument greater than the collection size returns an empty collection ? I asked a few people about it @ ESUG and it appears that the expected behaviour from #allButFirst: is not the same to all people. We need to decide so we improve consistence of collections. And then, we need to document that with a test :-). 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

6 5

[Pharo 8.0] Build #682: WeakValueDictionary-return-association-with-collectionElements-instead-of-nil
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2019

Aug. 30, 2019

There is a new Pharo build available! The status of the build #682 was: SUCCESS. The Pull Request #4400 was integrated: "WeakValueDictionary-return-association-with-collectionElements-instead-of-nil" Pull request url: https://github.com/pharo-project/pharo/pull/4400 Issue Url: https://github.com/pharo-project/pharo/issues/WeakValueDictionary Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #681: 4433-Pragmakeyword-should-be-deprecated-via-deprecation-mechanism
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2019

Aug. 30, 2019

There is a new Pharo build available! The status of the build #681 was: FAILURE. The Pull Request #4434 was integrated: "4433-Pragmakeyword-should-be-deprecated-via-deprecation-mechanism" Pull request url: https://github.com/pharo-project/pharo/pull/4434 Issue Url: https://github.com/pharo-project/pharo/issues/4433 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo topics for internships in Canada [Deadline for submission mid sept]
by StÃ©phane Ducasse Aug. 30, 2019

Aug. 30, 2019

Hello We would like to draw your attention that there are a couple of internships position for interns in Canada for May 2020. https://globalink.mitacs.ca/#/student/application/projects put Petrillo as Professor last name and Chicoumiti as University. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

[Pharo 8.0] Build #680: 4435-Cannot-browse-trait-in-class-description
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2019

Aug. 30, 2019

There is a new Pharo build available! The status of the build #680 was: FAILURE. The Pull Request #4438 was integrated: "4435-Cannot-browse-trait-in-class-description" Pull request url: https://github.com/pharo-project/pharo/pull/4438 Issue Url: https://github.com/pharo-project/pharo/issues/4435 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #679: 4439-Epicea-Should-FileOut-to-Image-Directory
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2019

Aug. 29, 2019

There is a new Pharo build available! The status of the build #679 was: SUCCESS. The Pull Request #4440 was integrated: "4439-Epicea-Should-FileOut-to-Image-Directory" Pull request url: https://github.com/pharo-project/pharo/pull/4440 Issue Url: https://github.com/pharo-project/pharo/issues/4439 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #678: 4258-AbsolutePath-withParents-on-root---on-linux---return-2-root-path
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2019

Aug. 29, 2019

There is a new Pharo build available! The status of the build #678 was: FAILURE. The Pull Request #4408 was integrated: "4258-AbsolutePath-withParents-on-root---on-linux---return-2-root-path" Pull request url: https://github.com/pharo-project/pharo/pull/4408 Issue Url: https://github.com/pharo-project/pharo/issues/4258 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Debugging Pharo-Headless-Linux-VM using Visual Studio running on Windows
by Ben Coman Aug. 28, 2019

Aug. 28, 2019

Guille's procrastination experiments inspired me to procrastination of my own, with an experiment around debugging Pharo-Headless-Linux-VM using Visual Studio running on Windows. I've refined the steps-from-scratch to reproduce down to the following... Overview... 1. Install Windows Subsystem from Linux 2. Install Visual Studio 2019 3. Build and run hello-world exercise inside WSL 4. Build and run Pharo-Headless-VM inside WSL Now lets get started... ############################### Install Windows Subsystem from Linux ############################### 1A. On a Windows 10 box, go to the Windows App Store and Ubuntu 18.04... Ref: https://docs.microsoft.com/en-us/windows/wsl/install-win10 1B. Ensure this configured as the default (otherwise later the $defaultWSLPath variable doesn't work and you may see a Visual Studio error "Could not open windows subsystem shell")... C:\Users\Ben>wslconfig /l Windows Subsystem for Linux Distributions: Legacy (Default) kali-linux Ubuntu-18.04 Ubuntu-16.04 C:\Users\Ben>wslconfig /setdefault Ubuntu-18.04 C:\Users\Ben>wslconfig /l Windows Subsystem for Linux Distributions: Ubuntu-18.04 (Default) Legacy kali-linux Ubuntu-16.04 Ref: https://www.howtogeek.com/344688/how-to-set-your-default-linux-distribution… btw, my Windows 10 box recently upgrade to latest version. C:\Users\Ben> ver Microsoft Windows [Version 10.0.18362.295] 1C. Start Ubuntu-18.04, then update/upgrade/install pre-requisites... ``` sudo apt-get update sudo apt-get upgrade sudo apt-get install clang gcc gdb make rsync zip # Visual Studio requirement sudo apt-get install uuid-dev # Pharo VM build requirement ``` While that is running... #################### Install Visual Studio 2019 #################### 2A. Download and run the installer for Visual Studio Community 2019 (not Visual Studio Code) Ref: https://visualstudio.microsoft.com/free-developer-offers/ 2B. When the "Visual Studio Installer" opens, under its "Workloads" tab, select "Linux development with C++" and click **Install**. Ref: https://docs.microsoft.com/en-us/cpp/linux/download-install-and-setup-the-l… ##################################### Build and run hello-world exercise inside WSL ##################################### 3A. Start Visual Studio 2019 and at its opening window, under "Get started" click "Create a new project". Then scroll down and choose "CMake Project" and <Next>. and configure... Project name: hello-world then click <Create>. Ref: https://docs.microsoft.com/en-us/cpp/linux/cmake-linux-project?view=vs-2019 Now it may immediately start the CMake build and get an error because its using the default "x64-Debug" configuration. Ignore that, we will create a new configuration to build on Windows Subsystem for Linux. 3B. From the "Configuration drop-down" (where you see "x64-Debug") select "Manage Configurations..." Delete "x64-Debug". Add... "WSL-Debug" and use all defaults then press <CTRL-S> to save. Inside WSL, Cmake will start generating the makefiles. At some point you might see "Supported CMake version is not present on WSL. Install CMake binaries built by Microsoft?" YES, do that. 3C. After "CMake generation finished", pull down "Select Startup Item" and select "hello-world" then press the green PLAY button. Inside WSL, the make build will start and after its done the pharo executable will run there. In the [Output] tab, it was successful if you see "The thread 'hello-world' (0x1f7a) has exited with code 0" . 3D. For proof that its running inside WSL, lets write a file! In the "Solution Explorer" tab, browse to "hello-world.cpp" and change its contents to... ``` #include <stdio.h> int main() { FILE* fp; int i; /* open the file for writing*/ fp = fopen("/tmp/built-by-visual-studio", "w"); fprintf(fp, "It worked.\n"); fclose(fp); return 0; } ``` then press the green PLAY button. After you see "thread 'hello-world' has exited with code 0" open a WSL shell and run... $ cat /tmp/built-by-visual-studio It worked 3E. To experience debugging Linux from Visual Studio, first remove the test file... $ rm /tmp/built-by-visual-studio then put a breakpoint on "fopen" and click the PLAY button. Check if the file is there... $ cat /tmp/built-by-visual-studio cat: /tmp/built-by-visual-studio: No such file or directory <STEP OVER> fopen $ cat /tmp/built-by-visual-studio <STEP OVER> fprintf $ cat /tmp/built-by-visual-studio <STEP OVER> fclose $ cat /tmp/built-by-visual-studio It worked 3F. All done... File > Close Folder ##################################### Build and run Pharo-Headless-VM inside WSL ##################################### 4A. From Visual Studio 2019 opening window, under "Get started" click "Clone or check out code" Repository location: https://github.com/bencoman/opensmalltalk-vm.git then click <Clone>. https://docs.microsoft.com/en-us/visualstudio/get-started/tutorial-open-pro… 4B. In the bottom-right status bar, click the "branching" icon and choose "Manage Branches". Expand "remotes/origin", then right-click "headless-WSL-VisualStudio" and "Checkout" A fixed "WSL-Debug" configuration is a part of this branch, so its CMake-build should auto-start and complete successfully. 4C. After "CMake generation finished", pull down "Select Startup Item" and select "pharo (build/vm/pharo)" then press the green PLAY button. Don't worry if it sits for a long time on "BalloonEnginePlugin>>primitiveAddRect" The [Error List] tab pops up with 116 Warnings. Switching back to the [Output] tab, you hopefully see "thread 'pharo' (0x4d0d) has exited with code 0" So the VM just built and ran headless under Windows Subsystem for Linux. Now lets debug that from Visual Studio. 4D. Browse to src/main.c and put a breakpoint in main() on the call to parseArguments() Then click the PLAY button. Once stopped at the breakpoint, <STEP INTO>. In the [Autos] tab, expand the "parameters" variable. Observe "imageFile" is empty. Notice "imageFile" becomes "Pharo.image" after <STEP OVER> splitVMAndImageParameters(). So now I leave you to play. I'd be interested in hearing about people's experiences. Placing the correct PharoHeadless.image in the right place to actually run the image is left as an exercise for the reader. cheers -ben

1 0

[Pharo 8.0] Build #677: [CI CLEANING] Fixing current test failures
by ci-pharo-ci-jenkins2＠inria.fr Aug. 28, 2019

Aug. 28, 2019

There is a new Pharo build available! The status of the build #677 was: SUCCESS. The Pull Request #4436 was integrated: "[CI CLEANING] Fixing current test failures" Pull request url: https://github.com/pharo-project/pharo/pull/4436 Issue Url: https://github.com/pharo-project/pharo/issues/fixingCurrentTestFailures Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Weekend Procastination] what the new minheadless opens as posibilities :D
by Guillermo Polito Aug. 26, 2019

Aug. 26, 2019

Hi all, Over the weekend, instead of working on my ESUG presentations I procastinated a bit with some experiments that I would like to share ^^. Procastination 1: Render the world fully in athens (instead of a middling bitmap) to have an idea of the effort to get fast to hdpi What you see here is a world drawn completely in athens in minheadless, where in red are the invalidated rectangles in the screen (Iâm using to debug a bit). Icons are broken because I broke them while playing, not because they do not work in athens :P. There is still work to do if we want to explore this direction. Mainly performance issues to make it at least usable, so it can be iterated easily. We have seen with Pablo that a lot of time is taken in the transformation of morphic/pharo form/bitmaps to athens ones, since they do not have the same format and right now it is done with a bit-per-bit copy. Procastination 2: poping out morphs out of the world What you see here is that I can have different os windows with different worlds, giving a multi-window experience :). There is also work to do in this direction if we want to push it: - morphic support for multiple worlds/windows is not so good... - the usage of the current world needs to be reviewed. The world has two distinct responsibilities right now 1) it is the manager of the hands (required for drag n drop) 2) it is the main container/pasteup for other morphs Imagine in the short term a Morphic Spec app can use a âexternal window rendering on athensâ strategy that mixes the two things above and each new window is popped up as a new window. :D For those @ESUG, Iâll be arriving this evening, Iâm going to show this in the show us your projects, and if you want to help, please contact me, you can learn a lot and its super fun :)

4 5

[MorphicUIManager] strange method onEventSensorStartup:
by ClÃ©ment Dutriez Aug. 26, 2019

Aug. 26, 2019

Hello, I working on the first step of the migration of the UIManager. ```Smalltalk onEventSensorStartup: anEventSensor anEventSensor flushAllButDandDEvents ``` the problem is that the only class defining 'flushAllButDandDEvents' method do nothing. It's normal? what is the responsibility of this method? Thanks -- Dutriez ClÃ©ment dutriezcle(a)gmail.com 0605199489 [image: www.linkedin.com/in/clÃ©ment-dutriez-407275173] <http://www.linkedin.com/in/clÃ©ment-dutriez-407275173>

1 0

[Pharo 8.0] Build #676: Add missing find and replace refactoring
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2019

Aug. 26, 2019

There is a new Pharo build available! The status of the build #676 was: FAILURE. The Pull Request #4430 was integrated: "Add missing find and replace refactoring" Pull request url: https://github.com/pharo-project/pharo/pull/4430 Issue Url: https://github.com/pharo-project/pharo/issues/FindAndReplace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #675: Add undo refactoring option
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2019

Aug. 26, 2019

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

1 0

[Pharo 8.0] Build #674: Pre-load MCWorkingCopy cache
by ci-pharo-ci-jenkins2＠inria.fr Aug. 25, 2019

Aug. 25, 2019

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

1 0

[Pharo 8.0] Build #673: Simplify Variables with default blocks
by ci-pharo-ci-jenkins2＠inria.fr Aug. 25, 2019

Aug. 25, 2019

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

1 0

[Pharo 8.0] Build #671: 4414-slot-class-defintion-Class-Variables-with-parameters-are-not-printed-correctly
by ci-pharo-ci-jenkins2＠inria.fr Aug. 25, 2019

Aug. 25, 2019

There is a new Pharo build available! The status of the build #671 was: FAILURE. The Pull Request #4418 was integrated: "4414-slot-class-defintion-Class-Variables-with-parameters-are-not-printed-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/4418 Issue Url: https://github.com/pharo-project/pharo/issues/4414 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

3 2

[Pharo 8.0] Build #672: 4149-instVarNames-is-not-including-instance-variables-coming-from-Stateful-traits
by ci-pharo-ci-jenkins2＠inria.fr Aug. 24, 2019

Aug. 24, 2019

There is a new Pharo build available! The status of the build #672 was: FAILURE. The Pull Request #4367 was integrated: "4149-instVarNames-is-not-including-instance-variables-coming-from-Stateful-traits" Pull request url: https://github.com/pharo-project/pharo/pull/4367 Issue Url: https://github.com/pharo-project/pharo/issues/4149 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #670: Roassal3Extentions
by ci-pharo-ci-jenkins2＠inria.fr Aug. 24, 2019

Aug. 24, 2019

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

1 0

[Pharo 8.0] Build #669: Class Variables with Default value
by ci-pharo-ci-jenkins2＠inria.fr Aug. 24, 2019

Aug. 24, 2019

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

1 0

[Pharo 8.0] Build #668: 4403-cannot-change-position-in-a-memory-write-stream
by ci-pharo-ci-jenkins2＠inria.fr Aug. 23, 2019

Aug. 23, 2019

There is a new Pharo build available! The status of the build #668 was: SUCCESS. The Pull Request #4404 was integrated: "4403-cannot-change-position-in-a-memory-write-stream" Pull request url: https://github.com/pharo-project/pharo/pull/4404 Issue Url: https://github.com/pharo-project/pharo/issues/4403 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #667: 4406-fix-class-def-parser-for-simple-definitions
by ci-pharo-ci-jenkins2＠inria.fr Aug. 23, 2019

Aug. 23, 2019

There is a new Pharo build available! The status of the build #667 was: FAILURE. The Pull Request #4409 was integrated: "4406-fix-class-def-parser-for-simple-definitions" Pull request url: https://github.com/pharo-project/pharo/pull/4409 Issue Url: https://github.com/pharo-project/pharo/issues/4406 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Class definition with slot template is broken
by Cyril Ferlicot Aug. 23, 2019

Aug. 23, 2019

Hi, Since yesterday I get a lot of bugs when I try to edit class definitions while having the slot template in class definition enabled. (See comment: https://github.com/pharo-project/pharo/pull/4391) This make it a little hard to develop :( Is there an easy fix? Else maybe we should revert the change until we have the fix? Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

4 5

[Pharo 8.0] Build #666: LazySlotPrinting
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #665: Improve-WeakValueDictionary
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #664: Monticello-tests-should-not-depend-on-deprecated-streams
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #664 was: FAILURE. The Pull Request #4347 was integrated: "Monticello-tests-should-not-depend-on-deprecated-streams" Pull request url: https://github.com/pharo-project/pharo/pull/4347 Issue Url: https://github.com/pharo-project/pharo/issues/Monticello Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #663: Add-deny-equivalent-of-assertCollection-hasSameElements
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #662: Enable CDClassParser in class definition in Calypso
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #662 was: FAILURE. The Pull Request #4391 was integrated: "Enable CDClassParser in class definition in Calypso" Pull request url: https://github.com/pharo-project/pharo/pull/4391 Issue Url: https://github.com/pharo-project/pharo/issues/classParserInCalypso Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #661: psKeysSemaSimplify
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #660: Push-down-method-on-right-owner
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #659: Use stack instead of recursion in MCScanner>>next
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #659 was: SUCCESS. The Pull Request #4310 was integrated: "Use stack instead of recursion in MCScanner>>next" Pull request url: https://github.com/pharo-project/pharo/pull/4310 Issue Url: https://github.com/pharo-project/pharo/issues/MCScanner_next Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Consortium New Bronze Member: Object Guild
by Marcus Denker Aug. 22, 2019

Aug. 22, 2019

The Pharo Consortium is very happy to announce that the Object Guild has joined the Consortium as a Bronze Member. Object Guild Simply Revolutionary High fidelity software solutions for values-driven organisations. We help you to help the world become a better place. Object Guild differentiates itself as a custom software design and development shop in the following ways: - by a commitment to use technology and software to make the world a better place; - by seeking and serving clients who are equally committed to social and environmental enhancement; - by focusing on "Software that Fits," that seamlessly integrates with and enhances the complex system where it is deployed; - by our commitment to Pharo and Smalltalk development, including expanding and enhancing Pharo; - by a focus on education and training, internal and for clients, that advances the "state-of-the-practice" of software development. https://objectguild.com The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. http://consortium.pharo.org Individuals can support Pharo via the Pharo Association. http://association.pharo.org

1 0

[Pharo 7.0] Build #169: 4282-Backport-Pharo7-trying-to-add-an-ivar-to-UndefinedObject-crashes-the-VM-4017
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #169 was: FAILURE. The Pull Request #4378 was integrated: "4282-Backport-Pharo7-trying-to-add-an-ivar-to-UndefinedObject-crashes-the-VM-4017" Pull request url: https://github.com/pharo-project/pharo/pull/4378 Issue Url: https://pharo.fogbugz.com/f/cases/4282 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #658: 4365-Reintroduce-separator
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #657: CodeGenWeakClassVar
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2019

Aug. 21, 2019

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

1 0

[Pharo 8.0] Build #656: FormCanvas-has-wrong-lazy-initialization
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2019

Aug. 21, 2019

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

1 0

Question on Behavior>>superclass:
by Jordi Delgado Aug. 21, 2019

Aug. 21, 2019

Hi, This example in the slides of Pharo MOOC, week 7, is broken in Pharo 7.0 (the variable newClass is not used, thus it has been removed): | behavior model | behavior := Behavior new. behavior superclass: Model. behavior setFormat: Model format. model := Model new. model primitiveChangeClassTo: behavior new. self assert: model class = behavior. self assert: model class superclass = Model. behavior compile: 'foo ^ 2'. self assert: model foo = 2. self should: [Model new foo] raise: MessageNotUnderstood (slide 14 in http://rmod-pharo-mooc.lille.inria.fr/MOOC/Slides/Week7/C019-W7S04-OtherRef…) The code is broken because there is no method Behavior>>classInstaller, and the message classInstaller is sent to self in Behavior>>superclass:. Adding a Behavior>>superclass2: to Pharo 7.0, copied from Pharo 6.1 Behavior>>superclass:, and using Behavior>>superclass2: in the example: | behavior model | behavior := Behavior new. behavior superclass2: Model. "<-------" behavior setFormat: Model format. model := Model new. model primitiveChangeClassTo: behavior new. self assert: model class = behavior. self assert: model class superclass = Model. behavior compile: 'foo ^ 2'. self assert: model foo = 2. self should: [Model new foo] raise: MessageNotUnderstood the code works again and the example is good. However, this is only an ugly workaround. Thus: I do not know why Behavior>>superclass: was changed in Pharo 7.0 but I guess it was not an accident. I assume it has to do with deep changes in the low level structure of the implementation of the language, having to do with slots, etc. I have browsed Pharo issues in github but I did not find anything related. Also, I'm not sure this problem qualifies as an "issue". So, my question is. Is it possible to easily adapt the example to the new Pharo 7.0? (with no silly workarounds, I mean). Thanks in advance and, as usual, apologies if the question is trivial and/or stupid. Bests, Jordi PS: Any Pharoer in CCCamp? -- Jordi Delgado Computer Science Department - Universitat PolitÃ¨cnica de Catalunya Campus Nord, Omega building, Office S115 c/Jordi Girona Salgado, 1-3 08034 Barcelona, Spain. Phone: +34.93.413.40.18 Public Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xB7911543AD9E79A8

1 0

[Pharo 8.0] Build #655: 4272 Fix Spelling of Responsability
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2019

Aug. 21, 2019

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

1 0