- Pharo-dev - lists.pharo.org

[ANN] Complishon: efficient heuristics for code completion

by Guillermo Polito

Hi all, Since yesterday, Pharo 9 contains a new alternative code completion engine. The idea behind this engine is to be pluggable, to be efficient and to be more accurate through the introduction of heuristics. The completion engine implements a couple of nice heuristics, like - chances are `anOrderedCollection` references an ordered collection - chances are you want to auto-complete messages implemented in the same package New heuristics can be added easily (I was playing with plugging heuristics using type inference like roel typer). If you want more details, check the blogpost: https://masteringobjects.wordpress.com/2020/03/30/complishon-efficient-heur… <https://masteringobjects.wordpress.com/2020/03/30/complishon-efficient-heur…> And if you have ideas for new heuristics that could make your Pharo experience better, let us know! Cheers, Guille

March 31, 2020

[Pharo 9.0] Build #202: Implementing a new iteration on top of spotter.

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

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

March 30, 2020

[Pharo 9.0] Build #201: Integrating HeuristicCompletion

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

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

March 30, 2020

[Pharo 9.0] Build #200: TypoFix-additionalMethodStateRefersToLitteral

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

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

March 30, 2020

[Pharo 9.0] Build #199: 2383 Cleanup DoubleLinkedList packages

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

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

March 30, 2020

Re: [Pharo-dev] [Mm10s] 2020-03-30

by tesonep＠gmail.com

### Last week: - [IdleVM] Fixing the debugging of callbacks and non callbacks (with Esteban) - [LargeImages] Improving Aleph indexes generation time - [LargeImages] Documentation of Aleph, Spotter and the Large image support baseline - Reading and validating PRs - [LargeImages] Working on improving the speed and responsiveness of large images. - [LargeImages] Creating Large Image baseline - [LargeImages] Integrating new Spotter in the image - [LargeImages] Integrating HeuristicCompletion in the image - [LargeImages] Adding GCConfiguration to improve the generation of indexes. - Consortium Organization Meeting - VM Journal Club - Fixing class side traits saving in Tonel - Adding tests to Tonel - Adding tests to Iceberg - Fixing the issue - Fixing problems in MCTraitDefinition and MCClassTraitDefinition - New versions of Iceberg & Tonel - PR to the image ### This week (starting 2020-03-30): - When everything integrated in the image, release of LargeImageSupport - Improving crash report of the VM - [VM] Check the crash dumps in an endless loop - Crash when executing a Metacello from github in the minimal image with the headless vm - Fixing Package List / Categories in Calypso - [VM] Fixing Tests in Idle. - Adding a label to a PR when it has no test errors. - [Pharo9] Propose a PR for Fuel to support Sista - [VM] Fix symbolic links in Pharo8 VM ### The rest of my pipeline - [Doc] Pass on VM booklet: Callback chapter / Preface - [VM] Documenting GC, participating in the GC code dojo. - [VM] SDL Plugin for Idle. - [VM] Improving Speed of TFFI. - [VM] REPL example / Interacting with an image from outside (?) - [PharoCOM] Making it run with TFFI. - [VM] Writing tests for JIT generation - [OSSubprocess] Integrate Pavel + Christophe windows version. - [VM] Improve the usage of Stdout and Stderr, in a correct way On Mon, Mar 30, 2020 at 10:28 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > ### Last week: > > * [idlevm] working with Pablo on the revamp of callbacks mechanism. Still WIP :( > * [idlevm] refactor into GtkDebugSession and GtkMorphicUIManager and allow them to be chosen > (Just to not crash the image while doing tests). > * [spec2] fix keybindings of text editors (they need to be redirected to textArea instead the > rubric morph) > * [spec2] fix printit on SpCodePresenter (still, I need to use a popover on it... but one thing > at a time) > * [spec2] spent a ridiculous amount of time refactoring the baseline. > * [spec2] fix an error while emulating keystrokes to tests keybindings. > * [spec2] fix SpToolCommands related to interaxcting with the code. > * [NewTools-Playground] bug: cmd+b in class shows SpCodePresenter > * [spec2] removed autoAccept and acceptoOnCr from text logic (this is a remain of > Morphic era, and it shouldnât be there in a widget library) > * Spec2: deal with the modal problem on Spec2-Morphic > * [spec2] add "defaultKeyboardFocus" concept to transmit directly to a specific child (yes, we > have the focusOrder concept, but this is to easy direct transmission. > * [spec2] enhanced SpCodePresenter source completion in Gtk (now it is not showing the popup > always, just when there is a word to complete) > > ### This week (starting 2020-03-30): > > * [idlevm] more on the revamp of callbacks > * [spec2] enhance SpMenuPresenter (to allow checkboxes and etc.) > * [spec2] more on SpCodePresenter > * [newtools]] more on StPlayground -- Pablo Tesone. tesonep(a)gmail.com

