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

[Pharo 8.0] Build #954: 3955-remove-testPerformanceInlined-ifNotNil-and-testPerformanceInlined-ifTrue

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 7, 2019

[Pharo 8.0] Build #953: Copy a selector converted to a test method selector

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #953 was: FAILURE. The Pull Request #5071 was integrated: "Copy a selector converted to a test method selector" Pull request url: https://github.com/pharo-project/pharo/pull/5071 Issue Url: https://github.com/pharo-project/pharo/issues/copyTestSelector Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019

[Pharo 8.0] Build #952: Syntax Highlighter: Simplify Parsing

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 7, 2019

Re: [Pharo-dev] Integer #byteAt: #digitAt: portability

by Sven Van Caekenberghe

https://github.com/pharo-project/pharo/pull/5079 > On 8 Oct 2019, at 19:32, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 8 Oct 2019, at 18:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> Recently, #digitAt: was renamed to #byteAt: in Pharo 8. I totally agree that this is better. >> >> However, how does one write a library that needs to use this selector and wants portability with at least Pharo 7 ? >> >> That requires quite some effort from my side (either an ugly dynamic hack, or different source code packages, just for one method). >> >> Can we back port #byteAt: at least as an alias to Pharo 7 ? > > yes of course good idea. > If you can send a PR it will be faster :) >> >> Sven

Nov. 7, 2019

[Pharo 8.0] Build #951: 5073-HandMorphposition-is-not-safe

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 7, 2019

[ANN] Roadmap progress report October 2019 - Open meeting 14/11 16h EU

by Esteban Lorenzano

Hello, This is the log of what we have been working on last month. As usual, they are just bullets because we assume you are already aware of most of them, but no hesitate to ask if you want more details :) Also, Iâm scheduling an open meeting next Thursday to talk with those who want to show up and ask questions, discuss something, comment something. This are the connection details (yes, you need to install an application, but is free and quality of communication is very good): Topic: Pharo open meeting Time: Nov 14, 2019 04:00 PM Paris Join Zoom Meeting https://zoom.us/j/148993322 Meeting ID: 148 993 322 One tap mobile +33170379729,,148993322# France +33756784048,,148993322# France Dial by your location +33 1 7037 9729 France +33 7 5678 4048 France +33 1 7037 2246 France +1 669 900 6833 US (San Jose) +1 929 205 6099 US (New York) Meeting ID: 148 993 322 Find your local number: https://zoom.us/u/aewx54d7wE <https://zoom.us/u/aewx54d7wE> Note: Meeting is 16h France time. Which is +1 UTC now, so it will be 15h UTC. Roadmap progress report October 2019 Image Spec2 Make "component list" part of the list family. Work on a new SpRichTextPresenter (still WIP) Implement first iteration of "application based styles" (the capability to add application styles to Spec2 applications) Styles can now be nested (e.g. so you can say "make this label dimâ) Work on tables and lists properties: sortable (working on morphic, WIP on gtk). Spec2 - Morphic backend Fix a problem when calculating width of toolbars. Fix component list presenter Make component list presenter able to show rows of different height. Spec2 - Gtk backend Make exception handling when inside a callback more solid (still need a couple of iterations) Utils: GtkLeakFinder to track different kind of leaks (image side non-GC, vm side non-freed) Utils: compiling a complete gtk3 distribution to allow debugging (not an easy task). Remove all leaks from backend and fight with some incorrect referenced objects. Making GtkRunLoop able to "defer" actions to be able to go back to the main thread. NewTools Inspector "Remember" pages opened to follow the flow. For example, if you open a panel when you had selected "Items", it will try to select âitems" in the next pane. It also remembers the replaced selection (to allow for example the inspection of images when traversing a collection). Add a "refresh" button to allow refreshing inspections other than the "raw" inspection (who gets refreshed automatically) Migrate some inspector extensions. Debugger pre-debug window now uses a button bar instead a toolbar (which is more correct) TFFI fix some bugs around new literal syntax. Working in the serialization of callbacks: Callbacks should always return in the order they are called Working in the debugability of Callbacks, the callbacks code should be debuggable without affecting the stability Improving Tests Image - general Create KMShortcutPrinter to unify the way to show shortcuts all around the image. FastTable now can be configured to have rows of different height (using beRowNonHomogeneous method) For the ones using the headless vm, window losing focus to stop showing the cursor (both gtk and sdl2). Until now, cycle continued drawing the cursor, consuming CPU and making things confusing. create a way to target generic git repositories with iceberg (reacting to Sven request). VM VM now can sleep when idle. VM now can run in a separated thread from the main thread. Implementing Async I/O in Windows Experiment running SDL2 and Gtk3 in the main thread (Done for the world rendering, WIP for Mars-Gtk). Improving Debugging of callbacks in Gtk / SDL2 Preparing and Giving the Pharo Techtalk. Working in GC compactor corruption. Improving the handling of VM Parameters. Improving the API to give support to different experiments. Experimenting of running embedded images. Improving String primitives with checks on Forwarders. Cheers, Esteban

