November 2016 - Pharo-dev - lists.pharo.org

Why join the Pharo Association?

by Marcus Denker

Hi, I added a page to explain the benefits for joining the Pharo Association. Have a look: https://association.pharo.org/Benefits <https://association.pharo.org/Benefits> Marcus

Nov. 30, 2016

Re: [Pharo-dev] [Pharo-users] Pharo 5 and retina displays in 2016?

by Dimitris Chloupis

looks ok to me On Wed, Nov 30, 2016 at 12:35 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 30 Nov 2016, at 11:23, Tim Mackinnon <tim(a)testit.works> wrote: > > Adding this to the Dev user group - is there really no solution for this? > I read a few old messages from 2012 about different fonts but nothing > seemed to work from what I could see. > > Has everyone just been putting up with the fuzziness and got used to it? > > > The majority of Pharo developers are on macOS, most of them with Retina > screens. I know that we do have some problems in that area, but I > personally consider the current situation acceptable. > > This is a screenshot of my current work image (still Pharo 4) in actual > size: > > > Is this (too) fuzzy for you ? > > As a new Retina display user, I love the clarity in other apps and find it > quite jarring in Pharo. I was going to do a brown bag session on Smalltalk > with the current team Iâm working with, however as they all have retina > Macs, I think I may reconsider this as unless you love the language its > another thing for people to throw stones at. > > As Stephan mentions below, were Tobiasâ changes not viable? Is there > anything we can do to help get them safely in - or can I try it on an > experimental branch? > > Tim > > On 29 Nov 2016, at 21:02, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 29/11/16 00:34, Tim Mackinnon wrote: > > Or is this still the same issue thatâs been hanging around for a long > time as its hard to easily fix? > > > Tobias Pape wrote some vm changes that solved the problem this summer, and > they somehow interfered, so were reverted. I posted some pictures > on twitter 10/11-7 of it working with both Pharo & Squeak. > > Stephan > > > > Hi Guys - its been a while since Iâve had a chance to get back into some > coding in Smalltalk, and took the plunge again with a new laptop and Pharo > 5, however the screen is really blurry? > > Doing a google search, I can see this same question raised back in 2012, > but has there been no progress in this intervening years or has a > workaround not been documented for google to find? Or has everyone just got > used to it, and I need to hand in there... > > I have tried using a different font - but not sure what constitutes a > true-type font (are these the same as free-type mentioned in the Settings > Browser?). Has anyone found a font that makes everything look crisp (I > tried Helvetica but its only marginally better). > > Or is this still the same issue thatâs been hanging around for a long time > as its hard to easily fix? > > Tim > > > > >

Nov. 30, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Denis Kudriashov

Hi Nicolas. 2016-11-29 22:55 GMT+01:00 Nicolas Passerini <npasserini(a)gmail.com>: > 2016-11-29 13:08 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> And my problem was related to feature/issue of Iceberg to require github >> keys. > > > This is interesting for my, which operation did demand for your github > keys? > I mean, were keys need for that operation or did Iceberg ask you for keys > before they are needed? > I got error when I install dev Brick: Git error: Cloning into ''Brick''... Permission denied (publickey). fatal: Could not read from remote repository. And I found comment that it could be not required in future.

Nov. 30, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60310 Home: https://github.com/pharo-project/pharo-core

Nov. 30, 2016

[pharo-project/pharo-core] abaf74: 60310

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: abaf74c3a3e3e8206312b4ee2c17f6da5a57e3fc https://github.com/pharo-project/pharo-core/commit/abaf74c3a3e3e8206312b4ee… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-11-30 (Wed, 30 Nov 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60309.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60310.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60309.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60310.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60310 19407 FastTable default intercell spacing for glamour is too big https://pharo.fogbugz.com/f/cases/19407 19401 New method isExtension for CompiledMethod https://pharo.fogbugz.com/f/cases/19401 19408 Custom method icon for FFI methods https://pharo.fogbugz.com/f/cases/19408 http://files.pharo.org/image/60/60310.zip

Nov. 30, 2016

Re: [Pharo-dev] How to report website text bugs?

by Henrik Nergaard

