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

Re: [Pharo-dev] setting fonts in pharo 3.0

by Tudor Girba

Oh, I see. The previous code relied on the assumption that the free types are not enabled: FreeTypeSystemSettings loadFt2Library: true. This implicitly triggered the fonts update. So, now I am doing: FreeTypeFontProvider current updateFromSystem. and it works just fine. Thanks. Doru On Fri, Nov 1, 2013 at 10:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 01 Nov 2013, at 21:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Hi, > > > > I am porting Moose to Pharo 3.0. I could get the image code to load > rather painlessly, and that is great. > > > > The first thing I notice is that something changed in the font > management: I cannot seem to be able to set non-bitmap fonts anymore. I > also noticed that the base Pharo image does not come with the advertised > non-bitmap fonts either. > > > > I am trying this: > > > > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBold') do: [ :each | > > Gofer new > > smalltalkhubUser: 'girba' project: 'FreeFonts'; > > package: each; > > load. > > (Smalltalk at: each asSymbol) new install ]. > > FreeTypeSystemSettings loadFt2Library: true. > > StandardFonts > > setAllStandardFontsTo: (LogicalFont familyName: 'Source > Sans Pro' pointSize: 10); > > haloFont: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 10); > > windowTitleFont: (LogicalFont familyName: 'Source Sans > Pro' pointSize: 14); > > balloonFont: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 10); > > codeFont: (LogicalFont familyName: 'Source Code Pro' > pointSize: 10) > > > > Could anyone point me in the right direction? > > This is how I customise newly downloaded 3.0 images (filing in this code): > > === > Author fullName: 'SvenVanCaekenberghe'. > > TaskbarMorph showWindowPreview: false. > > SourceCodeProRegular new install. > OpenSansRegular new install. > FreeTypeFontProvider current updateFromSystem. > > #( > #(#defaultFont: 'Open Sans' 12) > #(#listFont: 'Open Sans' 12) > #(#menuFont: 'Open Sans' 12) > #(#windowTitleFont: 'Open Sans' 12) > #(#balloonFont: 'Open Sans' 10) > #(#codeFont: 'Source Code Pro' 11) > #(#buttonFont: 'Open Sans' 12) > #(#haloFont: 'Open Sans' 10)) do: [ :spec | > | font | > font := LogicalFont familyName: spec second pointSize: > spec third. > StandardFonts perform: spec first with: font ] > === > > I did not manage to make the window title font bold though ;-) > > Sven > > > Cheers, > > Doru > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 1, 2013

how to set another inspector/explorer

by Tudor Girba

Hi, I am trying to set the GTInspector as the default explorer. However, I see that the inspector registration has changed. It seems to me that registering to #objectExplorer has no effect. Instead, we are now sending #inspect: and #explore to the #inspector: Object>>explore ^Smalltalk tools inspector explore: self I do not quite see the rationale behind the current design. Furthermore, Smalltalk tools still has an entry for #objectExplorer: (Smalltalk tools instVarNamed: #tools) at: #objectExplorer ==> ObjectExplorer Anyway, I added #inspect: and #explore: to GTInspector class, and I registered it as the #inspector. It seems fine, but the problem now is that the default Spec-based debugger relies on a #inspectorSpec method in the inspector class. This is highly problematic and I am stuck. I think we should not introduce Spec-specific requirements at such a basic level. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Nov. 1, 2013

Fuel: fix for Squeak trunk

by Nicolas Cellier

I have an easy fix for Fuel on Squeak trunk. It concerns the FuelCompatibility layer, so I hesitate to publish on Pharo fogbugz... Is there a dedicated bug tracker? What is the preferred procedure? Nicolas

Nov. 1, 2013

Re: [Pharo-dev] Proposal for a Topic for the bachelor/master list [safe-image for teaching]

by StÃ©phane Ducasse

Gisela I will add this idea to the topics list :) Thanks for the reminder. Stef On Nov 1, 2013, at 7:56 PM, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. > The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning. > > It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). > Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. > Also, some filters during debugging, to avoid "protected" code. > An easy way to obtain that image > > The idea is to reduce the common errors that we make when we start programming also to help teachers. > > >

Nov. 1, 2013

Re: [Pharo-dev] Proposal for a Topic for the bachelor/master list [safe-image for teaching]

by StÃ©phane Ducasse