Nov. 7, 2019

Moz2d Vs. Skia

by ducasse

Hi doru and alex Can you tell me why you drop Moz2D and switch to Skia (which to us looks a much safer path starting from the packaging :)? S

Nov. 7, 2019

[Pharo 8.0] Build #950: Compiler: Document Plugin AST copying

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #949: 5062-includesKey-does-not-work-after-garbage-collect-in-WeakValueDictionary

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #948: 5063-testInstSize-fails

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #947: Kernel dependencies cleanup

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #946: remove CrLfExchangeTable

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #945: Remove-Deprecated70

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #944: Prepare Epicea for latest Spec2

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #943: Fix-protocol-and-remove-useless-method

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #942: type-for-the-entries-is-not-a-good-name

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #941: Completion: Sorter should be Instance

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #940: 2282-ProcessorScheduler-method-comment-refers-to-DelayScheduler-class-comment

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 6, 2019

[Pharo 8.0] Build #939: 2283-WorldState-refers-to-missing-class-DelayScheduler

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 5, 2019

[Pharo 8.0] Build #938: Use-platform-visitor-in-native-browser

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 5, 2019

Re: [Pharo-dev] Pharo 7 Release Update

by Sabine Manaa

I am happy about this, too. Thank you! I just tested it with my config and can confirm that zinc loads correct. But the other problem (I remember other had this, too) remains: after loading, I have an empty debugger with "Instances of Process did not understand #isValid" Anyone having this, too? I can close this debugger and everything seems fine but I just want to report. Sabine Am Di., 5. Nov. 2019 um 08:43 Uhr schrieb Sven Van Caekenberghe < sven(a)stfx.eu>: > Hi, > > As reported (by Jonathan and checked by me), the launcher now creates an > Pharo 7.0 images from version Pharo7.0.4 build: 172, commit: ecc855d. This > build correctly loads the Zinc baseline ! > > This is very good news. Thanks again Pablo. > > Now this version has to be released so that it is served by the ZeroConf > tools (get.pharo.org) which is a manual process, IIUC. > > Do we have to go to 7.0.5 ? > > Can someone do the necessary steps please ? > > Sven > > > >

Nov. 5, 2019

[Pharo 8.0] Build #937: FileSystem>>copyFileAndDelete:to: don't raise a FileDoesNotExistException if the destination doesn't exist

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 5, 2019

Pharo 7 Release Update

by Sven Van Caekenberghe

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

Nov. 5, 2019

[Pharo 8.0] Build #936: close all windows like this

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 4, 2019

[Pharo 8.0] Build #935: 4829-SugsNautilusContext-can-be-removed

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 4, 2019

[Pharo 8.0] Build #934: Cleanup: #wantsRecompilationProgressReported

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 4, 2019

[Pharo 8.0] Build #933: Completion: use #hasEntries instead of isEmpty/notEmpty

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 4, 2019

Re: [Pharo-dev] Git URL issues

by Esteban Lorenzano

