June 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12024 (new version)

by StÃ©phane Ducasse

12024 ----- - Issue 2105: Packages remodularization and now without obsolete classes Stef (thanks Pavel)

June 30, 2010

Re: [Pharo-project] Strange behavior (bug) of wrapping text with TTFont (russian text) in TextMorph

by Nicolas Cellier

Hi Denis, My understanding of endOfRun is that the end of a run has been reached. An end of run mark a change of emphasis (think of Text string:runs:) or the end of the text to be rendered. stops endOfRun always return #endOfRun (the method to be executed when an endOfRun condition occurs is programmable, but a single usage is done across the image). You'll see that most CharacterScanner & subclasses will send a #setStopConditions, that will send a #setFont. That is the main purpose, when a change of emphasis (like bold or italic) occurs, font must be changed. The code is like this for ages (already in st80 ASCII times). Multilingual additions do also consider a change of leadingChar as a special case of endOfRun because current font must be changed too. Also, presumably it did not hurt to split text here because a change of leadingChar corresponds to a change of language. I don't think we changed this behaviour. We just used a message ^(stops endOfRun) instead of (stops at: EndOfRun), because previous implementation (along with CrossedX) did consume two character slots (256 257) which are valid Unicode (they were previously unused in ASCII times and previous Multilingual implementation because unicode leadingChar was 255). However, what changed is that less endOfRun are detected than before because Unicode leadingChar is now zero... I unfortunately don't eat my own dog food because I'm a native latin speaker, so maybe I just should stop touching the Multilingual code... But my understanding is that code needed (and still need!) to be cleaned up... ... and also that leadingChar is not really usefull for rendering Russian now that there are more and more fonts with good Unicode support... Would it be possible to change russian environment to use Unicode with a good font support? Nicolas 2010/6/30 Denis Kudriashov <dionisiydk(a)gmail.com>: > I found solution. > > I comment line of code in scanning loop in > MultiCharacterScanner>>scanMultiCharactersFrom: startIndex to: stopIndex in: > sourceString rightX: rightX stopConditions: stops kern: kernDelta > > ... > Â Â Â Â Â Â "encoding ~= startEncoding ifTrue: [lastIndex := lastIndex - 1. ^ > stops endOfRun]." > ... > > Without this commenting scanning process not register breakage at space when > scanning russian text. (because encoding is differ from startEncoding. > Encoding for space is 0 but for startEncoding is leadingChar of not ascii > russian text). > > I dont now meaning of this code line. But now I have correct wrapping > behavior. > > I know that multilingual package have many newly versions. All containes > that strange code line. > > I open Issue http://code.google.com/p/pharo/issues/detail?id=2608 > > 30 Ð¸ÑÐ½Ñ 2010 Ð³. 9:55:37 UTC+4 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ dionisiydk <dionisiydk(a)gmail.com> > Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >> >> No. #isSeparator message not used for wrapping. Wrapping logic implemented >> in MultiCompositionScanner and dont use #isSeparator >> >> 2010/6/30 Igor Stasenko <siguctua(a)gmail.com> >>> >>> 2010/6/30 Denis Kudriashov <dionisiydk(a)gmail.com>: >>> > I use Pharo 1.1 rc2 10.06 >>> > >>> > I found strange behavior of wrapping text with TTFont (russian text) in >>> > TextMorph. >>> > >>> > I dont know how to reproduce it. But I see it in my application. >>> > >>> > I have prototype button with TextMorph as it label. And I do many of: >>> > >>> > aPanel add: prototype veryDeepCopy contentsWrapped: someRussianText. >>> > >>> > And I see that text on label dont wrapped by words. It is wrapped only >>> > by >>> > label bounds. And words in text became break. >>> > Example. I expect >>> > >>> i think it wraps text based on #isSeparator test. >>> And any russian (as well as any other non-ascii characters), afaik is >>> treated as separators. >>> That's why it wraps on any letter. >>> >>> > "one two >>> > three" >>> > >>> > But I see >>> > >>> > "one two th >>> > ree >>> > " >>> > >>> > Its work correct for english text. But for russian not. >>> > >>> > And I cant reproduce it by execution code separetelly from my >>> > application >>> > (aPanel add: prototype veryDeepCopy contentsWrapped: someRussianText). >>> > >>> > I try many experiments with debuger and inspector. But I cant fix that. >>> > Wrapping text code is not simple. >>> > Maybe somebody tell me what place I need learn/inspect for fixing this >>> > bug? >>> > >>> > And I found that If I insert char by keyboard at the end of word "two" >>> > (see >>> > example) text wrapped correctly: >>> > "one twoNEW >>> > three >>> > " >>> > >>> > And this behavior correct in Pharo 1.0. >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > 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. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024

