April 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 85d0cf: 30812

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 85d0cff8ce066e410a9ace4c43640399a4be329b https://github.com/pharo-project/pharo-core/commit/85d0cff8ce066e410a9ace4c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-04-04 (Fri, 04 Apr 2014) Changed paths: A NativeBoost-Mac.package/NBMacShell.class/README.md A NativeBoost-Mac.package/NBMacShell.class/class/mac commands/open_.st A NativeBoost-Mac.package/NBMacShell.class/class/system/run_.st A NativeBoost-Mac.package/NBMacShell.class/definition.st A NativeBoost-Tests.package/NBMacSpecificTest.class/instance/tests/testSystemCall.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script465.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30812.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M ToolsTest.package/DebuggerTest.class/instance/testing/testBasic.st Log Message: ----------- 30812 13170 Hanging process after running DebuggerTest>>testBasic https://pharo.fogbugz.com/f/cases/13170 13147 NB Mac System Call Example https://pharo.fogbugz.com/f/cases/13147 http://files.pharo.org/image/30/30812.zip

April 4, 2014

[ANN] RenoirSt 1.2.0 released!

by Gabriel Cotelli

Hi, I'm announcing a new official release of RenoirSt, a DSL enabling programmatic cascading style sheet generation for Pharo. Changelog 1.2.0 - Issue #30 - Added units for frequencies, time, angles - Added additional units for relative lengths and resolutions - Issue #32 Added many font related properties and constants - Issue #37 Added some missing border and background properties (Thanks Maxi Tabacman) - Updated Tutorial Load it in your Pharo 3 image using the Configuration Browser (RenoirSt y RenoirStPlusSeaside configuratios), or visit the project page<http://gcotelli.github.io/RenoirSt/> and GitHub repository <https://github.com/gcotelli/RenoirSt> for more information on the supported and planned features, and check-out the online tutorial.<https://github.com/gcotelli/RenoirSt/blob/stable/docs/tutorial/Tutorial%20-…> I hope you find it useful. Feel free to ask any questions, suggest ideas and improvements, or report bugs<https://github.com/gcotelli/RenoirSt/issues> .

April 4, 2014

Build failed in Jenkins: Pharo-2.0 #356

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0/356/> ------------------------------------------ Started by upstream project "Pharo-2.0-Update-Step-0-GitTracker" build number 240 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on rmod-mac302.lille.inria.fr in workspace <https://ci.inria.fr/pharo/job/Pharo-2.0/ws/> Deleting project workspace... done Copied 20 artifacts from "Scripts-download" build number 2240 [Pharo-2.0] $ /bin/sh -xe /var/folders/k0/ljj6f35s7fv8sd6byqvgm9y40000gs/T/hudson2112834033210387307.sh + wget --quiet -O - http://get.pharo.org/20+vm /var/folders/k0/ljj6f35s7fv8sd6byqvgm9y40000gs/T/hudson2112834033210387307.sh: line 2: wget: command not found + bash + ./pharo Pharo.image update /var/folders/k0/ljj6f35s7fv8sd6byqvgm9y40000gs/T/hudson2112834033210387307.sh: line 4: ./pharo: No such file or directory Build step 'Execute shell' marked build as failure Archiving artifacts Description set: SSH: Current build result is [FAILURE], not going to run.

April 4, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Igor Stasenko