I made a PR to allow âgenericâ git repositories to be referenced: https://github.com/pharo-vcs/iceberg/pull/1324 <https://github.com/pharo-vcs/iceberg/pull/1324> Butâ¦ problem is more complicated than you may think: Metacello âvanillaâ relies on download a zip file with the sources, it cannot have a âgenericâ way to act. This means the PR will work just if you use iceberg. And maybe you do not want to declare your baselines relying on iceberg. In that case, you have just one workaround possible: 1) clone locally the remove private sources outside the image. 2) load them using plain metacello and filetree://. 3) âlockâ those repositories. Then you can run your installation. Esteban > On 4 Nov 2019, at 12:52, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 01.11.2019 um 17:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> >> >>> On 31 Oct 2019, at 12:18, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> >>>> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>> >>>> >>>>> On 25 Oct 2019, at 14:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> >>>>> How do you build/deploy non-public production code using the command line ? >>>> >>>> I just learned about the following technique: >>>> >>>> Using SSH agent forwarding >>>> >>>> https://developer.github.com/v3/guides/using-ssh-agent-forwarding/ >>>> >>>> This certainly makes using certificates on production servers much easier since you do no longer have to manage or install special ones on the deployment servers, you can just use your standard developer certificates. >>>> >>> That is quite late :P I always use this as it also chains through all the machins you log in. We use jenkins for building our software there it does not work. We just have a deployment key for that. That is a key pair without passphrase that is registered in the git repository and installed on the jenkins server. >>> >>> Norbert >> >> Indeed, the SSH forwarding cannot be used for independent CI builds. >> >> I am curious though: how do you do the initial checkout (clone) from your private repository ? Using regular git command line tools or using Iceberg/Metacello ? >> >> If the latter, how do you specify your URL, exactly ? >> >> The first case works for me too, using a gitlocal:// URL, but that is cheating a bit, I feel like we should be able to do this directly in Pharo. > > If checking out from private repo your problem is as deep as you reference private repos. My project (1) is in a private repository, it contains a baseline that references a project in a private repository (2) and this references a project in a private repo (3). > > * Project (1) is checked out by jenkins. I have a deployment key pair without passphrase where the public key is registered in the bitbucket project and the private key is deployed on jenkins. > > * I try to avoid iceberg as much as possible for deployment builds because later I want to have an image without iceberg. And it is not reliable to use iceberg because metacello won't update git repos automatically and the odds are high that you load old content. So I load the project with the eval commandline handler with > > Metacello new > repository: 'filetree://source <filetree://source>'; > baseline â¦ > â¦ > > * In order to load the private projects in the the baseline of the main project I run a script before build that hacks the image in a way that > > MCBitbucketRepository compile: 'httpsUrl > ^ ''https://USER:PASS@bitbucket.org/'', projectPath, ''.git'' <https://USER:PASS@bitbucket.org/'',%20projectPath,%20''.git''>'. > > MCBitbucketRepository compile: 'projectZipUrlFor: projectPath versionString: versionString > ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'' <https://USER:PASS@bitbucket.org/''%20,%20projectPath%20,%20''/get/''%20,%20versionString%20,%20''.zip''>'. > > MCBitbucketRepository class compile: 'projectZipUrlFor: projectPath versionString: versionString > ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'' <https://USER:PASS@bitbucket.org/''%20,%20projectPath%20,%20''/get/''%20,%20versionString%20,%20''.zip''>'. > > This works only because all private projects are on bitbucket and no public one. > > * Project (3) I made public because I did not see how to make that work > > Hope this helps. I feel this to be far too complicated. Together with the confusion between pharo5/pharo6/pharo7 with iceberg, tonel and iceberg and/or tonel support killed two weeks of my time at least. So I would welcome if there would be a better way to manage credentials > > Norbert

Nov. 4, 2019

Re: [Pharo-dev] Git URL issues

by Norbert Hartl