by StÃ©phane Ducasse

but in a 12025 I do not have the class anymore so I will redo 12024 I hope I do not miss a part. Stef On Jun 30, 2010, at 9:02 PM, Pavel Krivanek wrote: > You must do both parts. > > -- Pavel > > On Wed, Jun 30, 2010 at 8:58 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> if I build on 12024 I would not need to do the following? >> >> BreakPoint category: 'System-BreakPoints'. >>>>> BreakpointManager category: 'System-BreakPoints'. >>>>> MczInstaller category: 'System-Installers'. >>>>> SARInstaller category: 'System-Installers' >>>>> >>>>> ScriptLoader new addPackage: 'System-Installers'. >>>>> ScriptLoader new addPackage: 'System-BreakPoints'. >> >> if I do? >> >>> DecompilerTests compileAll. >>> LanguageEnvironment compileAll. >>> FileServices cleanUp. >>> CodeHolder compileAll. >>> CompiledMethod compileAll. >>> Debugger compileAll. >>> Object compileAll. >>> MCMczInstallerTest compileAll. >>> MCInitializationTest compileAll. >>> >> >> sorry to ask instead of trying to understand but it takes some times so I prefer to know in advance >>>>>>>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024

by StÃ©phane Ducasse

Ok I will the last one in 12026 On Jun 30, 2010, at 9:02 PM, Pavel Krivanek wrote: > You must do both parts. > > -- Pavel > > On Wed, Jun 30, 2010 at 8:58 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> if I build on 12024 I would not need to do the following? >> >> BreakPoint category: 'System-BreakPoints'. >>>>> BreakpointManager category: 'System-BreakPoints'. >>>>> MczInstaller category: 'System-Installers'. >>>>> SARInstaller category: 'System-Installers' >>>>> >>>>> ScriptLoader new addPackage: 'System-Installers'. >>>>> ScriptLoader new addPackage: 'System-BreakPoints'. >> >> if I do? >> >>> DecompilerTests compileAll. >>> LanguageEnvironment compileAll. >>> FileServices cleanUp. >>> CodeHolder compileAll. >>> CompiledMethod compileAll. >>> Debugger compileAll. >>> Object compileAll. >>> MCMczInstallerTest compileAll. >>> MCInitializationTest compileAll. >>> >> >> sorry to ask instead of trying to understand but it takes some times so I prefer to know in advance >>>>>>>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 30, 2010

[Pharo-project] [update 1.2] #12025

by StÃ©phane Ducasse

12025 ----- - Issue 2105: Packages remodularization - Post actions Pavel I just did the DecompilerTests compileAll. LanguageEnvironment compileAll. FileServices cleanUp. CodeHolder compileAll. CompiledMethod compileAll. Debugger compileAll. Object compileAll. MCMczInstallerTest compileAll. MCInitializationTest compileAll.

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024

by Pavel Krivanek

You must do both parts. -- Pavel On Wed, Jun 30, 2010 at 8:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > if I build on 12024 I would not need to do the following? > > Â Â Â Â BreakPoint category: 'System-BreakPoints'. >>>> BreakpointManager category: 'System-BreakPoints'. >>>> MczInstaller category: 'System-Installers'. >>>> SARInstaller category: 'System-Installers' >>>> >>>> ScriptLoader new addPackage: 'System-Installers'. >>>> ScriptLoader new addPackage: 'System-BreakPoints'. > > if I do? > >> DecompilerTests compileAll. >> LanguageEnvironment compileAll. >> FileServices cleanUp. >> CodeHolder compileAll. >> CompiledMethod compileAll. >> Debugger compileAll. >> Object compileAll. >> MCMczInstallerTest compileAll. >> MCInitializationTest compileAll. >> > > sorry to ask instead of trying to understand but it takes some times so I prefer to know in advance >>>>>>> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024

by StÃ©phane Ducasse

if I build on 12024 I would not need to do the following? BreakPoint category: 'System-BreakPoints'. >>> BreakpointManager category: 'System-BreakPoints'. >>> MczInstaller category: 'System-Installers'. >>> SARInstaller category: 'System-Installers' >>> >>> ScriptLoader new addPackage: 'System-Installers'. >>> ScriptLoader new addPackage: 'System-BreakPoints'. if I do? > DecompilerTests compileAll. > LanguageEnvironment compileAll. > FileServices cleanUp. > CodeHolder compileAll. > CompiledMethod compileAll. > Debugger compileAll. > Object compileAll. > MCMczInstallerTest compileAll. > MCInitializationTest compileAll. > sorry to ask instead of trying to understand but it takes some times so I prefer to know in advance >>>>>>