On 4 April 2014 11:17, J.F. Rick <self(a)je77.com> wrote: > Woohoo! Works for me. You made my day. > > yeah.. i am happy i figured it out finally :) i now making some cleanup and lill optimizations before committing the update. > In regards to determining the DPI of the display, can't we just set that > as a preference with a default value of 96? That would satisfy 98% of > cases. > it is already like that.. see TextStyle class>>#pixelsPerInch / #pixelsPerInch: > We could also add a primitive that would allow the VM to have its say > (e.g., retina display on MacOS). When that primitive fails, it would > default to the preference. > > sure.. one day we may add it. but in fact, who cares? if you think in terms of vectors, knowing screen DPI is something you largely don't need.. because DPI is thinking in terms of pixels :) As soon as you give user a way to zoom things in/out to make things convenient to him, it will no longer matter what is the absolute values like font sizes in UI design, the only thing what will matter is relative sizes between UI elements (like: here i want 2 times bigger font than here etc) Cheers, > > Jeff > > > On Fri, Apr 4, 2014 at 2:55 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> Okay, i think i got it.. >> >> Here is what happens: >> - the font size is usually specified in points, not x@y points, but >> typographical points, >> which is >> 1/72 inch >> >> >> TextStyle pointsToPixels: 14 >> >> TextStyle pointsToPixels: 14 => 18.666666666666668 >> >> pointsToPixels: points >> ^points * self pixelsPerInch / 72.0 >> >> >> but in Athens, i , stupid idiot, completely forgot about that, >> and use point size directly, to scale up font .. >> but the point is that this scaling performed in font units (EMs). >> >> so, to actually scale font correctly, i must use same TextStyle >> pointsToPixels: .. >> as Freetype package using.. >> >> there is one caveat, that if you really want to see exactly , say 16 >> points sized font on your screen, >> it is not possible without knowing the display resolution - how many >> pixels in one inch (hence >> #pixelsPerInch ). >> Unfortunately, our VMs don't give us a way to determine DPI of display.. >> and so, it is always 96 :/ >> >> pheww.... >> >> fromFreetypeFont: aFont cairoFace: face >> ..... >> >> - fontMatrix scaleBy: aFont pointSize. >> >> + fontMatrix scaleBy: (TextStyle pointsToPixels: aFont pointSize). >> >> problem solved ... (i hope) :) >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Best regards, Igor Stasenko.

April 4, 2014

Re: [Pharo-dev] Puzzled

by Camille Teruel

Fix in inbox https://pharo.fogbugz.com/f/cases/13170/ On 4 avr. 2014, at 12:46, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 4 avr. 2014, at 12:37, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> Thanks camille apparently I restarted from a clean image but may be I merged. >> Could you try loading the latest version of 12460 and let me know? > > It works, but we still need to add 'process terminate' at the end. > I open another bug entry (since it is not related to issue 12460). > >> >> On 04 Apr 2014, at 09:21, Camille Teruel <camille.teruel(a)gmail.com> wrote: >> >>> I tried on my machine in latest image and no matter how many times I run this test, this test still passes and I don't notice any slowdown nor image freeze. >>> But I see the hanging processes. >>> Adding 'process terminate' at the end works for me. >>> >>> >>> On 3 avr. 2014, at 19:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>> >>>> Hi guys >>>> >>>> I need your brain cells. >>>> >>>> When I execute the test >>>> >>>> testBasic >>>> | context process debugger printedString | >>>> context := [ 20 factorial ] asContext. >>>> >>>> process := Process >>>> forContext: context >>>> priority: Processor userInterruptPriority. >>>> >>>> debugger := Smalltalk tools debugger new >>>> process: process >>>> controller: nil >>>> context: context. >>>> debugger stack expand. >>>> >>>> self assert: debugger stack selectedIndex = 1. >>>> printedString := OpalCompiler isActive >>>> ifTrue: [ '[ 20 factorial ] in DebuggerTest>>testBasic'] >>>> ifFalse: [ '[...] in DebuggerTest>>testBasic' ]. >>>> self assert: debugger stack selectedItem printString = printedString. >>>> >>>> debugger send. >>>> debugger send. >>>> self assert: debugger code getText = (Integer>>#factorial) sourceCode. >>>> self assert: debugger stack selectedItem printString = 'SmallInteger(Integer)>>factorial'. >>>> >>>> two times my image (latest get totally unusable). >>>> I thought that may be the process should be terminated >>>> so I added >>>> >>>> process terminate >>>> >>>> But nothing changes. I tried to debug the code but not chance. >>>> I tried self halt after [ 20 factorial ] asContext. >>>> >>>> I tried to execute the beginning in a workspace and not as a test to eliminate problem. >>>> But again no chance. >>>> >>>> >>>> So did I miss something obvious? >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> >

April 4, 2014

Re: [Pharo-dev] Puzzled

by Camille Teruel

On 4 avr. 2014, at 12:37, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Thanks camille apparently I restarted from a clean image but may be I merged. > Could you try loading the latest version of 12460 and let me know? It works, but we still need to add 'process terminate' at the end. I open another bug entry (since it is not related to issue 12460). > > On 04 Apr 2014, at 09:21, Camille Teruel <camille.teruel(a)gmail.com> wrote: > >> I tried on my machine in latest image and no matter how many times I run this test, this test still passes and I don't notice any slowdown nor image freeze. >> But I see the hanging processes. >> Adding 'process terminate' at the end works for me. >> >> >> On 3 avr. 2014, at 19:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> >>> Hi guys >>> >>> I need your brain cells. >>> >>> When I execute the test >>> >>> testBasic >>> | context process debugger printedString | >>> context := [ 20 factorial ] asContext. >>> >>> process := Process >>> forContext: context >>> priority: Processor userInterruptPriority. >>> >>> debugger := Smalltalk tools debugger new >>> process: process >>> controller: nil >>> context: context. >>> debugger stack expand. >>> >>> self assert: debugger stack selectedIndex = 1. >>> printedString := OpalCompiler isActive >>> ifTrue: [ '[ 20 factorial ] in DebuggerTest>>testBasic'] >>> ifFalse: [ '[...] in DebuggerTest>>testBasic' ]. >>> self assert: debugger stack selectedItem printString = printedString. >>> >>> debugger send. >>> debugger send. >>> self assert: debugger code getText = (Integer>>#factorial) sourceCode. >>> self assert: debugger stack selectedItem printString = 'SmallInteger(Integer)>>factorial'. >>> >>> two times my image (latest get totally unusable). >>> I thought that may be the process should be terminated >>> so I added >>> >>> process terminate >>> >>> But nothing changes. I tried to debug the code but not chance. >>> I tried self halt after [ 20 factorial ] asContext. >>> >>> I tried to execute the beginning in a workspace and not as a test to eliminate problem. >>> But again no chance. >>> >>> >>> So did I miss something obvious? >>> >>> Stef >>> >>> >>> >>> >>> >> >> > >

April 4, 2014

Re: [Pharo-dev] Puzzled

by Pharo4Stef

Thanks camille apparently I restarted from a clean image but may be I merged. Could you try loading the latest version of 12460 and let me know? On 04 Apr 2014, at 09:21, Camille Teruel <camille.teruel(a)gmail.com> wrote: > I tried on my machine in latest image and no matter how many times I run this test, this test still passes and I don't notice any slowdown nor image freeze. > But I see the hanging processes. > Adding 'process terminate' at the end works for me. > > > On 3 avr. 2014, at 19:41, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> Hi guys >> >> I need your brain cells. >> >> When I execute the test >> >> testBasic >> | context process debugger printedString | >> context := [ 20 factorial ] asContext. >> >> process := Process >> forContext: context >> priority: Processor userInterruptPriority. >> >> debugger := Smalltalk tools debugger new >> process: process >> controller: nil >> context: context. >> debugger stack expand. >> >> self assert: debugger stack selectedIndex = 1. >> printedString := OpalCompiler isActive >> ifTrue: [ '[ 20 factorial ] in DebuggerTest>>testBasic'] >> ifFalse: [ '[...] in DebuggerTest>>testBasic' ]. >> self assert: debugger stack selectedItem printString = printedString. >> >> debugger send. >> debugger send. >> self assert: debugger code getText = (Integer>>#factorial) sourceCode. >> self assert: debugger stack selectedItem printString = 'SmallInteger(Integer)>>factorial'. >> >> two times my image (latest get totally unusable). >> I thought that may be the process should be terminated >> so I added >> >> process terminate >> >> But nothing changes. I tried to debug the code but not chance. >> I tried self halt after [ 20 factorial ] asContext. >> >> I tried to execute the beginning in a workspace and not as a test to eliminate problem. >> But again no chance. >> >> >> So did I miss something obvious? >> >> Stef >> >> >> >> >> > >

April 4, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by J.F. Rick

Woohoo! Works for me. You made my day. In regards to determining the DPI of the display, can't we just set that as a preference with a default value of 96? That would satisfy 98% of cases. We could also add a primitive that would allow the VM to have its say (e.g., retina display on MacOS). When that primitive fails, it would default to the preference. Cheers, Jeff On Fri, Apr 4, 2014 at 2:55 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Okay, i think i got it.. > > Here is what happens: > - the font size is usually specified in points, not x@y points, but > typographical points, > which is > 1/72 inch > > > TextStyle pointsToPixels: 14 > > TextStyle pointsToPixels: 14 => 18.666666666666668 > > pointsToPixels: points > ^points * self pixelsPerInch / 72.0 > > > but in Athens, i , stupid idiot, completely forgot about that, > and use point size directly, to scale up font .. > but the point is that this scaling performed in font units (EMs). > > so, to actually scale font correctly, i must use same TextStyle > pointsToPixels: .. > as Freetype package using.. > > there is one caveat, that if you really want to see exactly , say 16 > points sized font on your screen, > it is not possible without knowing the display resolution - how many > pixels in one inch (hence > #pixelsPerInch ). > Unfortunately, our VMs don't give us a way to determine DPI of display.. > and so, it is always 96 :/ > > pheww.... > > fromFreetypeFont: aFont cairoFace: face > ..... > > - fontMatrix scaleBy: aFont pointSize. > > + fontMatrix scaleBy: (TextStyle pointsToPixels: aFont pointSize). > > problem solved ... (i hope) :) > > -- > Best regards, > Igor Stasenko. > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

