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

Re: [Pharo-project] Some visual artifacts in buttons (Watery 2 theme)

by Igor Stasenko

2009/4/19 Damien Cassou <damien.cassou(a)gmail.com>: > Please report an issue on the issue tracker. > #755 > 2009/4/19 Igor Stasenko <siguctua(a)gmail.com>: >> Hello, >> just in case if you not already seen it.. >> These artifacts (a button labels blended with background) is appear >> only, when you draggin a morph in hand. >> If you just place morph over background - no visible artifacts appear. >> >> On screenshot, the button label is blended with Pharo logo, placed on >> background. It seems like somewhere, it not sets an opacity values >> correctly for button labels, which allows you to see through the >> cached form (which used when you dragging morph in hand). >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 19, 2009

[Pharo-project] Fwd: A little font rendering speedup

by Igor Stasenko

I put this on mantis, since i'm sure this applies to squeak3.10 and Pharo both. http://bugs.squeak.org/view.php?id=7338 ---------- Forwarded message ---------- From: Igor Stasenko <siguctua(a)gmail.com> Date: 2009/4/19 Subject: A little font rendering speedup To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> This is an image-side change, which makes a primitiveDisplayString to not fail because StrikeFontSet returns nil for (font characterToGlyphMap). Since the code, which using fast primitive looks like following: Â Â Â Â self primDisplayString: aString from: startIndex to: stopIndex Â Â Â Â Â Â Â Â Â Â Â Â map: font characterToGlyphMap xTable: font xTable Â Â Â Â Â Â Â Â Â Â Â Â kern: kernDelta I thought, why one would return nil in ( font characterToGlyphMap ). Since #xTable in StrikeFontSet implemented as following: xTable Â Â Â Â "Answer an Array of the left x-coordinate of characters in glyphs." Â Â Â Â ^ (fontArray Â at: 1) xTable. i think it is safe to do similar in characterToGlyphMap , this allows the primitive to work w/o failure, because otherwise, if you look at implementation of primDisplayString: aString from: startIndex to: stopIndex map: glyphMap xTable: xTable kern: kernDelta in fallback code it does same thing again (and ignoring glyphMap at all, btw). To bench a difference, leave a couple of windows with text in world and then do: [10 timesRepeat: [World fullDrawOn: World assuredCanvas] ] timeToRun before change: Â 645 after change: Â 545 -- Best regards, Igor Stasenko AKA sig.

April 19, 2009

Re: [Pharo-project] New Pharo-dev based on 10284

by Damien Cassou

2009/4/19 Bernhard Pieber <pieber(a)acm.org>: > I am wondering by the way what the policy is regarding issues, just create > an issue, or send a mail to the list, or both. Both -- Damien Cassou http://damiencassou.seasidehosting.st

April 19, 2009

Re: [Pharo-project] New Pharo-dev based on 10284

by Damien Cassou

On Sun, Apr 19, 2009 at 1:20 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > just found an issue: > > - text selection is not working when selecting a text using keyboard > (shift-left/right arrows) > both in browser, shout workspace. It working however, if i selecting > text using mouse. Please also report that one on the tracker :-). -- Damien Cassou http://damiencassou.seasidehosting.st

April 19, 2009

Re: [Pharo-project] Some visual artifacts in buttons (Watery 2 theme)

by Damien Cassou

Please report an issue on the issue tracker. 2009/4/19 Igor Stasenko <siguctua(a)gmail.com>: > Hello, > just in case if you not already seen it.. > These artifacts (a button labels blended with background) is appear > only, when you draggin a morph in hand. > If you just place morph over background - no visible artifacts appear. > > On screenshot, the button label is blended with Pharo logo, placed on > background. It seems like somewhere, it not sets an opacity values > correctly for button labels, which allows you to see through the > cached form (which used when you dragging morph in hand). > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Cassou http://damiencassou.seasidehosting.st

April 19, 2009

Re: [Pharo-project] A little font rendering speedup

by Damien Cassou

