- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 28 May 2018, at 12:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> Shortcomings: >> -> extensions are not treated, only the main package >> -> Not used much, for sure needs testing to see if this really works. > > â> there might be other places in addition global #compilerClass: where we need to point to the overlay version > For the complete âcompile a methodâ it works, but I think there are other cases where it is not enough. I think this one makes it really usable: https://github.com/pharo-project/pharo/pull/1455 <https://github.com/pharo-project/pharo/pull/1455> Now I can even put a halt in the semantic analysis which is called by syntax highlighting in the browser at each keystroke. Marcus

May 29, 2018

Re: [Pharo-dev] Pharo 7 on SqueakJS (demo)

by Tim Mackinnon

Interestingly - its faster on my iPhoneX than on my 2015 MacBook Pro - shows how much the processor speeds are advancing. > On 24 May 2018, at 16:51, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > Nice experiment! > The fact that it works it's a feat itself. > > Maybe in the future with WebAssembly and a lighter/core image it will > became a viable alternative. > > > > On 21/05/2018 07:01, Pavel Krivanek wrote: >> Hi, >> >> with some tweaks mostly related to FFI and fonts, we are able to run >> Pharo 7 on SqueakJS VM. >> >> Do not expect blazing performance. Currently, it is about two orders of >> magnitude slower than the native VM. >> >> https://pavel-krivanek.github.io/pharo/pharo.html >> >> Cheers, >> -- Pavel > > -- > Esteban A. Maringolo >

May 29, 2018

[ANN] Iceberg v1.0.0

by Guillermo Polito

Hi all, Time for a new Iceberg update, that will be available in the next Pharo build. This time, there are lots of cleanups and enhancements. On the big highlights: - Tonel migration plugin is available in the "Other menu item" - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 bits). Thanks to everybody that participated in reviewing, opening/closing issues or even fixing a typo! # Documentation Just as a reminder, here you have a link to iceberg's wiki, convering some info like terminology, how to help us, and so on... https://github.com/pharo-vcs/iceberg/wiki # And some videos ;) - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI - Loading a Baseline https://youtu.be/brUHEOr-p_E - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M # Changes Log https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 Enjoy, Guille PS, detailed changes log below: # Cleanups #819 Fix tooltip typo in settings #800 Iceberg should be removed from the catalogue #801 Remove not referenced packages #803 Correct some lints in tests #806 Bad repair options when local repository is missing #725 Remove and clean old UI #794 Some classes should use category "utilities" instead of "utility" #791 Begin to remove old UI #734 Begin to remove old UI #576 Add link to github/gitlab ssh instructions # Enhancements #776 Upgrade to Commander 0.6.2 dependencies #765 Add command to copy SHA from history window #793 Add the commit message to history window #785 Metacello conflicts are not handled Metacello Integration # Bug fixes #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not implemented #748 Code subdirectory in empty repository #767 Error while pulling with renamed packages #814 Moving extension from a package removes extended class #807 When we do not have the right to push on a report we get an Error instead of the pop up! #768 Inverse merge preview shows wrong diff #784 Pulling from a non existing remote branch fails#810 #removePackage: should recursively delete files # Documentation #702 Create screencast - How to contribute to iceberg #774 Copy Wiki contribution page to pharo-project/pharo wiki # Infrastructure #761 Make tests run in 64 bits Pharo 7

May 29, 2018

Re: [Pharo-dev] Horrible mess in keyboard modifiers processing

by Nicolas Cellier

2018-05-29 9:58 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > He, i think this may be a VM issue. I've fixed part of the keyboard event > handling in the past, but it's effectively a mess... > Yes, there are some issues opened already https://github.com/OpenSmalltalk/opensmalltalk-vm/issues?utf8=%E2%9C%93&q=i… https://github.com/OpenSmalltalk/opensmalltalk-vm/issues?utf8=%E2%9C%93&q=i… Feel free to complete or open new ones if necessary. > >

May 29, 2018

[Pharo 7.0-dev] Build #977: 21951-Deprecate-FileDoesNotExist

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

There is a new Pharo build available! The status of the build #977 was: FAILURE. The Pull Request #1447 was integrated: "21951-Deprecate-FileDoesNotExist" Pull request url: https://github.com/pharo-project/pharo/pull/1447 Issue Url: https://pharo.fogbugz.com/f/cases/21951 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 29, 2018

Re: [Pharo-dev] Horrible mess in keyboard modifiers processing

by phil＠highoctane.be

