January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Tudor Girba

We probably need to remove that variable from PluggableShoutMorph. This variable does not exist in Pharo 1.2 12292. Cheers, Doru On 20 Jan 2011, at 09:11, laurent laffont wrote: > Other error: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/71/console > > > duplicatedVariableError: styler is already defined in PluggableTextMorph > > > Laurent > > On Thu, Jan 20, 2011 at 8:38 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Thanks Laurent and Alain for testing this. > > Cheers, > Doru > > > On 20 Jan 2011, at 08:21, Alain Plantec wrote: > > > the same here, it works. > > Now I can load Petit. > > Thanks > > Alain > > > > Le 20/01/2011 08:08, laurent laffont a Ã©crit : > >> It works ! It works ! > >> > >> Laurent > >> > >> > > > > > > > > -- > www.tudorgirba.com > > "Live like you mean it." > > > -- www.tudorgirba.com "Presenting is storytelling."

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by laurent laffont

Other error: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/71/console duplicatedVariableError: styler is already defined in PluggableTextMorph Laurent On Thu, Jan 20, 2011 at 8:38 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Thanks Laurent and Alain for testing this. > > Cheers, > Doru > > > On 20 Jan 2011, at 08:21, Alain Plantec wrote: > > > the same here, it works. > > Now I can load Petit. > > Thanks > > Alain > > > > Le 20/01/2011 08:08, laurent laffont a Ã©crit : > >> It works ! It works ! > >> > >> Laurent > >> > >> > > > > > > > > -- > www.tudorgirba.com > > "Live like you mean it." > > >

Jan. 20, 2011

Re: [Pharo-project] Issue 3554 in pharo: CP1252TextConverter new does not work

by pharo＠googlecode.com

Comment #4 on issue 3554 by ryd...(a)gmail.com: CP1252TextConverter new does not work http://code.google.com/p/pharo/issues/detail?id=3554 There's a difference, otherwise they wouldn't have different names :) http://aspell.net/charsets/codepages.html The unicode mappings are in the download links. Basically, 1252 is a latin1 superset, while 1250 is (almost) a latin2 superset. Both map visual characters to the C1 control character (16r80 - 16r9F) range in the latin sets.

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Tudor Girba

Thanks Laurent and Alain for testing this. Cheers, Doru On 20 Jan 2011, at 08:21, Alain Plantec wrote: > the same here, it works. > Now I can load Petit. > Thanks > Alain > > Le 20/01/2011 08:08, laurent laffont a Ã©crit : >> It works ! It works ! >> >> Laurent >> >> > > > -- www.tudorgirba.com "Live like you mean it."

Jan. 20, 2011

Re: [Pharo-project] About XML Support in the 1.2

by Norbert Hartl

