May 2017 - Pharo-dev - lists.pharo.org

Calypso technology preview.

by Ben Coman

It is probably much too late to suggest this, but if Calypso is a candidate for our next browser, perhaps it could be included in Pharo 6 as a technology preview? Or maybe in a half-year point release Pharo 6.x ? cheers -ben

May 20, 2017

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

by Ben Coman

On Sat, May 20, 2017 at 2:02 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Ben Coman wrote > > What do you get installing from the Catalogue into a fresh Image and > > manually updating? > > When you say "fresh image", what do you have in mind because I got the same > error with a Pharo 6 from the CI, so it doesn't seem to be a launcher > issue. > Just that. Isolating the problem between Launcher or Pharo > Sorry if I was not clear... > > cool. cheers -ben

May 20, 2017

ReÂ : [Pharo-dev] QualityImprovements assured by tests

by Benoit St-Jean

How about a sprint? I surely am not the most qualified person to comment a class I did not create but we can all remove crap !Â EnvoyÃ© Ã partir de YahooÂ Courriel sur Android Le ven., mai 19 2017 Ã 18:26, Torsten Bergmann<astares(a)gmx.de> a Ã©critÂ : Hi, One year later we are close to a final release for Pharo 6 and either with Pharo 6 or upcoming Pharo 7 I would really like to see some checks that ensure a quality image and tests who keep us all more disciplined in the future. Because: Â 1. We should not have undocumented classes: Â Â Â Â (Object allSubclasses select: [:cls| cls hasComment not ]) Â Â but we have a lot in Pharo 6 now since we introduced new packages in this release iteration Â 2. We should not have class instance variables in uppercase but: Â Â (Object allSubclasses select: [:cls| cls isMeta]) select: [:cls| clsÂ Â Â Â instVarNames anySatisfy: [:n | n first isUppercase]] Â Â is not empty - although this was already discussed back in 2008 (!), see Â Â http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2008-November/00… Â 3. We should not have uncategorized methods but: Â Â (Object allSubclasses select: [:cls| (cls selectorsInProtocol: Protocol unclassified) notEmpty ]) Â Â we still have them. Â 4. I've seen methods with unused temporary variables. Dont know about unused ivars or other. Â 5. add you own here ... I know this is often boring to comment or categorize - but we should do our homework as we wanted to better compared to the past. Also if the base image is not following rules how should we expect others to provide quality packages on top of it? IMHO we should raise the bar. Either in Pharo 6 or in early Pharo 7. We can fix these once and for all AND assure with unit tests that we keep the standard image on this quality level. Thx T.

May 20, 2017

QualityImprovements assured by tests

by Torsten Bergmann

Hi, One year later we are close to a final release for Pharo 6 and either with Pharo 6 or upcoming Pharo 7 I would really like to see some checks that ensure a quality image and tests who keep us all more disciplined in the future. Because: 1. We should not have undocumented classes: (Object allSubclasses select: [:cls| cls hasComment not ]) but we have a lot in Pharo 6 now since we introduced new packages in this release iteration 2. We should not have class instance variables in uppercase but: (Object allSubclasses select: [:cls| cls isMeta]) select: [:cls| cls instVarNames anySatisfy: [:n | n first isUppercase]] is not empty - although this was already discussed back in 2008 (!), see http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2008-November/00… 3. We should not have uncategorized methods but: (Object allSubclasses select: [:cls| (cls selectorsInProtocol: Protocol unclassified) notEmpty ]) we still have them. 4. I've seen methods with unused temporary variables. Dont know about unused ivars or other. 5. add you own here ... I know this is often boring to comment or categorize - but we should do our homework as we wanted to better compared to the past. Also if the base image is not following rules how should we expect others to provide quality packages on top of it? IMHO we should raise the bar. Either in Pharo 6 or in early Pharo 7. We can fix these once and for all AND assure with unit tests that we keep the standard image on this quality level. Thx T.

May 19, 2017

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

by Alistair Grant

