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

Re: [Pharo-dev] Running without sources/changes ?

by Marcus Denker

> On 03 Nov 2015, at 17:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > Does anyone know if we can still run Pharo (4) without sources and without changes ? Years ago there used to be an option to 'abandon changes' and/or 'abandon sources', IIRC. Can we still do that ? I can't find this option in System Settings. I want to run just a reduced image on a server. > No, in Pharo4 it does not workâ¦ we should have a look again, if we have the time. What is clear is that we really need to find a better solution to .changes/.sourcesâ¦ Marcus

Nov. 4, 2015

Re: [Pharo-dev] Measuring width string

by Aliaksei Syrel

However, Helvetica Neue on mac has kerning. Will check Cheers, Alex On Wed, Nov 4, 2015 at 1:59 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > StandardFonts defaultFont > > > "a LogicalFont > familyName: Source Sans Pro > emphasis: nil > pointSize: 10 > realFont: FreeTypeFont('Source Sans Pro' 'Regular' 10) weight: 400 > stretch: 5 slant: 0" > > StandardFonts defaultFont realFont > > > "FreeTypeFont('Source Sans Pro' 'Regular' 10)" > > StandardFonts defaultFont realFont face hasKerning > > > "false" > > Free type source sans pro in Pharo just *does not* support kerning. > >

Nov. 4, 2015

Re: [Pharo-dev] Measuring width string

by Aliaksei Syrel

> > StandardFonts defaultFont "a LogicalFont familyName: Source Sans Pro emphasis: nil pointSize: 10 realFont: FreeTypeFont('Source Sans Pro' 'Regular' 10) weight: 400 stretch: 5 slant: 0" StandardFonts defaultFont realFont "FreeTypeFont('Source Sans Pro' 'Regular' 10)" StandardFonts defaultFont realFont face hasKerning "false" Free type source sans pro in Pharo just *does not* support kerning.

Nov. 4, 2015

Re: [Pharo-dev] Measuring width string

by Stephan Eggermont

Nice. So trying with #Ta and #ffl I noticed that there is no kerning (at least not correct) but there are ligatures. Stephan

Nov. 4, 2015

Re: [Pharo-dev] Measuring width string

by Thierry Goubier

2015-11-04 8:34 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 04 Nov 2015, at 01:15, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > Yes, this is an important insight, > > I've made a visual comparison of #4 (red) compared to #1 (blue) > > <dimensions.png> > > âhttp://ws.stfx.eu/LWMJN1SY7VXT > > Peter, this script is soo cool, really great work ! > > I like the 'whatever' :) Thierry > > plus compared to the other ones it can even tell the height... now to > teach Roassal how to use it... > > > > Peter > > > > On Tue, Oct 27, 2015 at 4:11 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > > Hi Alex, > > > > thanks, this is very usefull. Can you tell which one of these measures > is the closest to the effective length of a string morph? Number 4? > > > > Thierry > > > > > > 2015-10-27 12:02 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > > Hi > > > > I'm sending it here so that it doesn't get lost. > > > > There are multiple ways to measure string width. In the following > examples performance will be tested measuring 10`000 times the width of the > following string: > > > > string := 'abcdefghijklmnopqrstuvwxyz 0123456789!@#$%^&*()_+'. > > > > 1) The most straightforward way is to send #widthOfString: to the font. > Time to run gives around 250ms. > > http://ws.stfx.eu/2Q5YA9DFTRDR > > Resulting value is rounded to integer and seems to be not absolutely > correct and precise. > > > > 2) More complex way is to go deeper on the level of glyphs and manually > summarise the width of each character in the string sending #getGlyphWidth: > character to the font. Time to run gives around 750ms. > > http://ws.stfx.eu/ETBEW1EHAAZ8 > > Resulting value is float and looks like correct and precise value. > > > > 3) Even more complex is to use CairoFontMetricsProvider instead of > font's methods. The same as in 2nd case we measure each character. Time to > run around 350ms. > > http://ws.stfx.eu/7I89DMD0ZLM3 > > Resulting value is exactly the same as in the 2nd case. With almost > equal performance to 1st it is nice alternative. > > > > 4) One more way is to let native cairo to calculate everything for us. > Calls happen through nativeboost. Time to run around 120ms. > > http://ws.stfx.eu/HYD76OMIOM7L > > As result it returns CairoTextExtents which allows to calculate width > and height with one call. > > > > Cheers, > > Alex > > > > > > >

Nov. 4, 2015

Re: [Pharo-dev] Measuring width string

by Sven Van Caekenberghe