On 19.01.2011, at 19:01, Dale Henrichs wrote: > I think that the a good working model is to store the ConfigurationOfXXX in the project repository along with the project mcz files. > > When a new version is released the configuration should be copied to MetacelloRepository for the Pharo and Squeak community. I have a GemSource MetacelloRepository where I put copies of configurations that have been ported to GemStone .... when a new version for GemStone is available. > > I would not recommend that configurations be removed from MetacelloRepository as that could break existing configurations that expect to find the configuration there. So if it is found that there are out-of-date configurations in MetacelloRepository, a new version of the configuration should be copied into MetacelloRepository. > > Now that Metacello is more established, I don't think that it is critical to require that all configurations be copied to MetacelloRepository. > > It still is useful to have a sort of clearinghouse for configurations and until a better solution comes along it serves that purpose. BTW, I think Stef has plans to provide better solutions for Pharo... > I understand what you are saying and I partially agree. But it just doesn't feel right and this is easy to show. In this example of ConfigurationOfXMLSupport there was not one caring person like you are that does everything and has on overview. There is a Configuration in MetacelloRepository than it was decided to keep the main Configuration file in XMLSupport repository. Development took place in the XMLSupport repository. In the meantime someone changed the Configuration in MetacelloRepsository probably for integration purposes. Now the Configuration has been copied from XMLSupport and has overwritten the changes that have been made to the existing Configuration. That is what you get if you branch off things. I don't know how to solve this properly because I didn't have time to follow the metacello discussions. But if there is a possibility to specify the stable for pharo 1.1.1 that doesn't change even if the packages evolves I can't see much reason to have a writable version of the Configuration in MetacelloRepository. Norbert > > > On 01/19/2011 06:12 AM, laurent laffont wrote: >> On Wed, Jan 19, 2011 at 2:49 PM, Norbert Hartl <norbert(a)hartl.name >> <mailto:norbert@hartl.name>> wrote: >> >> >> On 19.01.2011, at 14:30, laurent laffont wrote: >> >>> On Wed, Jan 19, 2011 at 1:37 PM, Norbert Hartl <norbert(a)hartl.name >>> <mailto:norbert@hartl.name>> wrote: >>> >>> It depends where you look at. ConfigurationOfXMLSupport exists >>> in MetacelloRepository as well as in XMLSupport. The latter >>> one being the official one, the former one being very >>> outdated. My sugesstion would be to remove >>> ConfigurationOfXMLSupport from MetacelloRepository to lower >>> the confusion. >>> >>> >>> Personnally I always look in MetacelloRepository, this should be >>> the reference IMHO. >>> >> Laurent, >> >> I think it is up to the maintainers where to put those files. And in >> the XMLSupport case the decision was made deliberately not to put it >> in MetacelloRepository but in XMLSupport. The only thing I want to >> avoid is having multiple different files floating around that are >> edited in an inconsistent way. >> >> >> I thought that all ConfigurationOfXXX working for Pharo should be put in >> MetacelloRepository so we have a central place to look at. >> >> But I may be wrong. Mariano ? Dale ? >> >> Laurent >> >> >> Norbert >> >>> >>> Norbert >>> >>> On 19.01.2011, at 13:18, Tudor Girba wrote: >>> >>> > The last version 1.1.6 is marked as #release. >>> > >>> > Cheers, >>> > Doru >>> > >>> > >>> > On 19 Jan 2011, at 12:26, laurent laffont wrote: >>> > >>> >> I put ConfigurationOfXMLSupport version 1.0 because >>> blessing was #release. But I agree to change. >>> >> >>> >> Laurent >>> >> >>> >> On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker >>> <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >> >>> >> On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: >>> >> >>> >>> Indeed, this is a problem for Moose in general. We depend >>> on XMLSupport, but now we cannot update it in PharoDev. I >>> would also strongly support the idea of removing XMLSupport >>> from PharoDev. >>> >>> >>> >> >>> >> What would be important: we need the latest version in >>> Pharo 1.2... else how can we ever have a version where the >>> tests are green? >>> >> (not of XML, but in general) >>> >> >>> >> Marcus >>> >> >>> >>> Cheers, >>> >>> Doru >>> >>> >>> >>> >>> >>> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: >>> >>> >>> >>>> Hi, >>> >>>> >>> >>>> I have a problem with the XMLSupport version from Pharo 1.2. >>> >>>> >>> >>>> The problem is that I need to work with one of the last >>> version of XMLSupport but in the pharo image 1.2 is loaded an >>> old version of XMLSupport (I mean a version from Jan 2010). I >>> did try to load a newer version of XMLSupport using >>> ConfigurationOfXMLSupport but some errors make this operation >>> impossible. >>> >>>> So either Pharo-dev 1.2 load a newer (possibly the last) >>> version of XMLSupport by default or Pharo-dev 1.2 should not >>> load XMLSupport at all. >>> >>>> >>> >>>> I think that doesn't make sense to use by default such an >>> old version, also considering that the last XMLSupport has >>> nice and useful features like the XMLPluggableElementFactory. >>> >>>> >>> >>>> By avoiding to load XMLSupport in Pharo-dev 1.2 by >>> default you let people free to use the version that they like. >>> >>>> >>> >>>> Thanks, >>> >>>> >>> >>>> Fabrizio >>> >>>> >>> >>> >>> >>> -- >>> >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> >>> >>> >>> "We cannot reach the flow of things unless we let go." >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >>> >> -- >>> >> Marcus Denker -- http://www.marcusdenker.de >>> <http://www.marcusdenker.de/> >>> >> INRIA Lille -- Nord Europe. Team RMoD. >>> >> >>> >> >>> >> >>> > >>> > -- >>> > www.tudorgirba.com <http://www.tudorgirba.com/> >>> > >>> > "If you interrupt the barber while he is cutting your hair, >>> > you will end up with a messy haircut." >>> > >>> > >>> >>> >>> >> >> > >

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Alain Plantec

the same here, it works. Now I can load Petit. Thanks Alain Le 20/01/2011 08:08, laurent laffont a Ã©crit : > It works ! It works ! > > Laurent > >

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by laurent laffont