Hi Torsten, On Fri, May 19, 2017 at 10:50:41PM +0200, Torsten Bergmann wrote: > Hi Alistair, > > cant look right now but two things: > > - there are also events in the protocol - if we could hook Pharo into them > this would solve the problem without abusing delay (because then you will > get informed when the page loading is finished) That would be great. It will be a while before I get a chance to look at this (I want to finish some proposed changes to the FileSystem packages first), but I'll try and include it then. > - you can write "5 seconds wait" in Pharo Thanks for the tip (I'm still transitioning from VW 2.5 :-)). > > Bye > T. > > > > Gesendet: Freitag, 19. Mai 2017 um 17:51 Uhr > > Von: "Alistair Grant" <akgrant0710(a)gmail.com> > > An: pharo-dev(a)lists.pharo.org > > Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo > > > > On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote: > > > Alistair Grant wrote > > > > > > > This looks really interesting, thanks for making it available. I'm on > > > > linux, so I guess it will need some porting. > > > > > > I added support for Linux and tried on Ubuntu with Chromium. Works - see screenshot > > > > Fantastic, thanks! > > > > I did have to change your script for it to work on my laptop: > > > > 1. isInDebugMode is false by default, which meant that chrome wasn't > > launched with remote debugging enabled. > > > > 2. Retrieving the remotes in GoogleChrome class>>tabPages failed because > > the browser hadn't had time to start up. I'll submit a pull request > > which adds a retry with delay. I've submitted the PR to ping the browser while it starts up, and add /opt/google/chrome/chrome as a known location. Thanks again, Alistair > > 3. I initially got a white image. This appears to be because the script > > doesn't wait for the navigation to complete before taking the > > screenshot. I just added an ugly delay, but I'm not yet sure what the best > > solution here is. > > > > > > | chrome page | > > > > chrome := GoogleChrome new > > debugOn; > > open; > > yourself. > > page := chrome tabPages first. > > page navigateTo: 'http://www.pharo.org'. > > (Delay forSeconds: 5) wait. > > page captureScreenshot scaledToSize: 200@300. > > > > > > > You need to load my OSLinux package (instead of OSOSX) from catalog. Or start > > > Chrom manually in debug mode. > > > > > > In the Pharo settings browser you can set the path to the chrome executable > > > and the debug port to use. > > > > I doubt that the chrome executable is in that many different places. > > Would you be open accepting a pull request which adds (what I assume is) > > the Ubuntu 16.04 default location? > > > > > > > Will add Windows support as well (using my OSWindows package) > > > > > > > Do you know how the DevTools protocol relates to headless chome, which > > > > will be available in Chrome 59? > > > > See https://developers.google.com/web/updates/2017/04/headless-chrome > > > > > > Dont know - just try it. > > > > > > > In particular, is it possible to dump the DOM with your package? > > > > > > I've seen that Brackets editor as well as Netbeans open Chrome to > > > display webpages when editing and refresh when typing. Wanted > > > to find out how it was done. > > > > > > I have not implemented the full protocol. Only what was needed to show > > > that it is possible and to do things like grabbing screenshots from websites > > > using Pharo. > > > > I've found a page that describes accessing the DOM, so it looks like it > > should be possible. I'll see what I can do... > > > > > There is a DOM domain that one could wrap - basically it is just > > > sending JSON around, see > > > https://chromedevtools.github.io/devtools-protocol > > > > > > With > > > > > > chrome := GoogleChrome open. > > > chrome jsProtocolJSON. > > > chrome browseProtocolJSON > > > > > > you can now even retrieve the Protocol as JSON for the specific browser. > > > With a little bit more work it should be possible to even generate > > > the wrapper classes/methods from such a protocol spec.

May 19, 2017

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

by Torsten Bergmann

Hi Alistair, cant look right now but two things: - there are also events in the protocol - if we could hook Pharo into them this would solve the problem without abusing delay (because then you will get informed when the page loading is finished) - you can write "5 seconds wait" in Pharo Bye T. > Gesendet: Freitag, 19. Mai 2017 um 17:51 Uhr > Von: "Alistair Grant" <akgrant0710(a)gmail.com> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo > > On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote: > > Alistair Grant wrote > > > > > This looks really interesting, thanks for making it available. I'm on > > > linux, so I guess it will need some porting. > > > > I added support for Linux and tried on Ubuntu with Chromium. Works - see screenshot > > Fantastic, thanks! > > I did have to change your script for it to work on my laptop: > > 1. isInDebugMode is false by default, which meant that chrome wasn't > launched with remote debugging enabled. > > 2. Retrieving the remotes in GoogleChrome class>>tabPages failed because > the browser hadn't had time to start up. I'll submit a pull request > which adds a retry with delay. > > 3. I initially got a white image. This appears to be because the script > doesn't wait for the navigation to complete before taking the > screenshot. I just added an ugly delay, but I'm not yet sure what the best > solution here is. > > > | chrome page | > > chrome := GoogleChrome new > debugOn; > open; > yourself. > page := chrome tabPages first. > page navigateTo: 'http://www.pharo.org'. > (Delay forSeconds: 5) wait. > page captureScreenshot scaledToSize: 200@300. > > > > You need to load my OSLinux package (instead of OSOSX) from catalog. Or start > > Chrom manually in debug mode. > > > > In the Pharo settings browser you can set the path to the chrome executable > > and the debug port to use. > > I doubt that the chrome executable is in that many different places. > Would you be open accepting a pull request which adds (what I assume is) > the Ubuntu 16.04 default location? > > > > Will add Windows support as well (using my OSWindows package) > > > > > Do you know how the DevTools protocol relates to headless chome, which > > > will be available in Chrome 59? > > > See https://developers.google.com/web/updates/2017/04/headless-chrome > > > > Dont know - just try it. > > > > > In particular, is it possible to dump the DOM with your package? > > > > I've seen that Brackets editor as well as Netbeans open Chrome to > > display webpages when editing and refresh when typing. Wanted > > to find out how it was done. > > > > I have not implemented the full protocol. Only what was needed to show > > that it is possible and to do things like grabbing screenshots from websites > > using Pharo. > > I've found a page that describes accessing the DOM, so it looks like it > should be possible. I'll see what I can do... > > > There is a DOM domain that one could wrap - basically it is just > > sending JSON around, see > > https://chromedevtools.github.io/devtools-protocol > > > > With > > > > chrome := GoogleChrome open. > > chrome jsProtocolJSON. > > chrome browseProtocolJSON > > > > you can now even retrieve the Protocol as JSON for the specific browser. > > With a little bit more work it should be possible to even generate > > the wrapper classes/methods from such a protocol spec. > > Thanks again, > Alistair > > > >