> On 04 Nov 2015, at 01:15, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Yes, this is an important insight, > I've made a visual comparison of #4 (red) compared to #1 (blue) > <dimensions.png> > âhttp://ws.stfx.eu/LWMJN1SY7VXT Peter, this script is soo cool, really great work ! > plus compared to the other ones it can even tell the height... now to teach Roassal how to use it... > > Peter > > On Tue, Oct 27, 2015 at 4:11 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Alex, > > thanks, this is very usefull. Can you tell which one of these measures is the closest to the effective length of a string morph? Number 4? > > Thierry > > > 2015-10-27 12:02 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Hi > > I'm sending it here so that it doesn't get lost. > > There are multiple ways to measure string width. In the following examples performance will be tested measuring 10`000 times the width of the following string: > > string := 'abcdefghijklmnopqrstuvwxyz 0123456789!@#$%^&*()_+'. > > 1) The most straightforward way is to send #widthOfString: to the font. Time to run gives around 250ms. > http://ws.stfx.eu/2Q5YA9DFTRDR > Resulting value is rounded to integer and seems to be not absolutely correct and precise. > > 2) More complex way is to go deeper on the level of glyphs and manually summarise the width of each character in the string sending #getGlyphWidth: character to the font. Time to run gives around 750ms. > http://ws.stfx.eu/ETBEW1EHAAZ8 > Resulting value is float and looks like correct and precise value. > > 3) Even more complex is to use CairoFontMetricsProvider instead of font's methods. The same as in 2nd case we measure each character. Time to run around 350ms. > http://ws.stfx.eu/7I89DMD0ZLM3 > Resulting value is exactly the same as in the 2nd case. With almost equal performance to 1st it is nice alternative. > > 4) One more way is to let native cairo to calculate everything for us. Calls happen through nativeboost. Time to run around 120ms. > http://ws.stfx.eu/HYD76OMIOM7L > As result it returns CairoTextExtents which allows to calculate width and height with one call. > > Cheers, > Alex > >

Nov. 4, 2015

Re: [Pharo-dev] Running without sources/changes ?

by Max Leske

I tried that recently in a Pharo 1.3 image. âabandon sourcesâ et al donât work. What does work however is Smalltalk closeSourceFiles; openSourceFiles. I use it to speed up some stuff we do (prevents a lot of IO operations). I havenât tried it in newer versions though. Cheers, Max > On 03 Nov 2015, at 21:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > Does anyone know if we can still run Pharo (4) without sources and without changes ? Years ago there used to be an option to 'abandon changes' and/or 'abandon sources', IIRC. Can we still do that ? I can't find this option in System Settings. I want to run just a reduced image on a server. > > Sven > >

Nov. 4, 2015

Looking for a simple lecture on reflection in Smalltalk

by stepharo

Hi guys for the mooc I would like to give a simple lecture on reflection. If you have any pointers I'm interested in knowing them. Stef

Nov. 4, 2015

Re: [Pharo-dev] Measuring width string

by Peter UhnÃ¡k

Yes, this is an important insight, I've made a visual comparison of #4 (red) compared to #1 (blue) âhttp://ws.stfx.eu/LWMJN1SY7VXT plus compared to the other ones it can even tell the height... now to teach Roassal how to use it... Peter On Tue, Oct 27, 2015 at 4:11 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Alex, > > thanks, this is very usefull. Can you tell which one of these measures is > the closest to the effective length of a string morph? Number 4? > > Thierry > > > 2015-10-27 12:02 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > >> Hi >> >> I'm sending it here so that it doesn't get lost. >> >> >> There are multiple ways to measure string width. In the following >> examples performance will be tested measuring 10`000 times the width of the >> following string: >> >> *string := 'abcdefghijklmnopqrstuvwxyz 0123456789!@#$%^&*()_+'.* >> >> 1) The most straightforward way is to send #widthOfString: to the font. >> Time to run gives around 250ms. >> http://ws.stfx.eu/2Q5YA9DFTRDR >> Resulting value is rounded to integer and seems to be not absolutely >> correct and precise. >> >> 2) More complex way is to go deeper on the level of glyphs and manually >> summarise the width of each character in the string sending >> #getGlyphWidth: character to the font. Time to run gives around 750ms. >> http://ws.stfx.eu/ETBEW1EHAAZ8 >> Resulting value is float and looks like correct and precise value. >> >> 3) Even more complex is to use CairoFontMetricsProvider instead of font's >> methods. The same as in 2nd case we measure each character. Time to run >> around 350ms. >> http://ws.stfx.eu/7I89DMD0ZLM3 >> Resulting value is exactly the same as in the 2nd case. With almost equal >> performance to 1st it is nice alternative. >> >> 4) One more way is to let native cairo to calculate everything for us. >> Calls happen through nativeboost. Time to run around 120ms. >> http://ws.stfx.eu/HYD76OMIOM7L <http://ws.stfx.eu/HYD76OMIOM7L> >> As result it returns *CairoTextExtents* which allows to calculate width >> and height with one call. >> >> Cheers, >> Alex >> > >

Nov. 4, 2015

Re: [Pharo-dev] 16921 ConfigurationOfZincHTTPComponents cannot load Websockets tests

by Stephan Eggermont

On 03-11-15 20:15, Sven Van Caekenberghe wrote: > Stephan, > >> On 03 Nov 2015, at 13:58, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> I cannot write to the repo >> >> Stephan > > Your previous email is still open on my todo list, but a fix is even better. > > Yes I made a typo in the Zinc-WebSocket-Tests version. > > You should be able to write to > > http://smalltalkhub.com/mc/SvenVanCaekenberghe/ZincHTTPComponents/main/ Done Name: ConfigurationOfZincHTTPComponents-StephanEggermont.94 Author: StephanEggermont Time: 3 November 2015, 11:23:00.028743 pm UUID: 62ba6ba0-cf6d-494b-bdd3-656266397a13 Ancestors: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.93 typo fix for websockets tests Stephan

Nov. 3, 2015