One problem though: syntax highlighting is activated everywhere: text fields, dev workspace, help system .... Laurent On Thu, Jan 20, 2011 at 8:08 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > It works ! It works ! > > Laurent > > On Thu, Jan 20, 2011 at 7:51 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Can you check if with the fix it works? >> The rest is not my concern. >> I need to know to integrate them or not. >> >> Stef >> >> >> On Jan 19, 2011, at 10:55 PM, Alexandre Bergel wrote: >> >> > I got bitten by the Shout problem. >> > But ConfigurationOfMoose automatically loads Petit. Why loading it >> manually? >> > >> > Alexandre >> > >> > >> > On 19 Jan 2011, at 18:49, StÃ©phane Ducasse wrote: >> > >> >> alain >> >> mentioned that in another thread >> >> >> >> >> >> I've the same problem when I load Moose and/or Petit with the following >> scripts: >> >> >> >> Gofer new >> >> squeaksource: 'Moose'; >> >> package: 'ConfigurationOfMoose'; >> >> load. >> >> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. >> >> >> >> Gofer new >> >> renggli: 'petit'; >> >> package: 'ConfigurationOfPetitParser'; >> >> load. >> >> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. >> >> >> >> >> >> >> >> >> >> >> >> On Jan 19, 2011, at 10:43 PM, Alexandre Bergel wrote: >> >> >> >>> I do not understand. What can I do to help? >> >>> >> >>> Alexandre >> >>> >> >>> >> >>> On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: >> >>> >> >>>> Can somebody try by defining these methods >> >>>> >> >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem >> 11/25/2010 15:35'! >> >>>> stylerStyled: styledCopyOfText >> >>>> >> >>>> textMorph contents runs: styledCopyOfText runs . >> >>>> "textMorph paragraph recomposeFrom: 1 to: textMorph contents size >> delta: 0." "caused chars to appear in wrong order esp. in demo mode. >> remove this line when sure it is fixed" >> >>>> textMorph updateFromParagraph. >> >>>> selectionInterval >> >>>> ifNotNil:[ >> >>>> textMorph editor >> >>>> selectInvisiblyFrom: selectionInterval >> first to: selectionInterval last; >> >>>> storeSelectionInParagraph; >> >>>> setEmphasisHere]. >> >>>> textMorph editor blinkParen. >> >>>> self scrollSelectionIntoView >> >>>> ! ! >> >>>> >> >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem >> 11/25/2010 15:35'! >> >>>> stylerStyledInBackground: styledCopyOfText >> >>>> "It is possible that the text string has changed since the >> styling began. Disregard the styles if styledCopyOfText's string differs >> with the current textMorph contents string" >> >>>> >> >>>> textMorph contents string = styledCopyOfText string >> >>>> ifTrue: [self stylerStyled: styledCopyOfText]! ! >> >>>> >> >>>> >> >>>> >> >>>> I think that we found a bug in MC since the category where named: >> 'shout' (not with * so that the changes do not belong to the package of >> shout but really the one of PluggableTextMorph. >> >>>> >> >>>> >> >>>> On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: >> >>>> >> >>>>>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: >> >>>>> >> >>>>> >> >>>>> this is probably with a MC problem because in >> >>>>> Issue 3486: PluggableTextMorph should be able to support text >> styling >> >>>>> >> >>>>> we payed attention to have it. >> >>>>> http://code.google.com/p/pharo/issues/detail?id=3486 >> >>>>> >> >>>>> Benjamin can you have a look? >> >>>>> >> >>>>> Stef >> >>>>> >> >>>> >> >>>> >> >>> >> >>> -- >> >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >>> Alexandre Bergel http://www.bergel.eu >> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >> >> >> > >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> > >> > >> >> >> >

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by laurent laffont