Hi mariano Benjamin did a User and locking package for Pharo 20 and 30. Stef > Another similar project is a real working Image Locker for deploying... but not sure how much important it is... > > > On Fri, Nov 1, 2013 at 5:10 PM, Max Leske <maxleske(a)gmail.com> wrote: > I think thatâs a good idea. Obviously thatâs something that none of us developers want in the system but it would be good to have it from a promotional point of view I guess. Could applications like Dr. Geo benefit from such an environment? > > Max > > > On 01.11.2013, at 19:56, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > > > Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. > > The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning. > > > > It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). > > Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. > > Also, some filters during debugging, to avoid "protected" code. > > An easy way to obtain that image > > > > The idea is to reduce the common errors that we make when we start programming also to help teachers. > > > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 1, 2013

Re: [Pharo-dev] setting fonts in pharo 3.0

by Sven Van Caekenberghe

On 01 Nov 2013, at 21:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I am porting Moose to Pharo 3.0. I could get the image code to load rather painlessly, and that is great. > > The first thing I notice is that something changed in the font management: I cannot seem to be able to set non-bitmap fonts anymore. I also noticed that the base Pharo image does not come with the advertised non-bitmap fonts either. > > I am trying this: > > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > StandardFonts > setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); > balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) > > Could anyone point me in the right direction? This is how I customise newly downloaded 3.0 images (filing in this code): === Author fullName: 'SvenVanCaekenberghe'. TaskbarMorph showWindowPreview: false. SourceCodeProRegular new install. OpenSansRegular new install. FreeTypeFontProvider current updateFromSystem. #( #(#defaultFont: 'Open Sans' 12) #(#listFont: 'Open Sans' 12) #(#menuFont: 'Open Sans' 12) #(#windowTitleFont: 'Open Sans' 12) #(#balloonFont: 'Open Sans' 10) #(#codeFont: 'Source Code Pro' 11) #(#buttonFont: 'Open Sans' 12) #(#haloFont: 'Open Sans' 10)) do: [ :spec | | font | font := LogicalFont familyName: spec second pointSize: spec third. StandardFonts perform: spec first with: font ] === I did not manage to make the window title font bold though ;-) Sven > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 1, 2013

Re: [Pharo-dev] setting fonts in pharo 3.0

by Esteban Lorenzano

nothing changed, but there is a bug around that prevents the loading at startup (unless you do what Nicolas says). now, I'm on vacations and I will not have time to look at it until 18Nov+ :( Esteban On Nov 1, 2013, at 5:58 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > For me, enabling the Settings FreeType/update fonts at startup, saving then restarting the image did the trick > > > 2013/11/1 Tudor Girba <tudor(a)tudorgirba.com> > Hi, > > I am porting Moose to Pharo 3.0. I could get the image code to load rather painlessly, and that is great. > > The first thing I notice is that something changed in the font management: I cannot seem to be able to set non-bitmap fonts anymore. I also noticed that the base Pharo image does not come with the advertised non-bitmap fonts either. > > I am trying this: > > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > StandardFonts > setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); > balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) > > Could anyone point me in the right direction? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 1, 2013

Re: [Pharo-dev] Using Gutenberg

by StÃ©phane Ducasse

> > Lots of interesting material in the chapters. Artefact is of particular interest to me (creation of invoices). > > Now digesting the Pier syntax. > > Is there any Vim highlighting? I've downloaded the Wikipedia one, should be close to tweak in case there is no Vim plugin. the emacs one is working well now I do not know if there is a vim. Stef

Nov. 1, 2013

Re: [Pharo-dev] setting fonts in pharo 3.0

by Nicolas Cellier

For me, enabling the Settings FreeType/update fonts at startup, saving then restarting the image did the trick 2013/11/1 Tudor Girba <tudor(a)tudorgirba.com> > Hi, > > I am porting Moose to Pharo 3.0. I could get the image code to load rather > painlessly, and that is great. > > The first thing I notice is that something changed in the font management: > I cannot seem to be able to set non-bitmap fonts anymore. I also noticed > that the base Pharo image does not come with the advertised non-bitmap > fonts either. > > I am trying this: > > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBold') do: [ :each | > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > StandardFonts > setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 10); > haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: > 14); > balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) > > Could anyone point me in the right direction? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 1, 2013

setting fonts in pharo 3.0

by Tudor Girba

Hi, I am porting Moose to Pharo 3.0. I could get the image code to load rather painlessly, and that is great. The first thing I notice is that something changed in the font management: I cannot seem to be able to set non-bitmap fonts anymore. I also noticed that the base Pharo image does not come with the advertised non-bitmap fonts either. I am trying this: #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | Gofer new smalltalkhubUser: 'girba' project: 'FreeFonts'; package: each; load. (Smalltalk at: each asSymbol) new install ]. FreeTypeSystemSettings loadFt2Library: true. StandardFonts setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) Could anyone point me in the right direction? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Nov. 1, 2013