Please report an issue on the issue tracker. 2009/4/19 Igor Stasenko <siguctua(a)gmail.com>: > This is an image-side change, which makes a primitiveDisplayString to > not fail because StrikeFontSet returns nil for (font > characterToGlyphMap). > > Since the code, which using fast primitive looks like following: > > Â Â Â Â self primDisplayString: aString from: startIndex to: stopIndex > Â Â Â Â Â Â Â Â Â Â Â Â map: font characterToGlyphMap xTable: font xTable > Â Â Â Â Â Â Â Â Â Â Â Â kern: kernDelta > > I thought, why one would return nil in ( font characterToGlyphMap ). > Since #xTable in StrikeFontSet implemented as following: > > xTable > Â Â Â Â "Answer an Array of the left x-coordinate of characters in glyphs." > > Â Â Â Â ^ (fontArray Â at: 1) xTable. > > i think it is safe to do similar in characterToGlyphMap , > this allows the primitive to work w/o failure, because otherwise, if > you look at implementation of > > primDisplayString: aString from: startIndex to: stopIndex map: > glyphMap xTable: xTable kern: kernDelta > > in fallback code it does same thing again (and ignoring glyphMap at all, btw). > > > To bench a difference, leave a couple of windows with text in world and then do: > > [10 timesRepeat: [World fullDrawOn: World assuredCanvas] ] timeToRun > > before change: > > Â 645 > > after change: > > Â 545 > > P.S. since i did this in a fresh pharo-10284-dev, where changesorter > is completely broken(do you aware of it?), i filed out this method as > .st file. > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Cassou http://damiencassou.seasidehosting.st

April 19, 2009

Re: [Pharo-project] New Pharo-dev based on 10284

by Bernhard Pieber

Hi Damien, Thanks for providing the download! I get an error under Mac OS X when I try to open the file browser. There was already an issue, so I attached a note to it. Seehttp://code.google.com/p/pharo/issues/detail?id=370 . I am wondering by the way what the policy is regarding issues, just create an issue, or send a mail to the list, or both. Cheers, Bernhard Am 19.04.2009 um 12:00 schrieb Damien Cassou: > http://pharo-project.org/download > > OmniBrowser is in an experimental state. If you run into more troubles > than with the previous versions, please tell me. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 19, 2009

Re: [Pharo-project] SqueakMap Package Loader?

by Adrian Lienhard

On Apr 18, 2009, at 20:18 , Markus Fritsche wrote: > I just tried to start a SM Package loader which issued a dnu. Is it > my image > or is ImageSegment broken? > > Is SM deprecated? It seems so in the official squeak distribution... Our plan is to remove SM from Pharo core and treat it as an external package (IIRC Keith already provided means to load it). Adrian

April 19, 2009

[Pharo-project] A little font rendering speedup

by Igor Stasenko

This is an image-side change, which makes a primitiveDisplayString to not fail because StrikeFontSet returns nil for (font characterToGlyphMap). Since the code, which using fast primitive looks like following: self primDisplayString: aString from: startIndex to: stopIndex map: font characterToGlyphMap xTable: font xTable kern: kernDelta I thought, why one would return nil in ( font characterToGlyphMap ). Since #xTable in StrikeFontSet implemented as following: xTable "Answer an Array of the left x-coordinate of characters in glyphs." ^ (fontArray at: 1) xTable. i think it is safe to do similar in characterToGlyphMap , this allows the primitive to work w/o failure, because otherwise, if you look at implementation of primDisplayString: aString from: startIndex to: stopIndex map: glyphMap xTable: xTable kern: kernDelta in fallback code it does same thing again (and ignoring glyphMap at all, btw). To bench a difference, leave a couple of windows with text in world and then do: [10 timesRepeat: [World fullDrawOn: World assuredCanvas] ] timeToRun before change: 645 after change: 545 P.S. since i did this in a fresh pharo-10284-dev, where changesorter is completely broken(do you aware of it?), i filed out this method as .st file. -- Best regards, Igor Stasenko AKA sig.

April 19, 2009

Re: [Pharo-project] New Pharo-dev based on 10284

by Francois Stephany

Damien Cassou wrote: > http://pharo-project.org/download > > OmniBrowser is in an experimental state. If you run into more troubles > than with the previous versions, please tell me. > Thanks Damien! I was wondering for the future official releases, what will be the version naming scheme? The Pharo-core will have discrete version number as 1.0, 1.0.1, 1.1? or more something like 1.0-update10742, 1.4-update12837 ? Will the main Pharo (so Pharo-dev) will follow the same naming scheme? Or will you generate Pharo images every month as you are doing now? From a marketing point of view, it seems that Pharo discrete versions with 'conventional' naming scheme could be easier to sell and maybe easier for users to report bugs. Sorry if that was discussed in a previous thread :/ Francois

April 19, 2009