It works ! It works ! Laurent On Thu, Jan 20, 2011 at 7:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Can you check if with the fix it works? > The rest is not my concern. > I need to know to integrate them or not. > > Stef > > > On Jan 19, 2011, at 10:55 PM, Alexandre Bergel wrote: > > > I got bitten by the Shout problem. > > But ConfigurationOfMoose automatically loads Petit. Why loading it > manually? > > > > Alexandre > > > > > > On 19 Jan 2011, at 18:49, StÃ©phane Ducasse wrote: > > > >> alain > >> mentioned that in another thread > >> > >> > >> I've the same problem when I load Moose and/or Petit with the following > scripts: > >> > >> Gofer new > >> squeaksource: 'Moose'; > >> package: 'ConfigurationOfMoose'; > >> load. > >> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. > >> > >> Gofer new > >> renggli: 'petit'; > >> package: 'ConfigurationOfPetitParser'; > >> load. > >> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. > >> > >> > >> > >> > >> > >> On Jan 19, 2011, at 10:43 PM, Alexandre Bergel wrote: > >> > >>> I do not understand. What can I do to help? > >>> > >>> Alexandre > >>> > >>> > >>> On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: > >>> > >>>> Can somebody try by defining these methods > >>>> > >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem > 11/25/2010 15:35'! > >>>> stylerStyled: styledCopyOfText > >>>> > >>>> textMorph contents runs: styledCopyOfText runs . > >>>> "textMorph paragraph recomposeFrom: 1 to: textMorph contents size > delta: 0." "caused chars to appear in wrong order esp. in demo mode. > remove this line when sure it is fixed" > >>>> textMorph updateFromParagraph. > >>>> selectionInterval > >>>> ifNotNil:[ > >>>> textMorph editor > >>>> selectInvisiblyFrom: selectionInterval > first to: selectionInterval last; > >>>> storeSelectionInParagraph; > >>>> setEmphasisHere]. > >>>> textMorph editor blinkParen. > >>>> self scrollSelectionIntoView > >>>> ! ! > >>>> > >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem > 11/25/2010 15:35'! > >>>> stylerStyledInBackground: styledCopyOfText > >>>> "It is possible that the text string has changed since the > styling began. Disregard the styles if styledCopyOfText's string differs > with the current textMorph contents string" > >>>> > >>>> textMorph contents string = styledCopyOfText string > >>>> ifTrue: [self stylerStyled: styledCopyOfText]! ! > >>>> > >>>> > >>>> > >>>> I think that we found a bug in MC since the category where named: > 'shout' (not with * so that the changes do not belong to the package of > shout but really the one of PluggableTextMorph. > >>>> > >>>> > >>>> On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: > >>>> > >>>>>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: > >>>>> > >>>>> > >>>>> this is probably with a MC problem because in > >>>>> Issue 3486: PluggableTextMorph should be able to support text > styling > >>>>> > >>>>> we payed attention to have it. > >>>>> http://code.google.com/p/pharo/issues/detail?id=3486 > >>>>> > >>>>> Benjamin can you have a look? > >>>>> > >>>>> Stef > >>>>> > >>>> > >>>> > >>> > >>> -- > >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>> Alexandre Bergel http://www.bergel.eu > >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > >

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by StÃ©phane Ducasse

Can you check if with the fix it works? The rest is not my concern. I need to know to integrate them or not. Stef On Jan 19, 2011, at 10:55 PM, Alexandre Bergel wrote: > I got bitten by the Shout problem. > But ConfigurationOfMoose automatically loads Petit. Why loading it manually? > > Alexandre > > > On 19 Jan 2011, at 18:49, StÃ©phane Ducasse wrote: > >> alain >> mentioned that in another thread >> >> >> I've the same problem when I load Moose and/or Petit with the following scripts: >> >> Gofer new >> squeaksource: 'Moose'; >> package: 'ConfigurationOfMoose'; >> load. >> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. >> >> Gofer new >> renggli: 'petit'; >> package: 'ConfigurationOfPetitParser'; >> load. >> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. >> >> >> >> >> >> On Jan 19, 2011, at 10:43 PM, Alexandre Bergel wrote: >> >>> I do not understand. What can I do to help? >>> >>> Alexandre >>> >>> >>> On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: >>> >>>> Can somebody try by defining these methods >>>> >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >>>> stylerStyled: styledCopyOfText >>>> >>>> textMorph contents runs: styledCopyOfText runs . >>>> "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" >>>> textMorph updateFromParagraph. >>>> selectionInterval >>>> ifNotNil:[ >>>> textMorph editor >>>> selectInvisiblyFrom: selectionInterval first to: selectionInterval last; >>>> storeSelectionInParagraph; >>>> setEmphasisHere]. >>>> textMorph editor blinkParen. >>>> self scrollSelectionIntoView >>>> ! ! >>>> >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >>>> stylerStyledInBackground: styledCopyOfText >>>> "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" >>>> >>>> textMorph contents string = styledCopyOfText string >>>> ifTrue: [self stylerStyled: styledCopyOfText]! ! >>>> >>>> >>>> >>>> I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. >>>> >>>> >>>> On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: >>>> >>>>>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: >>>>> >>>>> >>>>> this is probably with a MC problem because in >>>>> Issue 3486: PluggableTextMorph should be able to support text styling >>>>> >>>>> we payed attention to have it. >>>>> http://code.google.com/p/pharo/issues/detail?id=3486 >>>>> >>>>> Benjamin can you have a look? >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Jan. 20, 2011

Re: [Pharo-project] Issue 3554 in pharo: CP1252TextConverter new does not work

by pharo＠googlecode.com

Comment #3 on issue 3554 by stephane...(a)gmail.com: CP1252TextConverter new does not work http://code.google.com/p/pharo/issues/detail?id=3554 Thanks henrik this is what I saw. Do you know if there is a difference between Cp1250 and CP1252 because Soup used CP1252 now I made the tests work with cp1250 but the parser got problem on real code so the tests are not good enough. ;(

Jan. 20, 2011