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

Re: [Pharo-dev] Esteban's ChangeLog week of 28 January 2019

by ducasse

Great ChangeLog!!!! Thanks esteban! > On 4 Feb 2019, at 08:00, estebanlm(a)gmail.com wrote: > > 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 >

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Alistair Grant

Hi Stef, On Sun, 3 Feb 2019 at 21:56, ducasse <stepharo(a)netcourrier.com> wrote: > > HI alistair > > you should use the latest pillar. Was dev-7 and now it is 70 > because this is around six months that we removed the dependency to grease. I can see the dev-7 branch (which is what I'm using in Pharo 8). But what do you mean by "now it is 70"? Thanks, Alistair

Feb. 4, 2019

Esteban's ChangeLog week of 28 January 2019

by estebanlm＠gmail.com

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

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by ducasse

HI alistair you should use the latest pillar. Was dev-7 and now it is 70 because this is around six months that we removed the dependency to grease. Now if you need help to migrate a book/doc from pillar 6 to 7 let me know I can help. I migrated many of the books to validate Pillar 70. It is three weeks that we do not find the time to officially release it but it is super stable. Stef > On 3 Feb 2019, at 21:48, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Cyril & Sven, > > I was loading an old version of Pillar, so that solves the Grease version info. > > Thanks again, > Alistair > > > On Sun, 3 Feb 2019 at 19:25, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Cyril & Sven, >> >> Thanks for the pointer. I'll have to figure out why it is being >> loaded from smalltalkhub - maybe Pillar? Anyway, I'll have a look. >> >> Thanks again, >> Alistair >> >> On Sun, 3 Feb 2019 at 19:22, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> >>> >>> >>> On Sun 3 Feb 2019 at 19:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> >>>> Hi All, >>>> >>>> It looks like Grease is still hosted on smalltalkhub - if not, please >>>> let me know where. >>> >>> >>> Hi, >>> >>> Here: >>> >>> https://github.com/SeasideSt/Grease >>> >>> :) >>> >>>> >>>> Are there any objections to me updating >>>> ConfigurationOfGrease>>release1: to load on Pharo8? >>>> >>>> The updated method is (apologies for loss of formatting): >>>> >>>> release1: aSpec >>>> <symbolicVersion:#'release1'> >>>> aSpec for: #'pharo3.x' version: #'release1.3'. >>>> aSpec for: #'pharo4.x' version: #'release1.3'. >>>> aSpec for: #'pharo5.x' version: #'release1.3'. >>>> aSpec for: #'pharo6.x' version: #'release1.3'. >>>> aSpec for: #'pharo7.x' version: #'release1.3'. >>>> aSpec for: #'pharo8.x' version: #'release1.3'. >>>> aSpec for: #'squeak5.x' version: #'release1.3'. >>>> aSpec for: #'gs3.x' version: #'release1.3'. >>>> aSpec for: #'pharo1.x' version: #'release1.2'. >>>> aSpec for: #'pharo2.x' version: #'release1.2'. >>>> aSpec for: #'squeak4.x' version: #'release1.2'. >>>> aSpec for: #'gs2.x' version: #'release1.2' >>>> >>>> The change is the addition of the #'pharo8.x' line. >>>> >>>> Thanks, >>>> Alistair >>>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >

Feb. 3, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Alistair Grant

Hi Cyril & Sven, I was loading an old version of Pillar, so that solves the Grease version info. Thanks again, Alistair On Sun, 3 Feb 2019 at 19:25, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Cyril & Sven, > > Thanks for the pointer. I'll have to figure out why it is being > loaded from smalltalkhub - maybe Pillar? Anyway, I'll have a look. > > Thanks again, > Alistair > > On Sun, 3 Feb 2019 at 19:22, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > > > > > On Sun 3 Feb 2019 at 19:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: > >> > >> Hi All, > >> > >> It looks like Grease is still hosted on smalltalkhub - if not, please > >> let me know where. > > > > > > Hi, > > > > Here: > > > > https://github.com/SeasideSt/Grease > > > > :) > > > >> > >> Are there any objections to me updating > >> ConfigurationOfGrease>>release1: to load on Pharo8? > >> > >> The updated method is (apologies for loss of formatting): > >> > >> release1: aSpec > >> <symbolicVersion:#'release1'> > >> aSpec for: #'pharo3.x' version: #'release1.3'. > >> aSpec for: #'pharo4.x' version: #'release1.3'. > >> aSpec for: #'pharo5.x' version: #'release1.3'. > >> aSpec for: #'pharo6.x' version: #'release1.3'. > >> aSpec for: #'pharo7.x' version: #'release1.3'. > >> aSpec for: #'pharo8.x' version: #'release1.3'. > >> aSpec for: #'squeak5.x' version: #'release1.3'. > >> aSpec for: #'gs3.x' version: #'release1.3'. > >> aSpec for: #'pharo1.x' version: #'release1.2'. > >> aSpec for: #'pharo2.x' version: #'release1.2'. > >> aSpec for: #'squeak4.x' version: #'release1.2'. > >> aSpec for: #'gs2.x' version: #'release1.2' > >> > >> The change is the addition of the #'pharo8.x' line. > >> > >> Thanks, > >> Alistair > >> > > -- > > Cyril Ferlicot > > https://ferlicot.fr

Feb. 3, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Alistair Grant

Hi Cyril & Sven, Thanks for the pointer. I'll have to figure out why it is being loaded from smalltalkhub - maybe Pillar? Anyway, I'll have a look. Thanks again, Alistair On Sun, 3 Feb 2019 at 19:22, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > On Sun 3 Feb 2019 at 19:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi All, >> >> It looks like Grease is still hosted on smalltalkhub - if not, please >> let me know where. > > > Hi, > > Here: > > https://github.com/SeasideSt/Grease > > :) > >> >> Are there any objections to me updating >> ConfigurationOfGrease>>release1: to load on Pharo8? >> >> The updated method is (apologies for loss of formatting): >> >> release1: aSpec >> <symbolicVersion:#'release1'> >> aSpec for: #'pharo3.x' version: #'release1.3'. >> aSpec for: #'pharo4.x' version: #'release1.3'. >> aSpec for: #'pharo5.x' version: #'release1.3'. >> aSpec for: #'pharo6.x' version: #'release1.3'. >> aSpec for: #'pharo7.x' version: #'release1.3'. >> aSpec for: #'pharo8.x' version: #'release1.3'. >> aSpec for: #'squeak5.x' version: #'release1.3'. >> aSpec for: #'gs3.x' version: #'release1.3'. >> aSpec for: #'pharo1.x' version: #'release1.2'. >> aSpec for: #'pharo2.x' version: #'release1.2'. >> aSpec for: #'squeak4.x' version: #'release1.2'. >> aSpec for: #'gs2.x' version: #'release1.2' >> >> The change is the addition of the #'pharo8.x' line. >> >> Thanks, >> Alistair >> > -- > Cyril Ferlicot > https://ferlicot.fr

Feb. 3, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Sven Van Caekenberghe

> On 3 Feb 2019, at 19:19, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi All, > > It looks like Grease is still hosted on smalltalkhub - if not, please > let me know where. The main repo is https://github.com/SeasideSt/Seaside and has been for a while > Are there any objections to me updating > ConfigurationOfGrease>>release1: to load on Pharo8? > > The updated method is (apologies for loss of formatting): > > release1: aSpec > <symbolicVersion:#'release1'> > aSpec for: #'pharo3.x' version: #'release1.3'. > aSpec for: #'pharo4.x' version: #'release1.3'. > aSpec for: #'pharo5.x' version: #'release1.3'. > aSpec for: #'pharo6.x' version: #'release1.3'. > aSpec for: #'pharo7.x' version: #'release1.3'. > aSpec for: #'pharo8.x' version: #'release1.3'. > aSpec for: #'squeak5.x' version: #'release1.3'. > aSpec for: #'gs3.x' version: #'release1.3'. > aSpec for: #'pharo1.x' version: #'release1.2'. > aSpec for: #'pharo2.x' version: #'release1.2'. > aSpec for: #'squeak4.x' version: #'release1.2'. > aSpec for: #'gs2.x' version: #'release1.2' > > The change is the addition of the #'pharo8.x' line. > > Thanks, > Alistair >

Feb. 3, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Cyril Ferlicot

On Sun 3 Feb 2019 at 19:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi All, > > It looks like Grease is still hosted on smalltalkhub - if not, please > let me know where. > Hi, Here: https://github.com/SeasideSt/Grease :) > Are there any objections to me updating > ConfigurationOfGrease>>release1: to load on Pharo8? > > The updated method is (apologies for loss of formatting): > > release1: aSpec > <symbolicVersion:#'release1'> > aSpec for: #'pharo3.x' version: #'release1.3'. > aSpec for: #'pharo4.x' version: #'release1.3'. > aSpec for: #'pharo5.x' version: #'release1.3'. > aSpec for: #'pharo6.x' version: #'release1.3'. > aSpec for: #'pharo7.x' version: #'release1.3'. > aSpec for: #'pharo8.x' version: #'release1.3'. > aSpec for: #'squeak5.x' version: #'release1.3'. > aSpec for: #'gs3.x' version: #'release1.3'. > aSpec for: #'pharo1.x' version: #'release1.2'. > aSpec for: #'pharo2.x' version: #'release1.2'. > aSpec for: #'squeak4.x' version: #'release1.2'. > aSpec for: #'gs2.x' version: #'release1.2' > > The change is the addition of the #'pharo8.x' line. > > Thanks, > Alistair > > -- Cyril Ferlicot https://ferlicot.fr

Feb. 3, 2019

ConfigurationOfGrease for Pharo8

by Alistair Grant

Hi All, It looks like Grease is still hosted on smalltalkhub - if not, please let me know where. Are there any objections to me updating ConfigurationOfGrease>>release1: to load on Pharo8? The updated method is (apologies for loss of formatting): release1: aSpec <symbolicVersion:#'release1'> aSpec for: #'pharo3.x' version: #'release1.3'. aSpec for: #'pharo4.x' version: #'release1.3'. aSpec for: #'pharo5.x' version: #'release1.3'. aSpec for: #'pharo6.x' version: #'release1.3'. aSpec for: #'pharo7.x' version: #'release1.3'. aSpec for: #'pharo8.x' version: #'release1.3'. aSpec for: #'squeak5.x' version: #'release1.3'. aSpec for: #'gs3.x' version: #'release1.3'. aSpec for: #'pharo1.x' version: #'release1.2'. aSpec for: #'pharo2.x' version: #'release1.2'. aSpec for: #'squeak4.x' version: #'release1.2'. aSpec for: #'gs2.x' version: #'release1.2' The change is the addition of the #'pharo8.x' line. Thanks, Alistair

Feb. 3, 2019

Re: [Pharo-dev] Spotter shortcut reset

by Nicolas Cellier

Oups, it seems that my mail client was lagging... Le dim. 3 fÃ©vr. 2019 Ã 17:19, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> a Ã©crit : > Ben, > The figures in the table are quite linear. > Duration * rate = constant. > > It's just that you want to plot 1/ duration or 1/ rate if you don't want > to see an hyperbole xÃy=cte > > Le dim. 3 fÃ©vr. 2019 Ã 12:17, ducasse <stepharo(a)netcourrier.com> a Ã©crit : > >> Wouahhhhhh you are not playing :) >> This is cool. >> My network at home is lame to the dispear of my sons. >> >> Stef >> >> >> On 3 Feb 2019, at 12:06, Ben Coman <btc(a)openinworld.com> wrote: >> >> >> On Sat, 2 Feb 2019 at 18:54, ducasse <stepharo(a)netcourrier.com> wrote: >> > On Sat, 2 Feb 2019 at 11:01, Ben Coman <btc(a)openinworld.com> wrote: >> > >> > > I am getting network errors trying to download latest Pharo Launcher, >> > >> > can you tell me how so that I try to reproduce it? >> >> Since network performance depends a lot on location, and presuming you'd >> need to be at my house to reproduce my experience, >> I spent the afternoon learning about AWS so I could do some testing from >> a Australian based cloud box >> that you should be able to reproduce fairly easily, since this was my >> first time using AWS. >> >> With this 10 minute tutorial... >> [Launch a Linux Virtual Machine]( >> https://aws.amazon.com/getting-started/tutorials/launch-a-virtual-machine/ >> ) >> 1. Signed up and signed in >> Tip: I struggled a long while looping on "Sign in with root account >> credentials" until I discovered I needed to use the email address I signed >> up with, not the account name. >> >> [Edit:] In the top right between account name and support, >> pulled down list and selected "Asia Pacfic (Sydney)" >> >> >> 2. Clicked "Launch a virtual machine" >> (note, that only seems to show up for blank account, otherwise its >> "Launch Instance" >> >> >> 3. Ticked "Free tier only" filter. >> + Selected "Amazon Linux 2 AMI (HVM), SSD Volume Type" >> + Clicked <Review and Launch> (used default t2.micro) >> + Clicked <Launch> >> + From the pull-down selected "Create a new key pair", >> gave it a name and clicked <Download Keypair> saved as >> "SydneyPharoSpeedTest.pem" >> + Clicked <Launch Instance> >> + Clicked <View Instances> >> noted instance... >> * IP address: 54.252.136.78 >> * Zone: ap-southeast-2b >> * Security Group: Launch Wizard 1 >> >> 4. On my Windows 10 box, in WSL did... >> $ cd ~/.ssh # if it doesn't exist, first do... mkdir -m 700 ~/.ssh >> $ cp /mnt/c/Users/Ben/Downloads/SydneyPharoSpeedTest.pem ~/.ssh >> $ chmod 400 ~/.ssh/SydneyPharoSpeedTest.pem >> $ ssh -i ~/.ssh/SydneyPharoSpeedTest.pem ubuntu(a)54.252.136.78$ cat >> /etc/os-release >> ID="amzn" >> ID_LIKE="centos rhel fedora" >> >> >> GOOD NETWORK BASELINE TEST... >> Ignoring any packet loss on poor networks, first testing low bandwidths >> on a good network >> $ vi test.sh >> #!/bin/sh >> if [ -d out ]; then >> dirdate=`stat -c %z out | awk '{print $1"-"$2}' ` >> mv out out.${dirdate} >> fi >> mkdir out >> for RATE in 1000k 500k 200k 100k 50k 20k 10k 5k 2k 1k >> do >> echo $RATE >> /usr/bin/time -f "%e" -o out/time.$RATE \ >> wget --quiet --limit-rate $RATE >> https://files.pharo.org/pharo-launcher/1.6/pharo-launcher-1.6.msi -O >> out/file.$RATE & >> done >> >> $ sh test.sh >> monitoring with... >> $ cat out/time* | sort -n >> $ ls -lS out >> >> results in following table and graphs... >> $RATE >> (kb/s) TIME >> (s) TIME >> (min) TIME >> (hr) >> 1000 54 1 0.0 >> 500 105 2 0.0 >> 200 259 4 0.1 >> 100 515 9 0.1 >> 50 1029 17 0.3 >> 20 2576 43 0.7 >> 10 5149 86 1.4 >> 5 10527 175 2.9 >> >> <download-speed.png> >> >> Wow that surprised me. I'm not sure what the behaviour of file servers >> at low bandwidth should be, >> but intuitively the above seems odd. In the past troubleshooting seems >> to have been >> focused on the cause of slow speeds, but these can occur for many reasons >> unrelated to the >> the file server. The above test ignores cause to isolate behaviour at >> slow speeds. >> >> I forgot my own download speed yesterday (today is okay), but here is >> another sample... >> "(in Argentina) it is really slow ... 3.5KB/s ... average 10KB/s". >> http://forum.world.st/Pharo-Downloads-are-sluggish-td5084963.html >> >> I would hope that download time was near linear with speed all the way >> down to 1kb/s. >> Anyone have some sysadmins they can lean on to understand if that is >> realistic? >> >> The straightness of the line using a log-log axis makes it seem like >> policy rather than physics. >> <download-speed(log).png> >> >> HTH, >> cheers -ben >> >> >>

Feb. 3, 2019