May 19, 2017

Epicea and #name in #behaviorAffectedName

by Torsten Bergmann

Hi, in latest Pharo 6 image 60494 I run into some trouble today where the deprecation warning dialog popped up and repeated itself unstoppable due to Epicea. It is hard to reproduce but what I found out was that I had a class modification (represented by EpClassModification) which run into a state where "newClass" was nil and therefore in EpClassModification>>#behaviorAffectedName the message #name was sent to nil. So #name was found in Object and as we all know we deprecated it now which lead to the deprecation dialog, leading to the deprecation dialog, leading to the deprecation dialog, ... Nearly all implementors of Epiceas #behaviorAffectedName send #name which is ok if there is a valid object it is sent to. I do not know if we should protect them somehow in case something goes wrong (like having nil in newClass) or if we should keep this untouched. At least I wanted to inform because I do not know if this later gets others into trouble too and losing their changes because Epicea does not record. Thanks T.

May 19, 2017

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

by Sean P. DeNigris

Ben Coman wrote > What do you get installing from the Catalogue into a fresh Image and > manually updating? When you say "fresh image", what do you have in mind because I got the same error with a Pharo 6 from the CI, so it doesn't seem to be a launcher issue. Sorry if I was not clear... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-and-Pharo-6-Errors-on-Mac-tp4947652p4947665.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 19, 2017

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

by Ben Coman

Would you be interested in trying it with BSD Licensed Chromium... https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md which could be packaged with a Pharo distribution. cheers -ben P.S. on the idea of an in-Image browser, this looks interesting... https://en.wikipedia.org/wiki/Chromium_Embedded_Framework On Fri, May 19, 2017 at 3:20 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > I played around with remote controlling Google Chrome from > Pharo using Chrome DevTools Protocol [1] (based on WebSockets). > > The video shows an example using latest Pharo 6 on Mac: > https://www.youtube.com/watch?v=9F5FrQTEJWY > > Initial Code is on GitHub [2] if someone is interested, > requires OSOSX and Zinc Websockets to be loaded. > > Have fun > T. > > [1] https://chromedevtools.github.io/devtools-protocol > [2] https://github.com/astares/Pharo-Chrome > >

May 19, 2017

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

by Ben Coman

What do you get installing from the Catalogue into a fresh Image and manually updating? cheers -ben On Fri, May 19, 2017 at 10:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > On image start, I get "PrimitiveFailed: primitive #createDirectory: in > MacStore failed" for > /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn > /T/AppTranslocation/4EF86F92-66D6-4944-8B30-FBCD96118FCC/d/ > Pharo.app/Contents/Resources/pharo-local > > When I try to Quit, I get "PrimitiveFailed: primitive #primSize: in > MultiByteFileStream failed" from `SourceFiles changesFileStream size` > > FYI I got the same results when I downloaded: > - the latest Launcher from > https://ci.inria.fr/pharo/view/Launcher/job/Launcher/ > PHARO=60,VERSION=stable,VM=vm,label=linux/lastSuccessfulBuild/artifact/ > Pharo-mac.zip > - Pharo 6 from http://files.pharo.org/platform/Pharo6.0-mac.zip > > Mac Sierra 10.12.3 > > From the Pharo 6 download: > > Image > ----- > /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn > /T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/ > Pharo6.0.app/Contents/Resources/Pharo6.0.image > Pharo6.0 > Latest update: #60494 > Unnamed > > Virtual Machine > --------------- > /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kc0000gn > /T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/ > Pharo6.0.app/Contents/MacOS/Pharo > CoInterpreter VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > Mac OS X built on May 2 2017 17:03:29 UTC Compiler: 4.2.1 Compatible Apple > LLVM 6.1.0 (clang-602.0.53) > VMMaker versionString VM: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2 > 08:52:41 2017 -0700 $ Plugins: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > CoInterpreter VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ > Launcher-and-Pharo-6-Errors-on-Mac-tp4947652.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 19, 2017