I think that we could address this by using left or right Alt/Ctrl to emulate Cmd. There is no way out of the fact that the Mac has some that Cmd key. We have a Windows key but it is out of reach for most of the usages. Capslock comes to mind... Phil On Tue, May 29, 2018 at 9:58 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > He, i think this may be a VM issue. I've fixed part of the keyboard event > handling in the past, but it's effectively a mess... > > On Tue, May 29, 2018 at 9:45 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Btw I've opened an issue for this (for linux) last month >> https://pharo.fogbugz.com/f/cases/21732/left-click-ctr >> l-is-unsuable-on-Linux >> >> > The Ctrl key does not have correct modifier flag when the mouse is >> pressed >> >> Note in the linked issue, that the modifier is present on mouseUp. My >> understanding is that mouseDown it is being replaced by a different event >> somewhere inside Pharo (maybe the mentioned InputEventSensor >> class>>swapMouseButtons ?) >> >> Peter >> >> On Mon, May 28, 2018 at 6:02 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com >> > wrote: >> >>> On Linux and Windows, the keyboard usage is very limited, especially in >>> combination with the mouse. There is no way how to invoke any key >>> corresponding to Mac command key (â). As result there are is no option >>> how on these platforms select several nonadjacent methods in Calypso to >>> display them at once and you cannot click on a method selector to reach the >>> implementation. >>> >>> I tried to log modifiers on input events on all three platforms and this >>> is the sad result: >>> >>> Mac: >>> shift 0 1 1 0 >>> ctrl 0 2 2 0 >>> option (â¥) 0 4 4 0 >>> command (â) 0 8 8 0 >>> >>> The numbers are in order: >>> - modifier key pressed >>> - mouse down >>> - mouse up >>> - modifier key released >>> >>> So on Mac the mouse events are processed correctly but the events >>> related keyboard have no modifiers flags. >>> >>> Linux: >>> shift 0 1 1 0 >>> ctrl 0 0 2 0 >>> win - 0 0 - >>> alt 0 - - 0 >>> altgr - 0 0 - >>> >>> So on Linux the Shift key is processed correctly, The Ctrl key does not >>> have correct modifier flag when the mouse is pressed (which is strange >>> because the combination of Shift+Ctrl returns 0 3 3 0). Win key changes >>> click behavior to right mouse button. For Alt the mouse events are not >>> detected at all and AltGr behaves as Win except the right mouse button >>> simulation. The keyboard event modifiers are not set. >>> >>> Windows: >>> shift 16 1 1 1 16 >>> ctrl 17 2 2 2 17 >>> win - 0 0 0 - >>> alt 18 8 8 8 18 >>> altgr 18 8 8 8 18 >>> >>> Windows as the only platform set modifiers for keyboard events. The >>> mouse button release generates two events, Win key changes behavior to >>> right mouse button, and Alt behaves the same way as AltGr. >>> >>> Cheers, >>> -- Pavel >>> >>> >>> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

May 29, 2018

Re: [Pharo-dev] Horrible mess in keyboard modifiers processing

by Guillermo Polito

He, i think this may be a VM issue. I've fixed part of the keyboard event handling in the past, but it's effectively a mess... On Tue, May 29, 2018 at 9:45 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Btw I've opened an issue for this (for linux) last month > https://pharo.fogbugz.com/f/cases/21732/left-click- > ctrl-is-unsuable-on-Linux > > > The Ctrl key does not have correct modifier flag when the mouse is > pressed > > Note in the linked issue, that the modifier is present on mouseUp. My > understanding is that mouseDown it is being replaced by a different event > somewhere inside Pharo (maybe the mentioned InputEventSensor > class>>swapMouseButtons ?) > > Peter > > On Mon, May 28, 2018 at 6:02 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> On Linux and Windows, the keyboard usage is very limited, especially in >> combination with the mouse. There is no way how to invoke any key >> corresponding to Mac command key (â). As result there are is no option >> how on these platforms select several nonadjacent methods in Calypso to >> display them at once and you cannot click on a method selector to reach the >> implementation. >> >> I tried to log modifiers on input events on all three platforms and this >> is the sad result: >> >> Mac: >> shift 0 1 1 0 >> ctrl 0 2 2 0 >> option (â¥) 0 4 4 0 >> command (â) 0 8 8 0 >> >> The numbers are in order: >> - modifier key pressed >> - mouse down >> - mouse up >> - modifier key released >> >> So on Mac the mouse events are processed correctly but the events related >> keyboard have no modifiers flags. >> >> Linux: >> shift 0 1 1 0 >> ctrl 0 0 2 0 >> win - 0 0 - >> alt 0 - - 0 >> altgr - 0 0 - >> >> So on Linux the Shift key is processed correctly, The Ctrl key does not >> have correct modifier flag when the mouse is pressed (which is strange >> because the combination of Shift+Ctrl returns 0 3 3 0). Win key changes >> click behavior to right mouse button. For Alt the mouse events are not >> detected at all and AltGr behaves as Win except the right mouse button >> simulation. The keyboard event modifiers are not set. >> >> Windows: >> shift 16 1 1 1 16 >> ctrl 17 2 2 2 17 >> win - 0 0 0 - >> alt 18 8 8 8 18 >> altgr 18 8 8 8 18 >> >> Windows as the only platform set modifiers for keyboard events. The mouse >> button release generates two events, Win key changes behavior to right >> mouse button, and Alt behaves the same way as AltGr. >> >> Cheers, >> -- Pavel >> >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 29, 2018

