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

Re: [Pharo-project] TextEditor>>possiblyChanged broke TextEditor quite well :(

by StÃ©phane Ducasse

good news. So I will do it. On Aug 18, 2010, at 1:11 PM, Fernando olivero wrote: > This method is used when installing an new editor on a TextMorph, and resusing the state of the previous one ( for example: selection interval). > > Currently we are just creating a new one, so YES, we could remove all senders. > > Fernando. > > On Aug 17, 2010, at 11:25 PM, StÃ©phane Ducasse wrote: > >> >>> >>> From: stephane ducasse <stephane.ducasse(a)gmail.com> >>> Date: August 17, 2010 10:46:05 PM GMT+02:00 >>> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> >>> Subject: TextEditor>>possiblyChanged broke TextEditor quite well :( >>> >>> >>> Hi fernando >>> >>> apparently in TextEditor>>stateArrayPut: stateArray there is call to possiblyChanged which does not exist in pharo or Squeak >>> >>> TextEditor>>stateArrayPut: stateArray >>> | sel | >>> sel := stateArray at: 1. >>> self selectFrom: sel first to: sel last. >>> beginTypeInBlock := stateArray at: 2. >>> emphasisHere := stateArray at: 3. >>> morph possiblyChanged >>> >>> And this breaks the system when I try to integrate the ParagraphEditro replacement.... lost laready a couple of hours >>> >>> In CUIS it is defined as >>> >>> >>> PluggableTextMorph>>possiblyChanged >>> "A hook for notificating possible interested parties >>> Not used in base system" >>> >>> >>> TextMorph>>possiblyChanged >>> >>> TextMorphForEditView>>possiblyChanged >>> editView possiblyChanged >>> >>> >>> So? >>> Do we need that? if not we should remove all the senders >>> Stef >>> >>> >>> >>> >>> >>> >>> >> >> <ATT00001..txt> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 18, 2010

Re: [Pharo-project] why TextMorph and PluggableTextMorph are not

by StÃ©phane Ducasse

Yes! > WEIRD! > > IMO There should be no need for PluggableTextMorph, I think the work on NewTextMorph goes into that direction, a customizable and extensible text morph, > that announces whatever happens to it. > > On Aug 17, 2010, at 9:46 PM, StÃ©phane Ducasse wrote: > >> well in the same hierarchy? >> I like because I'm so naive about how the world could be :) >> >> Stef >> >> _______________________________________________ >> 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

Aug. 18, 2010

Re: [Pharo-project] About porting and using the classificationModel in Pharo

by StÃ©phane Ducasse

On Aug 18, 2010, at 1:08 PM, Fernando olivero wrote: > Hi, is there a port to Pharo1.2 of the ClassificationModel. (http://scg.unibe.ch/archive/papers/Wuyt04aClassifications.pdf) > > If not would the Star Browser for Squeak , be a good place to start from? Yes > > http://map.squeak.org/package/9187f67b-a437-4e52-93f9-eecb9b48df78 > > > Thanks > Fernando > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 18, 2010

Re: [Pharo-project] TextEditor>>possiblyChanged broke TextEditor quite well :(

by Fernando olivero

This method is used when installing an new editor on a TextMorph, and resusing the state of the previous one ( for example: selection interval). Currently we are just creating a new one, so YES, we could remove all senders. Fernando. On Aug 17, 2010, at 11:25 PM, StÃ©phane Ducasse wrote: > >> >> From: stephane ducasse <stephane.ducasse(a)gmail.com> >> Date: August 17, 2010 10:46:05 PM GMT+02:00 >> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> >> Subject: TextEditor>>possiblyChanged broke TextEditor quite well :( >> >> >> Hi fernando >> >> apparently in TextEditor>>stateArrayPut: stateArray there is call to possiblyChanged which does not exist in pharo or Squeak >> >> TextEditor>>stateArrayPut: stateArray >> | sel | >> sel := stateArray at: 1. >> self selectFrom: sel first to: sel last. >> beginTypeInBlock := stateArray at: 2. >> emphasisHere := stateArray at: 3. >> morph possiblyChanged >> >> And this breaks the system when I try to integrate the ParagraphEditro replacement.... lost laready a couple of hours >> >> In CUIS it is defined as >> >> >> PluggableTextMorph>>possiblyChanged >> "A hook for notificating possible interested parties >> Not used in base system" >> >> >> TextMorph>>possiblyChanged >> >> TextMorphForEditView>>possiblyChanged >> editView possiblyChanged >> >> >> So? >> Do we need that? if not we should remove all the senders >> Stef >> >> >> >> >> >> >> > > <ATT00001..txt>

Aug. 18, 2010

Re: [Pharo-project] why TextMorph and PluggableTextMorph are not

by Fernando olivero

WEIRD! IMO There should be no need for PluggableTextMorph, I think the work on NewTextMorph goes into that direction, a customizable and extensible text morph, that announces whatever happens to it. On Aug 17, 2010, at 9:46 PM, StÃ©phane Ducasse wrote: > well in the same hierarchy? > I like because I'm so naive about how the world could be :) > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 18, 2010

[Pharo-project] About porting and using the classificationModel in Pharo

by Fernando olivero

Hi, is there a port to Pharo1.2 of the ClassificationModel. (http://scg.unibe.ch/archive/papers/Wuyt04aClassifications.pdf) If not would the Star Browser for Squeak , be a good place to start from? http://map.squeak.org/package/9187f67b-a437-4e52-93f9-eecb9b48df78 Thanks Fernando

Aug. 18, 2010

Re: [Pharo-project] SocketStream enh

by StÃ©phane Ducasse

>>>> I will integrate the following SocketStream tests and before I would love to see if this >>>> does not impact seaside >>>> >>>> http://code.google.com/p/pharo/issues/detail?id=2767 Does anybody have the time to give feedback on this important network changes? Stef

Aug. 18, 2010

Re: [Pharo-project] adding ISO-8859-15 and CP-1252 support

by StÃ©phane Ducasse

may be you should contact yoshiki. On Aug 18, 2010, at 9:59 AM, Philippe Marschall wrote: > On 08/17/2010 04:55 PM, Henrik Johansen wrote: >> >> On Aug 16, 2010, at 9:49 30PM, Philippe Marschall wrote: >> >>> Hi >>> >>> I decided to write ISO-8859-15 and CP-1252 support [1] (mostly for >>> selfish reasons so that Seaside on Pharo would support ISO-8859-15 and >>> CP-1252). >> >> >> More converters are always nice :D >> Their code seems ok to me. >>> >>> A couple of notes: >>> - the five unmapped bytes of CP-1252 (not ISO-8859-15, the comment is >>> wrong) are mapped to the Unicode replacement character (U+FFFD) >>> - a new Latin9 language environment is introduced >>> - some minor clean up like removing unused class variables >>> >>> I'd appreciate it if somebody knowledgeable in these areas could review >>> the changes. I'm especially unsure about the Latin9 language >>> environment, but reusing Latin1 or Unicode seemed wrong. >> >> I'm not sure its too wrong, according to EncodedCharSet comment: >> "The other confusion comes from the name of "Latin1" class. It used to mean the Latin-1 (ISO-8859-1) character set, but now it primarily means that the "Western European languages that are covered by the characters in Latin-1 character set." >> I'd reckon the same holds true for Latin1Environment (Western ), Latin2Environment (Eastern), and Latin7Environment (Greek). I don't think CP1252/8859-15 warrants the same as they are basically alternative encodings to latin1 for western languages. >> >> Also: >> - leadingChar is used in StrikeFontSet to choose different glyph sets. This allows for StrikeFonts supporting more than the default latin1 glyphs, seems to me it would be "wrong" to use the same one for two different encodings. >> Not sure why this approach was taken rather than allowing additional strike font sets based on unicode code point ranges, then using leadingChar only to differentiate when the visual glyphs for those code points would be different. I suspect it maybe was developed to deal with Han unification first, then reused to support multiple character sets later. >> >> - LanguageEnvironment seems to have been used in conjunction with translation (note the entire old translation system was removed in Pharo and replaced by an external package), maybe to decide which encoding externally stored translation files should be read in as. >> Then, having environments with overlapping supportedLanguages seem somewhat weird as well. >> Modifying defaultEncodingName/systemConverterClass of Latin1Environment to use CP1252 for some Windows systems (as per Latin2) may be another approach, may or may not lead to unintended consequences elsewhere though, I did not investigate all uses. >> >> IMHO, for someone who wasn't involved in its developemnt, the whole multilingual package could use some cleaning, more class comments, and clearer statement of responsibilities. >> >> Cheers, >> Henry >> >> TLDR; >> More converters: yay! >> More LanguageEnvironments: o_O, not sure > > OK, if nobody says it's a good idea and the right thing to do I'll drop > the LanguageEnvironment. > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 18, 2010

[Pharo-project] [update 1.2] #12098

by Marcus Denker

12098 ----- Issue 2826: add empty PluggableButtonMorphPlus Issue 2824: PluggableTextMorphWithModel is not used Issue 2333: MCSnapshotBrowser>>allClassNames would incorrectly list the classe -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 18, 2010

Re: [Pharo-project] adding ISO-8859-15 and CP-1252 support

by Philippe Marschall

On 08/17/2010 04:55 PM, Henrik Johansen wrote: > > On Aug 16, 2010, at 9:49 30PM, Philippe Marschall wrote: > >> Hi >> >> I decided to write ISO-8859-15 and CP-1252 support [1] (mostly for >> selfish reasons so that Seaside on Pharo would support ISO-8859-15 and >> CP-1252). > > > More converters are always nice :D > Their code seems ok to me. >> >> A couple of notes: >> - the five unmapped bytes of CP-1252 (not ISO-8859-15, the comment is >> wrong) are mapped to the Unicode replacement character (U+FFFD) >> - a new Latin9 language environment is introduced >> - some minor clean up like removing unused class variables >> >> I'd appreciate it if somebody knowledgeable in these areas could review >> the changes. I'm especially unsure about the Latin9 language >> environment, but reusing Latin1 or Unicode seemed wrong. > > I'm not sure its too wrong, according to EncodedCharSet comment: > "The other confusion comes from the name of "Latin1" class. It used to mean the Latin-1 (ISO-8859-1) character set, but now it primarily means that the "Western European languages that are covered by the characters in Latin-1 character set." > I'd reckon the same holds true for Latin1Environment (Western ), Latin2Environment (Eastern), and Latin7Environment (Greek). I don't think CP1252/8859-15 warrants the same as they are basically alternative encodings to latin1 for western languages. > > Also: > - leadingChar is used in StrikeFontSet to choose different glyph sets. This allows for StrikeFonts supporting more than the default latin1 glyphs, seems to me it would be "wrong" to use the same one for two different encodings. > Not sure why this approach was taken rather than allowing additional strike font sets based on unicode code point ranges, then using leadingChar only to differentiate when the visual glyphs for those code points would be different. I suspect it maybe was developed to deal with Han unification first, then reused to support multiple character sets later. > > - LanguageEnvironment seems to have been used in conjunction with translation (note the entire old translation system was removed in Pharo and replaced by an external package), maybe to decide which encoding externally stored translation files should be read in as. > Then, having environments with overlapping supportedLanguages seem somewhat weird as well. > Modifying defaultEncodingName/systemConverterClass of Latin1Environment to use CP1252 for some Windows systems (as per Latin2) may be another approach, may or may not lead to unintended consequences elsewhere though, I did not investigate all uses. > > IMHO, for someone who wasn't involved in its developemnt, the whole multilingual package could use some cleaning, more class comments, and clearer statement of responsibilities. > > Cheers, > Henry > > TLDR; > More converters: yay! > More LanguageEnvironments: o_O, not sure OK, if nobody says it's a good idea and the right thing to do I'll drop the LanguageEnvironment. Cheers Philippe

Aug. 18, 2010