April 4, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Igor Stasenko

On 4 April 2014 08:35, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > > > I don't think there is any way for the VM to know the #pixelsPerInch of > the > > display, regardless of the display resolution. > > There is no api in the OS for that? It would be really strange that we > cannot know such information. > > There is, of course. Usually, display drivers can provide such information. But still you not always can know the physical dimensions of your display: - consider trying to measure DPI of display which actually a wall projector :) Anyways, i doesn't really matters what is DPI of the screen.. since with with vector graphics you are free at any moment to zoom in/out things to most pleasant scale. And therefore, font size in points becomes more like a relative measurement, rather than absolute (you know that font with of 20 points size will be 2 times bigger than same font with 10 points size) > > Maybe that implies that some > > calibration would be needed in the image to relate font points to the > > physical display. > > > > Dave > > > > > -- Best regards, Igor Stasenko.

April 4, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Igor Stasenko

On 4 April 2014 08:33, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Igor > > I was wondering the following: ? But TextStyle is not about strikefont? > > TextStyle contains so many different things.. > Stef > > On 04 Apr 2014, at 02:55, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > Okay, i think i got it.. > > > > Here is what happens: > > - the font size is usually specified in points, not x@y points, but > typographical points, > > which is > > 1/72 inch > > > > > > TextStyle pointsToPixels: 14 > > > > TextStyle pointsToPixels: 14 => 18.666666666666668 > > > > pointsToPixels: points > > ^points * self pixelsPerInch / 72.0 > > > > > > but in Athens, i , stupid idiot, completely forgot about that, > > and use point size directly, to scale up font .. > > but the point is that this scaling performed in font units (EMs). > > > > so, to actually scale font correctly, i must use same TextStyle > pointsToPixels: .. > > as Freetype package using.. > > > > there is one caveat, that if you really want to see exactly , say 16 > points sized font on your screen, > > it is not possible without knowing the display resolution - how many > pixels in one inch (hence > > #pixelsPerInch ). > > Unfortunately, our VMs don't give us a way to determine DPI of display.. > > and so, it is always 96 :/ > > > > pheww.... > > > > fromFreetypeFont: aFont cairoFace: face > > ..... > > > > - fontMatrix scaleBy: aFont pointSize. > > > > + fontMatrix scaleBy: (TextStyle pointsToPixels: aFont pointSize). > > > > problem solved ... (i hope) :) > > > > -- > > Best regards, > > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

April 4, 2014