June 30, 2010

Re: [Pharo-project] ESUG will sponsor the XMLRPC project!

by StÃ©phane Ducasse

Philippe this is good that you reacted. The point of esug is to support actions that will help people so probably XML-RCP is not a really good choice. Now what would be good is to have a map of current techno and their support for smalltalk. Then act to fill up the gaps. Stef > > It doesn't strike me as a forward looking investment. IMHO XML-RCP is > something that will only get used less in the future, not more. The > value you get from an XML-RCP implementation will become less and less > as fewer services support it. > > But then again ESUG is free to spend their money on what they seem fit. > If they disagree or decide the current use is big enough, I have no > problem at all with this. > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024

by StÃ©phane Ducasse

Ok I will redo it Stef On Jun 30, 2010, at 8:27 PM, Pavel Krivanek wrote: > It will be better to modify the update 12024 directly. Reloading of > the packages will not remove the obsolete classes. > > -- Pavel > > On Wed, Jun 30, 2010 at 8:00 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> In the image 12023 do: >> >> BreakPoint category: 'System-BreakPoints'. >> BreakpointManager category: 'System-BreakPoints'. >> MczInstaller category: 'System-Installers'. >> SARInstaller category: 'System-Installers' >> >> ScriptLoader new addPackage: 'System-Installers'. >> ScriptLoader new addPackage: 'System-BreakPoints'. >> >> Upload this new packages to the repository and add them to the next update. >> >> -- Pavel >> >> On Wed, Jun 30, 2010 at 7:55 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> do you have a fix? >>> >>> Stef >>> >>> On Jun 30, 2010, at 7:49 PM, Pavel Krivanek wrote: >>> >>>> Great! >>>> >>>> there are two issues: there's no new package System-BreakPoints (my >>>> fault) and System-Installers. >>>> >>>> SystemNavigation default obsoleteClasses -> an >>>> Array(AnObsoleteSARInstaller AnObsoleteBreakPoint >>>> AnObsoleteBreakpointManager AnObsoleteMczInstaller) >>>> >>>> The empty system and method categories should be removed. >>>> >>>> -- Pavel >>>> >>>> On Wed, Jun 30, 2010 at 7:09 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> Pavel can you have a look to see if everything is ok? >>>>> >>>>> 12024 >>>>> ----- >>>>> >>>>> - Issue 2105: Packages remodularization >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024

by Pavel Krivanek

This code removes the obsolete classes in case you will not recreate the update 12024: DecompilerTests compileAll. LanguageEnvironment compileAll. FileServices cleanUp. CodeHolder compileAll. CompiledMethod compileAll. Debugger compileAll. Object compileAll. MCMczInstallerTest compileAll. MCInitializationTest compileAll. -- Pavel On Wed, Jun 30, 2010 at 8:27 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > It will be better to modify the update 12024 directly. Reloading of > the packages will not remove the obsolete classes. > > -- Pavel > > On Wed, Jun 30, 2010 at 8:00 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> In the image 12023 do: >> >> BreakPoint category: 'System-BreakPoints'. >> BreakpointManager category: 'System-BreakPoints'. >> MczInstaller category: 'System-Installers'. >> SARInstaller category: 'System-Installers' >> >> ScriptLoader new addPackage: 'System-Installers'. >> ScriptLoader new addPackage: 'System-BreakPoints'. >> >> Upload this new packages to the repository and add them to the next update. >> >> -- Pavel >> >> On Wed, Jun 30, 2010 at 7:55 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> do you have a fix? >>> >>> Stef >>> >>> On Jun 30, 2010, at 7:49 PM, Pavel Krivanek wrote: >>> >>>> Great! >>>> >>>> there are two issues: there's no new package System-BreakPoints (my >>>> fault) and System-Installers. >>>> >>>> SystemNavigation default obsoleteClasses -> an >>>> Array(AnObsoleteSARInstaller AnObsoleteBreakPoint >>>> AnObsoleteBreakpointManager AnObsoleteMczInstaller) >>>> >>>> The empty system and method categories should be removed. >>>> >>>> -- Pavel >>>> >>>> On Wed, Jun 30, 2010 at 7:09 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> Pavel can you have a look to see if everything is ok? >>>>> >>>>> 12024 >>>>> ----- >>>>> >>>>> - Issue 2105: Â Packages remodularization >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >

June 30, 2010