> Am 01.11.2019 um 17:44 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >> On 31 Oct 2019, at 12:18, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> >>> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> >>> >>>> On 25 Oct 2019, at 14:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> How do you build/deploy non-public production code using the command line ? >>> >>> I just learned about the following technique: >>> >>> Using SSH agent forwarding >>> >>> https://developer.github.com/v3/guides/using-ssh-agent-forwarding/ >>> >>> This certainly makes using certificates on production servers much easier since you do no longer have to manage or install special ones on the deployment servers, you can just use your standard developer certificates. >>> >> That is quite late :P I always use this as it also chains through all the machins you log in. We use jenkins for building our software there it does not work. We just have a deployment key for that. That is a key pair without passphrase that is registered in the git repository and installed on the jenkins server. >> >> Norbert > > Indeed, the SSH forwarding cannot be used for independent CI builds. > > I am curious though: how do you do the initial checkout (clone) from your private repository ? Using regular git command line tools or using Iceberg/Metacello ? > > If the latter, how do you specify your URL, exactly ? > > The first case works for me too, using a gitlocal:// URL, but that is cheating a bit, I feel like we should be able to do this directly in Pharo. If checking out from private repo your problem is as deep as you reference private repos. My project (1) is in a private repository, it contains a baseline that references a project in a private repository (2) and this references a project in a private repo (3). * Project (1) is checked out by jenkins. I have a deployment key pair without passphrase where the public key is registered in the bitbucket project and the private key is deployed on jenkins. * I try to avoid iceberg as much as possible for deployment builds because later I want to have an image without iceberg. And it is not reliable to use iceberg because metacello won't update git repos automatically and the odds are high that you load old content. So I load the project with the eval commandline handler with Metacello new repository: 'filetree://source'; baseline â¦ â¦ * In order to load the private projects in the the baseline of the main project I run a script before build that hacks the image in a way that MCBitbucketRepository compile: 'httpsUrl ^ ''https://USER:PASS@bitbucket.org/'', projectPath, ''.git'''. MCBitbucketRepository compile: 'projectZipUrlFor: projectPath versionString: versionString ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'''. MCBitbucketRepository class compile: 'projectZipUrlFor: projectPath versionString: versionString ^ ''https://USER:PASS@bitbucket.org/'' , projectPath , ''/get/'' , versionString , ''.zip'''. This works only because all private projects are on bitbucket and no public one. * Project (3) I made public because I did not see how to make that work Hope this helps. I feel this to be far too complicated. Together with the confusion between pharo5/pharo6/pharo7 with iceberg, tonel and iceberg and/or tonel support killed two weeks of my time at least. So I would welcome if there would be a better way to manage credentials Norbert

Nov. 4, 2019

Horizontal scrolling in FastTable

by Danil Osipchuk