Re: [Pharo-dev] Horrible mess in keyboard modifiers processing

by Peter UhnÃ¡k

Btw I've opened an issue for this (for linux) last month https://pharo.fogbugz.com/f/cases/21732/left-click-ctrl-is-unsuable-on-Linux > The Ctrl key does not have correct modifier flag when the mouse is pressed Note in the linked issue, that the modifier is present on mouseUp. My understanding is that mouseDown it is being replaced by a different event somewhere inside Pharo (maybe the mentioned InputEventSensor class>>swapMouseButtons ?) Peter On Mon, May 28, 2018 at 6:02 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > On Linux and Windows, the keyboard usage is very limited, especially in > combination with the mouse. There is no way how to invoke any key > corresponding to Mac command key (â). As result there are is no option > how on these platforms select several nonadjacent methods in Calypso to > display them at once and you cannot click on a method selector to reach the > implementation. > > I tried to log modifiers on input events on all three platforms and this > is the sad result: > > Mac: > shift 0 1 1 0 > ctrl 0 2 2 0 > option (â¥) 0 4 4 0 > command (â) 0 8 8 0 > > The numbers are in order: > - modifier key pressed > - mouse down > - mouse up > - modifier key released > > So on Mac the mouse events are processed correctly but the events related > keyboard have no modifiers flags. > > Linux: > shift 0 1 1 0 > ctrl 0 0 2 0 > win - 0 0 - > alt 0 - - 0 > altgr - 0 0 - > > So on Linux the Shift key is processed correctly, The Ctrl key does not > have correct modifier flag when the mouse is pressed (which is strange > because the combination of Shift+Ctrl returns 0 3 3 0). Win key changes > click behavior to right mouse button. For Alt the mouse events are not > detected at all and AltGr behaves as Win except the right mouse button > simulation. The keyboard event modifiers are not set. > > Windows: > shift 16 1 1 1 16 > ctrl 17 2 2 2 17 > win - 0 0 0 - > alt 18 8 8 8 18 > altgr 18 8 8 8 18 > > Windows as the only platform set modifiers for keyboard events. The mouse > button release generates two events, Win key changes behavior to right > mouse button, and Alt behaves the same way as AltGr. > > Cheers, > -- Pavel > > >

May 29, 2018

[Pharo 7.0-dev] Build #976: 22000-Click-on-the-taskbar-empty-space-should-open-the-world-menu

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

There is a new Pharo build available! The status of the build #976 was: SUCCESS. The Pull Request #1454 was integrated: "22000-Click-on-the-taskbar-empty-space-should-open-the-world-menu" Pull request url: https://github.com/pharo-project/pharo/pull/1454 Issue Url: https://pharo.fogbugz.com/f/cases/22000 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 29, 2018

Re: [Pharo-dev] IMPORTANT: ML Etiquette

by monty

> Sent: Sunday, May 27, 2018 at 11:48 PM > From: "Sean P. DeNigris" <sean(a)clipperadams.com> > To: pharo-dev(a)lists.pharo.org > Subject: [Pharo-dev] IMPORTANT: ML Etiquette > > Dear all, > > There were several posts in the "Beacon for Pharo 7" thread which top-posted > on top of massive unsnipped quotes that were several-previous-posts deep. > IMHO this made the conversation impossible to follow. This issue has cropped > up from time to time in other threads. > > Please adhere to basic ML etiquette [1] to maximize our effectiveness. Two > essential guidelines are: > 1) snip quoted material to just what's necessary to understand what's > being replied to > 2) Post reply /after/ the quote from the OP, not before. 3) Use plain text. Disable any HTML formatting in your mail client. > 1. > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiqu… > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > ___ montyos.wordpress.com

May 29, 2018