SystemNavigation new allLocalCallsOn: 'No change' ofClass: ProtoObject . "a Set(Delay class>>#delaySchedulerClass:)" From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Esteban Lorenzano Sent: Wednesday, November 30, 2016 12:14 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] How to report website text bugs? On 30 Nov 2016, at 12:09, Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> wrote: On 30 Nov 2016, at 11:26, Tim Mackinnon <tim(a)testit.works<mailto:tim@testit.works>> wrote: I just tried the new example on the website (factorial is a great example from the command line - I like it). The output is: $ ./pharo Pharo.image eval "42 factorial" 'No change' 1405006117752879898543142606244511569936384000000000 $ Out of curiosity, What is the âNo Changeâ message above the answer? no idea :) obviouslyâ¦ a remaining error :P and btwâ¦ thatâs obviously a transcript message. Esteban Tim On 29 Nov 2016, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> wrote: yes, but no needâ¦ I already fixed it :) On 29 Nov 2016, at 09:29, phil(a)highoctane.be<mailto:phil@highoctane.be> wrote: Report them on pharo.fogbugz.com<http://pharo.fogbugz.com/> http://pharo.org/contribute-report-bug Use Project: Websites as the reference. Phil On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <tim(a)testit.works<mailto:tim@testit.works>> wrote: Hi Guys - how is the best way to report website and text bugs? As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can. I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed) Are you using macOS Sierra? Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder. We are working to fix this temporary inconvenience. Also - the Hello world command line example on the front page doesnât work on a standard Terminal on a Mac (you get an error: $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" -bash: !'": event not found The culprit is of course the â!â Character so a better example might be: $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" Hello WorldStdioStream: 'stdout' Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:â¦.?). I think its an impressive example, but it just doesnât quite look right? Tim

Nov. 30, 2016

Re: [Pharo-dev] How to report website text bugs?

by Esteban Lorenzano

> On 30 Nov 2016, at 12:09, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 30 Nov 2016, at 11:26, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> I just tried the new example on the website (factorial is a great example from the command line - I like it). >> >> The output is: >> >> $ ./pharo Pharo.image eval "42 factorial" >> 'No change' >> 1405006117752879898543142606244511569936384000000000 >> $ >> >> Out of curiosity, What is the âNo Changeâ message above the answer? > > no idea :) > obviouslyâ¦ a remaining error :P and btwâ¦ thatâs obviously a transcript message. > > Esteban > >> >> Tim >> >>> On 29 Nov 2016, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> yes, but no needâ¦ I already fixed it :) >>> >>>> On 29 Nov 2016, at 09:29, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >>>> >>>> Report them on pharo.fogbugz.com <http://pharo.fogbugz.com/> >>>> >>>> http://pharo.org/contribute-report-bug <http://pharo.org/contribute-report-bug> >>>> >>>> Use Project: Websites as the reference. >>>> >>>> Phil >>>> >>>> On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>> Hi Guys - how is the best way to report website and text bugs? >>>> >>>> As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can. >>>> >>>> I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed) >>>> >>>> Are you using macOS Sierra? >>>> Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder. >>>> We are working to fix this temporary inconvenience. >>>> >>>> >>>> Also - the Hello world command line example on the front page doesnât work on a standard Terminal on a Mac (you get an error: >>>> >>>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" >>>> -bash: !'": event not found >>>> >>>> The culprit is of course the â!â Character so a better example might be: >>>> >>>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" >>>> Hello WorldStdioStream: 'stdout' >>>> >>>> Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:â¦.?). I think its an impressive example, but it just doesnât quite look right? >>>> >>>> >>>> Tim >>>> >>> >> >

Nov. 30, 2016

Re: [Pharo-dev] How to report website text bugs?

by Esteban Lorenzano

> On 30 Nov 2016, at 11:26, Tim Mackinnon <tim(a)testit.works> wrote: > > I just tried the new example on the website (factorial is a great example from the command line - I like it). > > The output is: > > $ ./pharo Pharo.image eval "42 factorial" > 'No change' > 1405006117752879898543142606244511569936384000000000 > $ > > Out of curiosity, What is the âNo Changeâ message above the answer? no idea :) obviouslyâ¦ a remaining error :P Esteban > > Tim > >> On 29 Nov 2016, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> yes, but no needâ¦ I already fixed it :) >> >>> On 29 Nov 2016, at 09:29, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >>> >>> Report them on pharo.fogbugz.com <http://pharo.fogbugz.com/> >>> >>> http://pharo.org/contribute-report-bug <http://pharo.org/contribute-report-bug> >>> >>> Use Project: Websites as the reference. >>> >>> Phil >>> >>> On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> Hi Guys - how is the best way to report website and text bugs? >>> >>> As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can. >>> >>> I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed) >>> >>> Are you using macOS Sierra? >>> Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder. >>> We are working to fix this temporary inconvenience. >>> >>> >>> Also - the Hello world command line example on the front page doesnât work on a standard Terminal on a Mac (you get an error: >>> >>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" >>> -bash: !'": event not found >>> >>> The culprit is of course the â!â Character so a better example might be: >>> >>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" >>> Hello WorldStdioStream: 'stdout' >>> >>> Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:â¦.?). I think its an impressive example, but it just doesnât quite look right? >>> >>> >>> Tim >>> >> >

