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

[Pharo 8.0] Build #52: 2338 GT Extensions should also be visible on empty directories
by ci-pharo-ci-jenkins2＠inria.fr Feb. 7, 2019

Feb. 7, 2019

There is a new Pharo build available! The status of the build #52 was: SUCCESS. The Pull Request #2339 was integrated: "2338 GT Extensions should also be visible on empty directories" Pull request url: https://github.com/pharo-project/pharo/pull/2339 Issue Url: https://pharo.fogbugz.com/f/cases/2338 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #148: Ensure subMenu is opened (backport)
by ci-pharo-ci-jenkins2＠inria.fr Feb. 6, 2019

Feb. 6, 2019

There is a new Pharo build available! The status of the build #148 was: FAILURE. The Pull Request #2376 was integrated: "Ensure subMenu is opened (backport)" Pull request url: https://github.com/pharo-project/pharo/pull/2376 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Sprints first half 2019
by Marcus Denker Feb. 5, 2019

Feb. 5, 2019

We organise one Pharo âSprintâ per month were we meet to work on boring issue tracker entries together. Goals of the next sprints: - Fix issues for Pharo8 - Backport important fixes to Pharo7 Remotely, you can join us on Discord. During the sprint, we will try to synchronize local and remote Pharo sprinters. In the past people organised local sprints at the same time (e.g. Santiago/Chile). See here for more infos: http://pharo.org/contribute-events There will be an event on the association website for each sprint. The next dates are: - 22 Feb https://association.pharo.org/event-3253818 - 29 Mar https://association.pharo.org/event-3253842 - 26 Apr https://association.pharo.org/event-3253846 - 31 May https://association.pharo.org/event-3253848 - 28 Jun https://association.pharo.org/event-3253850 For more Pharo Event, have a look at the Events Page: https://association.pharo.org/events

1 0

An article that talks about Pharo in a portal from MÃ©xico
by Esteban Lorenzano Feb. 5, 2019

Feb. 5, 2019

https://www.unocero.com/smartphones/pharo-7-internet-de-las-cosas/ <https://www.unocero.com/smartphones/pharo-7-internet-de-las-cosas/> Just presenting version 7. Couple of observations: 1. We reach farther than we think. 2. IoT has a lot of attention at this moment. Esteban

2 1

iceberg: merging branches just at the git level without changing code in the image
by Andrei Chis Feb. 5, 2019

Feb. 5, 2019

Hi, Currently in Iceberg to merge a branch into another, we need to checkout the branch into which we want to merge and then do the merge. Checking out a branch also updates the code in the image, which when needing to perform automatic releases on a branch can cause issues. Is there already a way in Iceberg to switch to a branch (for example `release`) and then merge another branch (for example `master`) into it without updating any code in the image? The use-case is that the user is on the `master` branch and needs to merge `master` into `release` without changing any code in the image. I found LGitRepository>>#merge:, but it seems not to be used anywhere in the image. Another way would be to implement something like the method below. This: - calculates what changes need to be merged - always takes what is on the left branch (in this case what is on master overrides what is on release) - does not call loadChangesInWorkingCopy: to update the working copy as the code is already in the image - refreshes the dirty packages in case there are changes between what is on the image and what is on disk ``` IceMerge>>#executeWithAcceptingLeftOnConflictAndWithoutImageUpdate | commitToAdvance | mergeCommit validateCanMerge. self isAlreadyMerged ifTrue: [ ^ self ]. self calculateChanges. self conflictsDo: [ :operation | operation selectLeft. ]. commitToAdvance := self updateHead. "Do not update the working copy" "repository workingCopy loadChangesInWorkingCopy: self changesToWorkingCopyTree." repository workingCopy refreshDirtyPackages. ^ commitToAdvance ``` Could something like the above solution work? Or are there other issues to take into account? Cheers, Andrei

3 2

[Pharo 7.0] Build #147: Add scrollSelectionIntoView
by ci-pharo-ci-jenkins2＠inria.fr Feb. 5, 2019

Feb. 5, 2019

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

1 0

ProcessBrowser does not auto-update itself by default? Should it?
by Thomas Dupriez Feb. 5, 2019

Feb. 5, 2019