March 30, 2020

[Mm10s] 2020-03-30

by Esteban Lorenzano

### Last week: * [idlevm] working with Pablo on the revamp of callbacks mechanism. Still WIP :( * [idlevm] refactor into GtkDebugSession and GtkMorphicUIManager and allow them to be chosen (Just to not crash the image while doing tests). * [spec2] fix keybindings of text editors (they need to be redirected to textArea instead the rubric morph) * [spec2] fix printit on SpCodePresenter (still, I need to use a popover on it... but one thing at a time) * [spec2] spent a ridiculous amount of time refactoring the baseline. * [spec2] fix an error while emulating keystrokes to tests keybindings. * [spec2] fix SpToolCommands related to interaxcting with the code. * [NewTools-Playground] bug: cmd+b in class shows SpCodePresenter * [spec2] removed autoAccept and acceptoOnCr from text logic (this is a remain of Morphic era, and it shouldnât be there in a widget library) * Spec2: deal with the modal problem on Spec2-Morphic * [spec2] add "defaultKeyboardFocus" concept to transmit directly to a specific child (yes, we have the focusOrder concept, but this is to easy direct transmission. * [spec2] enhanced SpCodePresenter source completion in Gtk (now it is not showing the popup always, just when there is a word to complete) ### This week (starting 2020-03-30): * [idlevm] more on the revamp of callbacks * [spec2] enhance SpMenuPresenter (to allow checkboxes and etc.) * [spec2] more on SpCodePresenter * [newtools]] more on StPlayground

March 30, 2020

Re: [Pharo-dev] Iceberg Bug? Branches with $/

by Bernhard Pieber

While that may be true, I'd like to note that git-flow [1], one of the most widely used Git workflows, uses slashes in its default conventions. Bernhard [1] https://github.com/petervanderdoes/gitflow-avh > Am 14.01.2020 um 05:35 schrieb Ben Coman <btc(a)openInWorld.com>: > > Even from the command line I find slashes in branch names problematic, > because slashes are as a "remote/branch" separator incites confusion about what is being referenced. > > Other have different problems... > > https://stackoverflow.com/questions/273695/what-are-some-examples-of-common… > "slashes can cause problems. Because branches are implemented as paths, > you cannot have a branch named "foo" and another branch named "foo/bar". This can be confusing for new users." > > "I'm going to start a campaign to never use slashes in git branch naming. The reason for this is that if on a CI for example, > you want to refer to the branch name when packaging code for example, you want to refer to the name of the branch > when building a URI or PATH (for example), perhaps building a URI in a bash script; you will have trouble building the URI due > to the slash adding a URL part. Yes its possible to replace the slash but it is going to take me to much time to sort out." > > > https://news.ycombinator.com/item?id=8872683 > "If you use '/' is branch names you can create path conflicts. I've seen it happen and it took me a day to debug and figure out. > There is some code checking for path conflicts in the git source but it's not invoked via all code paths that create branches. > I recommend against using slashes in branch names unless you know what you are doing. > For example: > $ git branch fireos > $ git branch fireos/feature-branch > error: unable to create directory for .git/refs/heads/fireos/feature-branch > fatal: Failed to lock ref for update: No such file or directory > This happens because creating 'fireos' branch stores the sha1 in file .git/refs/heads/fireos. > But if you later want to create branch 'fireos/feature-branch', git needs to store the sha1 in .git/refs/heads/fireos/feature-branch. > This is impossible because 'fireos' is a file and cannot be a directory. Path conflict. > > It gets even uglier when you don't discover those conflicts until a pull or push. > > cheers -ben > > > > > > > On Tue, 14 Jan 2020 at 07:45, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > As per common Git workflow, I named an issue branch "port/mac-pharo-7". When > trying to load via: > Metacello new > baseline: 'VLC'; > repository: 'github://seandenigris/Pharo-LibVLC:port/mac-pharo-7'; > onConflict: [ :ex | ex allow ]; > load. > > I got: NotFound: Revspec 'port' not found.. > > Bug? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 29, 2020

[Pharo 9.0] Build #198: 6012-Click-outside-of-completion-pop-up-should-close-it

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

There is a new Pharo build available! The status of the build #198 was: SUCCESS. The Pull Request #6017 was integrated: "6012-Click-outside-of-completion-pop-up-should-close-it" Pull request url: https://github.com/pharo-project/pharo/pull/6017 Issue Url: https://github.com/pharo-project/pharo/issues/6012 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #197: Queue pending mouse events

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

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

March 27, 2020