Hi all I wonder what is happening to the horizontal scrolling in FastTable, the stub is there for years (I've checked the latest 8.0). I need it rather badly, could someone advise what is the hindrance there? I would try doing it myself, but I've never was doing much of UI programming and only recently returned to Pharo again, so have to catch up (a lot of things changed for good). How difficult would be to adopt vertical scrolling approach (which seems to be the same problem already solved to layperson ) horizontalScrollBarValue: aNumber trialHSB ifNotNil: [ self inform: 'FTTableMorph>>#horizontalScrollBarValue: ', aNumber printString , String cr, 'Does nothing yet.' , String cr, 'Need some advise here.' ]. regards, Danil

Nov. 4, 2019

Re: [Pharo-dev] make github issues clearer?

by Nicolas Cellier

Le lun. 4 nov. 2019 Ã 07:17, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> a Ã©crit : > > This is more severe with the VM front. > > HernÃ¡n > > > Hi Hernan, could you ellaborate the problem you observe with the VM front?

Nov. 4, 2019

Re: [Pharo-dev] make github issues clearer?

by ducasse

Yes sometimes describing it takes more time than fixing it. I would encourage people complaining to participate more. (no need to tell me that if we do not describe then people cannot get it). At the end of the day, the key point is to contribute for real. Stef >> minimum reproducible example (MRE). > > +100 > > I am not sure that it needs a name (never heard it), but this should be so obvious. > > Of course there has to be code that shows the issue, as simple as possible. > > BTW I hate it when people explain their issue by saying: load a couple of complex projects, install some other software and then run it 10 times and it will probably happen.

Nov. 4, 2019

Re: [Pharo-dev] make github issues clearer?

by Sven Van Caekenberghe

> On 4 Nov 2019, at 07:16, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > minimum reproducible example (MRE). +100 I am not sure that it needs a name (never heard it), but this should be so obvious. Of course there has to be code that shows the issue, as simple as possible. BTW I hate it when people explain their issue by saying: load a couple of complex projects, install some other software and then run it 10 times and it will probably happen.

Nov. 4, 2019

Re: [Pharo-dev] make github issues clearer?

by Marcus Denker

I can tell you that it is even hard for me to understand some issue tracker entries. We really need to find a way that people add better information. For me one thing I will try to do: to not use the issue tracker anymore as my private TODO list. This means that the âI should maybe look into this but i have no time to even add a descriptionâ entries are now in my private list and if I make an issue on the issue tracker I will try to write it in a way that it explains how someone else could fix it. Marcus > On 4 Nov 2019, at 07:16, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > This is it. > > Finally this problem is spotted. It's been years since I read a Pharo issue because of their targeted "narrative" to a bunch of 5 - 10 people who share a daily operational knowledge. This is more severe with the VM front. > > Other communities, like R, use a lot minimum reproducible example (MRE). So nothing new should be invented here, if Pharo just could adopt one of the standard practices... > > Cheers, > > HernÃ¡n > > > > El mar., 29 oct. 2019 a las 8:56, Torsten Bergmann (<astares(a)gmx.de <mailto:astares@gmx.de>>) escribiÃ³: > +1000 > > I've seen this several times that issues where just a short title only "wizards" were able to understand > > The "Full description requires time" is not an argument here. We all should get more professional > and disciplined here - so anyone is able to reproduce and understand what an issue is about. This will > also increase the trust into Pharo and its dev process... > > Bye > T.

Nov. 4, 2019

Re: [Pharo-dev] make github issues clearer?

by HernÃ¡n Morales Durand

This is it. Finally this problem is spotted. It's been years since I read a Pharo issue because of their targeted "narrative" to a bunch of 5 - 10 people who share a daily operational knowledge. This is more severe with the VM front. Other communities, like R, use a lot minimum reproducible example (MRE). So nothing new should be invented here, if Pharo just could adopt one of the standard practices... Cheers, HernÃ¡n El mar., 29 oct. 2019 a las 8:56, Torsten Bergmann (<astares(a)gmx.de>) escribiÃ³: > +1000 > > I've seen this several times that issues where just a short title only > "wizards" were able to understand > > The "Full description requires time" is not an argument here. We all > should get more professional > and disciplined here - so anyone is able to reproduce and understand what > an issue is about. This will > also increase the trust into Pharo and its dev process... > > Bye > T. >

Nov. 4, 2019

Re: [Pharo-dev] I love this idea: learning by doing...

by ducasse

> On 3 Nov 2019, at 11:10, Hilaire <hilaire(a)drgeo.eu> wrote: > > There were some game frameworks project goings on with Pharo. > > What are their status? I never finished to have a look and produce something that could be used by others. Coding is just a part of the story. Explaining and presenting is the part that is often missing. > > Hilaire > > Le 03/11/2019 Ã 09:53, ducasse a Ã©crit : >> https://github.com/danistefanovic/build-your-own-x >> >> I would love to get some pharo there. >> >> Thanks sebastian for the pointer. >> >> Stef >> >> > -- > Dr. Geo > http://drgeo.eu > > >

Nov. 3, 2019

Re: [Pharo-dev] I love this idea: learning by doing...

by Hilaire

There were some game frameworks project goings on with Pharo. What are their status? Hilaire Le 03/11/2019 Ã 09:53, ducasse a Ã©critÂ : > https://github.com/danistefanovic/build-your-own-x > > I would love to get some pharo there. > > Thanks sebastian for the pointer. > > Stef > > -- Dr. Geo http://drgeo.eu

Nov. 3, 2019

I love this idea: learning by doing...

by ducasse

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

Nov. 3, 2019

[Pharo 8.0] Build #932: Put each executable comment in its own comment

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 3, 2019

[Pharo 8.0] Build #931: 3695-Epicea-shows-a-Change-that-is-not-a-change

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 2, 2019

[Pharo 8.0] Build #930: Spec based find & replace dialog

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 2, 2019

[Pharo 8.0] Build #929: executable comments

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 2, 2019

[Pharo 7.0] Build #172: 4764-Change-is-ZnBuffered-are-breaking-something-

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 2, 2019

[Pharo 8.0] Build #928: Executable comments

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 2, 2019

[Pharo 8.0] Build #927: exacutable comments for asBit method

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 2, 2019

Re: [Pharo-dev] Git URL issues

by Sven Van Caekenberghe

> On 31 Oct 2019, at 12:18, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 31.10.2019 um 12:12 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> >> >>> On 25 Oct 2019, at 14:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> How do you build/deploy non-public production code using the command line ? >> >> I just learned about the following technique: >> >> Using SSH agent forwarding >> >> https://developer.github.com/v3/guides/using-ssh-agent-forwarding/ >> >> This certainly makes using certificates on production servers much easier since you do no longer have to manage or install special ones on the deployment servers, you can just use your standard developer certificates. >> > That is quite late :P I always use this as it also chains through all the machins you log in. We use jenkins for building our software there it does not work. We just have a deployment key for that. That is a key pair without passphrase that is registered in the git repository and installed on the jenkins server. > > Norbert Indeed, the SSH forwarding cannot be used for independent CI builds. I am curious though: how do you do the initial checkout (clone) from your private repository ? Using regular git command line tools or using Iceberg/Metacello ? If the latter, how do you specify your URL, exactly ? The first case works for me too, using a gitlocal:// URL, but that is cheating a bit, I feel like we should be able to do this directly in Pharo. Sven

Nov. 1, 2019

Re: [Pharo-dev] FOSDEM rooms are available

by Santiago Bragagnolo

Great Phil! So maybe you can do the presentation your self if you would like to do it! It would be way better if we have a better user than me for doing this presentation ;). Still, i am available if it becomes complex. El jue., 31 oct. 2019 a las 12:11, phil(a)highoctane.be (<phil(a)highoctane.be>) escribiÃ³: > I should be there as well (I am local after all). > > Would be cool to do something about Grafoscopio as I use it quite often. > > Phil > > On Thu, 31 Oct 2019, 10:32 Santiago Bragagnolo, < > santiagobragagnolo(a)gmail.com> wrote: > >> Hi Offray!! I have no clue if there are scholarships. To be honest i >> don't think so, since it is completely free. but still, don't take my word. >> Check it. I can do some research on it tomorrow. >> >> If not the case, we can do the proposal together, and if they accept the >> talk we do an intensive couching / course and i present it :) >> >> El miÃ©., 30 oct. 2019 a las 0:02, Offray Vladimir Luna CÃ¡rdenas (< >> offray.luna(a)mutabit.com>) escribiÃ³: >> >>> >>> On 29/10/19 4:24 a. m., Santiago Bragagnolo wrote: >>> >>> >>> [...] >>> >>> *Communication *( >>> https://fosdem.org/2020/schedule/track/collaborative_information_and_conten… >>> https://fosdem.org/2020/schedule/track/coding_for_language_communities/ >>> ) >>> *Offray*! I think there is space for graphoscope in here. If you >>> can give a talk, great, if not, i propose my self to be the speaker (of >>> course in that case i will need some couching and teaching on the usage). >>> >>> I will love to be in Brussels for early February to give the talk, but >>> if the event has no scholarships or travel funding, I can couch you about >>> what we have being doing with Grafoscopio since 2015 and giving some >>> overview of explanatory materials including the mind maps, projects, >>> prototypes, and docs I use for the presentations. >>> >>> Thanks for keeping and eye on this and thinking in the way the wider >>> community can participate on this, >>> >>> Offray >>> >>>

Nov. 1, 2019

Re: [Pharo-dev] FOSDEM rooms are available

by Santiago Bragagnolo

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

Nov. 1, 2019