Hello, The Process Browser does not auto-updates itself by default to show new processes and hide processes that stopped. Is there a specific reason for that? The first time I opened it I kind of expected it would auto-update itself, and I think this may be a more "intuitive" behaviour that no auto-updates by default. What do you think? Getting auto-updates is "easy" (there is no button in the UI (something to improve?), but one can call the "toggleAutoUpdate" method to get this behaviour). My question is about it not being default. Thomas

4 3

Camp Smalltalk Charlotte 2019 Update!
by Mariano Martinez Peck Feb. 4, 2019

Feb. 4, 2019

Hello Smalltalkers, Camp Smalltalk Charlotte 2019 is looking good! At this point we are over half full. Looks like some cool demos using different Smalltalk dialects are already lining up. A google groups forum has been created for attendees so everyone can collaborate beforehand. Attendees will get an invitation for group access shortly after registering. This event is happening March 29th â March 31st 2019 in Charlotte, North Carolina. Please register for the event as spots will be limited. Event details and registration info are available at the following link: Camp Smalltalk Charlotte 2019 <https://www.google.com/url?q=https%3A%2F%2Fwww.eventbrite.com%2Fe%2Fcamp-sm…> Hope to see you there! -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

1 0

[Pharo 8.0] Build #51: OpalCompiler-Core spelling in class comment
by ci-pharo-ci-jenkins2＠inria.fr Feb. 4, 2019

Feb. 4, 2019

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

1 0

Esteban's ChangeLog week of 28 January 2019
by estebanlm＠gmail.com Feb. 4, 2019

Feb. 4, 2019

Hello! This is my weekly ChangeLog, from 28 January 2019 to 3 February 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=28/1/2019&to=3/2/2019 ChangeLog ========= 30 January 2019: ---------------- * Still more work for the [PR](https://github.com/pharo-spec/Spec/pull/208) I submited yesterday. It is now ready to merge! 29 January 2019: ---------------- * I made a [PR](https://github.com/pharo-spec/Spec/pull/208) that adds two new elements to Spec 2: 1) SpecPanedLayout is a new layout that complements SpecBoxLayout: A paned layout is like a Box Layout (it places childen in vertical or horizontal fashion), but it will add a splitter in between, that user can drag to resize the panel. In exchange, a paned layout can have just two children. 2) NotebookPresenter is a new implementation of a tab manager. Needed because old one was not lazy, bad layouted and too attached to Morphic (while we attempt to be more backend agnostic). All of this is still WIP (there are missing functionality still), but what is there is working fine :) * I merged this [PR](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/362) from Pavel to improve keyboard handling on Windows VMs. * Now that Pharo 7.0 is out, I started work on the Pharo 8.0 roadmap (that I need to send to the list, btw). Since some weeks I've been working on Spec2 (because we will need it sooner than expected and I wanted to make some progress on its general design and needs). In Spec2, some things will be enhanced, some others replaced and some other more added from scratch. I wanted to know mor more or less were we stand to do the job. Some work I've made (along with Cyril): 1) Layouts will be revamped. Right now there is just one layout which is overpowerful but hard to use and too attached to morphic (and our goal is to be able to replace the Morphic backend with a Bloc backend). We decided to go for a different approach: instead one layout that does all, having different layouts to fulfil different needs: - +SpecBoxLayout+ (rigid panes) - +SpecPanedLayout+ (non rigid panes) - +SpecGridLayout+ (form kind layout) - +SpecFlowLayout+ (flowing components) - +SpecXYLayout+ (rigid coordinates) - And of course there will be need of a kasowary based layout. - ... ? I already implemented +SpecBoxLayout+, +SpecPanesLayout+ and a preliminary version od +SpecGridLayout+ :). 2) Interpreter will be removed. Just the old layout makes it necessary today, and it adds a complexity we do not need. 3) We will add a +TablePresenter+ (a good one) and a +TreeTablePresenter+ (again, a good one). Old versions that try to fullfil same function will be deprecated. There is already a functional preliminary version of them :) 4) We will add components for Numbers, Dates, etc. (+NumberInputFieldPresenter+ is already implemented) 5) We will revisit all other components. As a roadmap, is pretty ambicious but is looking good so far :) cheers! Esteban

2 1