- Pharo-dev - lists.pharo.org

[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