Nov. 30, 2016

Re: [Pharo-dev] [Pharo-users] Pharo 5 and retina displays in 2016?

by Sven Van Caekenberghe

> On 30 Nov 2016, at 11:23, Tim Mackinnon <tim(a)testit.works> wrote: > > Adding this to the Dev user group - is there really no solution for this? I read a few old messages from 2012 about different fonts but nothing seemed to work from what I could see. > > Has everyone just been putting up with the fuzziness and got used to it? The majority of Pharo developers are on macOS, most of them with Retina screens. I know that we do have some problems in that area, but I personally consider the current situation acceptable. This is a screenshot of my current work image (still Pharo 4) in actual size: Is this (too) fuzzy for you ? > As a new Retina display user, I love the clarity in other apps and find it quite jarring in Pharo. I was going to do a brown bag session on Smalltalk with the current team Iâm working with, however as they all have retina Macs, I think I may reconsider this as unless you love the language its another thing for people to throw stones at. > > As Stephan mentions below, were Tobiasâ changes not viable? Is there anything we can do to help get them safely in - or can I try it on an experimental branch? > > Tim > >> On 29 Nov 2016, at 21:02, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 29/11/16 00:34, Tim Mackinnon wrote: >>> Or is this still the same issue thatâs been hanging around for a long >>> time as its hard to easily fix? >> >> Tobias Pape wrote some vm changes that solved the problem this summer, and they somehow interfered, so were reverted. I posted some pictures >> on twitter 10/11-7 of it working with both Pharo & Squeak. >> >> Stephan >> >> >> >>> Hi Guys - its been a while since Iâve had a chance to get back into some coding in Smalltalk, and took the plunge again with a new laptop and Pharo 5, however the screen is really blurry? >>> >>> Doing a google search, I can see this same question raised back in 2012, but has there been no progress in this intervening years or has a workaround not been documented for google to find? Or has everyone just got used to it, and I need to hand in there... >>> >>> I have tried using a different font - but not sure what constitutes a true-type font (are these the same as free-type mentioned in the Settings Browser?). Has anyone found a font that makes everything look crisp (I tried Helvetica but its only marginally better). >>> >>> Or is this still the same issue thatâs been hanging around for a long time as its hard to easily fix? >>> >>> Tim > >

Nov. 30, 2016

Re: [Pharo-dev] How to report website text bugs?

by Tim Mackinnon

I just tried the new example on the website (factorial is a great example from the command line - I like it). The output is: $ ./pharo Pharo.image eval "42 factorial" 'No change' 1405006117752879898543142606244511569936384000000000 $ Out of curiosity, What is the âNo Changeâ message above the answer? Tim > On 29 Nov 2016, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, but no needâ¦ I already fixed it :) > >> On 29 Nov 2016, at 09:29, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >> >> Report them on pharo.fogbugz.com <http://pharo.fogbugz.com/> >> >> http://pharo.org/contribute-report-bug <http://pharo.org/contribute-report-bug> >> >> Use Project: Websites as the reference. >> >> Phil >> >> On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> Hi Guys - how is the best way to report website and text bugs? >> >> As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can. >> >> I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed) >> >> Are you using macOS Sierra? >> Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder. >> We are working to fix this temporary inconvenience. >> >> >> Also - the Hello world command line example on the front page doesnât work on a standard Terminal on a Mac (you get an error: >> >> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" >> -bash: !'": event not found >> >> The culprit is of course the â!â Character so a better example might be: >> >> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" >> Hello WorldStdioStream: 'stdout' >> >> Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:â¦.?). I think its an impressive example, but it just doesnât quite look right? >> >> >> Tim >> >

Nov. 30, 2016