July 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] testSubstrings fails in 10049

by Adrian Lienhard

It seems that #testSubstrings was introduced by http://code.google.com/p/pharo/issues/detail?id=26 . This test fails in update 10049. Why was no fix applied? Adrian

July 9, 2008

Re: [Pharo-project] UTF support in Linux

by StÃ©phane Ducasse

I think that fixing encodings is also part of mike push. I just saw these changesets and may be we should open tickets to see if we want to have a look. But encodings is a hell. Stef On Jul 9, 2008, at 11:29 AM, Serge Stinckwich wrote: > Hi Norbert, > i'm aware of the UTF infrastructure inside Squeak. > I think i see recently some messages on squeak-dev about various > problems with keyboard inputs. > I have to dig in the squeak-dev mailing list in order to find the > messages ... > > 2008/7/9 Norbert Hartl <norbert(a)hartl.name>: >> On Wed, 2008-07-09 at 10:44 +0200, Serge Stinckwich wrote: >>> UTF input (in VM and image) support in Pharo (or Squeak) is a must ! >>> >> What do you mean? There is support for UTF-8 and UTF-16 in the image. >> The image itself changed the internal character format to a modified >> Unicode (4 Bytes) Character. I assume that you don't need any >> conversion >> for UTF-32. >> >> The problem is not the support but to know what encoding the unicode >> has. If you have a Byte-Order-Mark this can be easy. Otherwise >> there is >> no way around than to transmit a character encoding along with the >> data >> or to use a convention for it. The etoys stuff seems like it can >> changes >> the input to something unicode but this is a convention that is >> manually >> adjusted. >> >> Do I understand something wrong? >> >> Norbert >>> 2008/7/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> >>>> >>>> Begin forwarded message: >>>> >>>>> From: Bert Freudenberg <bert(a)freudenbergs.de> >>>>> Date: July 9, 2008 12:20:52 AM CEDT >>>>> To: "A friendly place to get answers to even the most basic >>>>> questions >>>>> about Squeak." <beginners(a)lists.squeakfoundation.org> >>>>> Subject: Re: [Newbies] UTF support in Linux? >>>>> Reply-To: "A friendly place to get answers to even the most basic >>>>> questions about Squeak." <beginners(a)lists.squeakfoundation.org> >>>>> >>>>> >>>>> Am 08.07.2008 um 23:09 schrieb smith02243: >>>>> >>>>>> >>>>>> Hi all, >>>>>> >>>>>> In the Linux VM, when I try to input, via paste or the right alt >>>>>> combination, non-ascii characters, like 'Ã¶' or 'Ã©' for example, >>>>>> Squeak >>>>>> merely shows 'o?' or 'e?' I researched into this and >>>>>> accordingly chose a >>>>>> font that supports UTF-8 and set the locale and VM command line >>>>>> options >>>>>> appropriately: >>>>>> >>>>>> export LC_CTYPE="en_IE.UTF-8" >>>>>> locale-gen en_IE.UTF-8 >>>>>> (...which claims that locale is upto date...) >>>>>> sudo dpkg-reconfigure -plow locales >>>>>> (...which outputs en_IE.UTF-8... done among other things....) >>>>>> squeak -encoding UTF-8 -textenc UTF-8 -pathenc UTF-8 >>>>>> Squeak3.10.2-7179-basic.image >>>>>> >>>>>> Now when I try to input the aforementioned characters I >>>>>> encounter a debug >>>>>> message: "Error subscript is out of bound." >>>>>> >>>>>> However, I have set Squeak's language to Spanish and then >>>>>> German, and the >>>>>> characters display perfectly well in the menus. Although, the >>>>>> same cannot >>>>>> be >>>>>> said for the any files with non-ascii characters in the file >>>>>> dialogue. >>>>>> So, >>>>>> it seems it's an input problem. >>>>>> >>>>>> Anyone with any ideas? Thanks. >>>>> >>>>> This has only been addressed recently, and may not have found >>>>> its way into >>>>> a release yet. >>>>> >>>>> You need the very latest Squeak VM (3.10-1 at least). It >>>>> supports Unicode >>>>> keyboard events (which are passed to the image as UTF32). >>>>> >>>>> To make use of these events your image needs to be using >>>>> UTF32InputInterpreter. Evaluate >>>>> >>>>> ActiveHand keyboardInterpreter >>>>> >>>>> to see the currently used one. It can be changed by patching >>>>> Latin1Environment class>>inputInterpreterClass. >>>>> >>>>> I don't know if this is in any official release yet, or >>>>> scheduled for one. >>>>> >>>>> Some relevant change sets from the Etoys image seem to be >>>>> >>>>> http://tinlizzie.org/updates/etoys/updates/1713UnicodeInput1-yo.cs >>>>> http://tinlizzie.org/updates/etoys/updates/1714UnicodeInput2-yo.cs >>>>> http://tinlizzie.org/updates/etoys/updates/1925unixLatin1Input-yo.cs >>>>> http://tinlizzie.org/updates/etoys/updates/1935unicodeFallback-bf.cs >>>>> >>>>> - Bert - >>>>> >>>>> >>>>> _______________________________________________ >>>>> Beginners mailing list >>>>> Beginners(a)lists.squeakfoundation.org >>>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners >>>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> > > > > -- > Serge Stinckwich > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 9, 2008

Re: [Pharo-project] Keeping track of external issues

by StÃ©phane Ducasse

>>> "This issue is also tracked by Pharo: http://code.google.com/p/pharo/issues/detail?id=XY >>> " >>> >>> So this comment does not say whether we eventually integrated it or >>> not (this can be simply found out by following the link). So the >>> comment can be added already earlier in the process, which makes it >>> easier. >>> >>> Anybody has a better idea? >>> >> At the moment we track Mantis tickets that we are interested in. So >> we link to Mantis. What purpose is served by linking back from >> Mantis? > > just so that if you look at Mantis you can easily see whether this > was treated in Pharo without needing to search in our issue tracker. > Maybe its not needed, I'm not sure. I think that this is needed. I like to know in a glance that the issue is done. So I added harvested in pharo or evaluated and rejected for pharo. > So we can also go without it for now and if we see that it would be > nice to have the links, we can add them later. > >> Is there a possibility to get a listing of bugs that pharo isn't >> aware of? I have some problems understanding the intended workflow. >> I added the Mantis bug numbers to the title of each issue so we can >> easily get an overview of the mantis tickets we track. > > I think how you did it is exactly the right way. > >> However if we acknowledge on your proposal than the squeak issues >> I created aren't the right way to do. A squeak version can include >> many mantis tickets. If we like to integrate only some of them that >> leads to confusion. > > I don't think so. The link on Mantis would just be for convenience. > Say, you find an important fix on Mantis that was recently added and > you want to integrate it into Pharo. The note would then be > convenient to quickly see whether somebody else had already done this. > >> Btw. if I understand Stef correct than we shouldn't >> try to integrate all 3.10 fixes but to really analyze what pharo >> needs. > > I agree. I would focus on the important ones. Not only, the simple ones are cool too. :) We need the good ones :) after the fixes of nicolas are also some that we should look at. Stef

July 9, 2008

Re: [Pharo-project] UTF support in Linux

by Serge Stinckwich

Hi Norbert, i'm aware of the UTF infrastructure inside Squeak. I think i see recently some messages on squeak-dev about various problems with keyboard inputs. I have to dig in the squeak-dev mailing list in order to find the messages ... 2008/7/9 Norbert Hartl <norbert(a)hartl.name>: > On Wed, 2008-07-09 at 10:44 +0200, Serge Stinckwich wrote: >> UTF input (in VM and image) support in Pharo (or Squeak) is a must ! >> > What do you mean? There is support for UTF-8 and UTF-16 in the image. > The image itself changed the internal character format to a modified > Unicode (4 Bytes) Character. I assume that you don't need any conversion > for UTF-32. > > The problem is not the support but to know what encoding the unicode > has. If you have a Byte-Order-Mark this can be easy. Otherwise there is > no way around than to transmit a character encoding along with the data > or to use a convention for it. The etoys stuff seems like it can changes > the input to something unicode but this is a convention that is manually > adjusted. > > Do I understand something wrong? > > Norbert >> 2008/7/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> > >> > >> > Begin forwarded message: >> > >> >> From: Bert Freudenberg <bert(a)freudenbergs.de> >> >> Date: July 9, 2008 12:20:52 AM CEDT >> >> To: "A friendly place to get answers to even the most basic questions >> >> about Squeak." <beginners(a)lists.squeakfoundation.org> >> >> Subject: Re: [Newbies] UTF support in Linux? >> >> Reply-To: "A friendly place to get answers to even the most basic >> >> questions about Squeak." <beginners(a)lists.squeakfoundation.org> >> >> >> >> >> >> Am 08.07.2008 um 23:09 schrieb smith02243: >> >> >> >>> >> >>> Hi all, >> >>> >> >>> In the Linux VM, when I try to input, via paste or the right alt >> >>> combination, non-ascii characters, like 'Ã¶' or 'Ã©' for example, Squeak >> >>> merely shows 'o?' or 'e?' I researched into this and accordingly chose a >> >>> font that supports UTF-8 and set the locale and VM command line options >> >>> appropriately: >> >>> >> >>> export LC_CTYPE="en_IE.UTF-8" >> >>> locale-gen en_IE.UTF-8 >> >>> (...which claims that locale is upto date...) >> >>> sudo dpkg-reconfigure -plow locales >> >>> (...which outputs en_IE.UTF-8... done among other things....) >> >>> squeak -encoding UTF-8 -textenc UTF-8 -pathenc UTF-8 >> >>> Squeak3.10.2-7179-basic.image >> >>> >> >>> Now when I try to input the aforementioned characters I encounter a debug >> >>> message: "Error subscript is out of bound." >> >>> >> >>> However, I have set Squeak's language to Spanish and then German, and the >> >>> characters display perfectly well in the menus. Although, the same cannot >> >>> be >> >>> said for the any files with non-ascii characters in the file dialogue. >> >>> So, >> >>> it seems it's an input problem. >> >>> >> >>> Anyone with any ideas? Thanks. >> >> >> >> This has only been addressed recently, and may not have found its way into >> >> a release yet. >> >> >> >> You need the very latest Squeak VM (3.10-1 at least). It supports Unicode >> >> keyboard events (which are passed to the image as UTF32). >> >> >> >> To make use of these events your image needs to be using >> >> UTF32InputInterpreter. Evaluate >> >> >> >> ActiveHand keyboardInterpreter >> >> >> >> to see the currently used one. It can be changed by patching >> >> Latin1Environment class>>inputInterpreterClass. >> >> >> >> I don't know if this is in any official release yet, or scheduled for one. >> >> >> >> Some relevant change sets from the Etoys image seem to be >> >> >> >> http://tinlizzie.org/updates/etoys/updates/1713UnicodeInput1-yo.cs >> >> http://tinlizzie.org/updates/etoys/updates/1714UnicodeInput2-yo.cs >> >> http://tinlizzie.org/updates/etoys/updates/1925unixLatin1Input-yo.cs >> >> http://tinlizzie.org/updates/etoys/updates/1935unicodeFallback-bf.cs >> >> >> >> - Bert - >> >> >> >> >> >> _______________________________________________ >> >> Beginners mailing list >> >> Beginners(a)lists.squeakfoundation.org >> >> http://lists.squeakfoundation.org/mailman/listinfo/beginners >> >> >> > >> > >> > _______________________________________________ >> > 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 > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

July 9, 2008

Re: [Pharo-project] UTF support in Linux

by Norbert Hartl

On Wed, 2008-07-09 at 11:18 +0200, Norbert Hartl wrote: > On Wed, 2008-07-09 at 10:44 +0200, Serge Stinckwich wrote: > > UTF input (in VM and image) support in Pharo (or Squeak) is a must ! > > > What do you mean? There is support for UTF-8 and UTF-16 in the image. > The image itself changed the internal character format to a modified > Unicode (4 Bytes) Character. I assume that you don't need any conversion > for UTF-32. > > The problem is not the support but to know what encoding the unicode s/unicode/input/ Norbert > has. If you have a Byte-Order-Mark this can be easy. Otherwise there is > no way around than to transmit a character encoding along with the data > or to use a convention for it. The etoys stuff seems like it can changes > the input to something unicode but this is a convention that is manually > adjusted. > > Do I understand something wrong? > > Norbert > > 2008/7/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > > > > > > > > Begin forwarded message: > > > > > >> From: Bert Freudenberg <bert(a)freudenbergs.de> > > >> Date: July 9, 2008 12:20:52 AM CEDT > > >> To: "A friendly place to get answers to even the most basic questions > > >> about Squeak." <beginners(a)lists.squeakfoundation.org> > > >> Subject: Re: [Newbies] UTF support in Linux? > > >> Reply-To: "A friendly place to get answers to even the most basic > > >> questions about Squeak." <beginners(a)lists.squeakfoundation.org> > > >> > > >> > > >> Am 08.07.2008 um 23:09 schrieb smith02243: > > >> > > >>> > > >>> Hi all, > > >>> > > >>> In the Linux VM, when I try to input, via paste or the right alt > > >>> combination, non-ascii characters, like 'Ã¶' or 'Ã©' for example, Squeak > > >>> merely shows 'o?' or 'e?' I researched into this and accordingly chose a > > >>> font that supports UTF-8 and set the locale and VM command line options > > >>> appropriately: > > >>> > > >>> export LC_CTYPE="en_IE.UTF-8" > > >>> locale-gen en_IE.UTF-8 > > >>> (...which claims that locale is upto date...) > > >>> sudo dpkg-reconfigure -plow locales > > >>> (...which outputs en_IE.UTF-8... done among other things....) > > >>> squeak -encoding UTF-8 -textenc UTF-8 -pathenc UTF-8 > > >>> Squeak3.10.2-7179-basic.image > > >>> > > >>> Now when I try to input the aforementioned characters I encounter a debug > > >>> message: "Error subscript is out of bound." > > >>> > > >>> However, I have set Squeak's language to Spanish and then German, and the > > >>> characters display perfectly well in the menus. Although, the same cannot > > >>> be > > >>> said for the any files with non-ascii characters in the file dialogue. > > >>> So, > > >>> it seems it's an input problem. > > >>> > > >>> Anyone with any ideas? Thanks. > > >> > > >> This has only been addressed recently, and may not have found its way into > > >> a release yet. > > >> > > >> You need the very latest Squeak VM (3.10-1 at least). It supports Unicode > > >> keyboard events (which are passed to the image as UTF32). > > >> > > >> To make use of these events your image needs to be using > > >> UTF32InputInterpreter. Evaluate > > >> > > >> ActiveHand keyboardInterpreter > > >> > > >> to see the currently used one. It can be changed by patching > > >> Latin1Environment class>>inputInterpreterClass. > > >> > > >> I don't know if this is in any official release yet, or scheduled for one. > > >> > > >> Some relevant change sets from the Etoys image seem to be > > >> > > >> http://tinlizzie.org/updates/etoys/updates/1713UnicodeInput1-yo.cs > > >> http://tinlizzie.org/updates/etoys/updates/1714UnicodeInput2-yo.cs > > >> http://tinlizzie.org/updates/etoys/updates/1925unixLatin1Input-yo.cs > > >> http://tinlizzie.org/updates/etoys/updates/1935unicodeFallback-bf.cs > > >> > > >> - Bert - > > >> > > >> > > >> _______________________________________________ > > >> Beginners mailing list > > >> Beginners(a)lists.squeakfoundation.org > > >> http://lists.squeakfoundation.org/mailman/listinfo/beginners > > >> > > > > > > > > > _______________________________________________ > > > 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

July 9, 2008

Re: [Pharo-project] UTF support in Linux

by Norbert Hartl

On Wed, 2008-07-09 at 10:44 +0200, Serge Stinckwich wrote: > UTF input (in VM and image) support in Pharo (or Squeak) is a must ! > What do you mean? There is support for UTF-8 and UTF-16 in the image. The image itself changed the internal character format to a modified Unicode (4 Bytes) Character. I assume that you don't need any conversion for UTF-32. The problem is not the support but to know what encoding the unicode has. If you have a Byte-Order-Mark this can be easy. Otherwise there is no way around than to transmit a character encoding along with the data or to use a convention for it. The etoys stuff seems like it can changes the input to something unicode but this is a convention that is manually adjusted. Do I understand something wrong? Norbert > 2008/7/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > > > > > Begin forwarded message: > > > >> From: Bert Freudenberg <bert(a)freudenbergs.de> > >> Date: July 9, 2008 12:20:52 AM CEDT > >> To: "A friendly place to get answers to even the most basic questions > >> about Squeak." <beginners(a)lists.squeakfoundation.org> > >> Subject: Re: [Newbies] UTF support in Linux? > >> Reply-To: "A friendly place to get answers to even the most basic > >> questions about Squeak." <beginners(a)lists.squeakfoundation.org> > >> > >> > >> Am 08.07.2008 um 23:09 schrieb smith02243: > >> > >>> > >>> Hi all, > >>> > >>> In the Linux VM, when I try to input, via paste or the right alt > >>> combination, non-ascii characters, like 'Ã¶' or 'Ã©' for example, Squeak > >>> merely shows 'o?' or 'e?' I researched into this and accordingly chose a > >>> font that supports UTF-8 and set the locale and VM command line options > >>> appropriately: > >>> > >>> export LC_CTYPE="en_IE.UTF-8" > >>> locale-gen en_IE.UTF-8 > >>> (...which claims that locale is upto date...) > >>> sudo dpkg-reconfigure -plow locales > >>> (...which outputs en_IE.UTF-8... done among other things....) > >>> squeak -encoding UTF-8 -textenc UTF-8 -pathenc UTF-8 > >>> Squeak3.10.2-7179-basic.image > >>> > >>> Now when I try to input the aforementioned characters I encounter a debug > >>> message: "Error subscript is out of bound." > >>> > >>> However, I have set Squeak's language to Spanish and then German, and the > >>> characters display perfectly well in the menus. Although, the same cannot > >>> be > >>> said for the any files with non-ascii characters in the file dialogue. > >>> So, > >>> it seems it's an input problem. > >>> > >>> Anyone with any ideas? Thanks. > >> > >> This has only been addressed recently, and may not have found its way into > >> a release yet. > >> > >> You need the very latest Squeak VM (3.10-1 at least). It supports Unicode > >> keyboard events (which are passed to the image as UTF32). > >> > >> To make use of these events your image needs to be using > >> UTF32InputInterpreter. Evaluate > >> > >> ActiveHand keyboardInterpreter > >> > >> to see the currently used one. It can be changed by patching > >> Latin1Environment class>>inputInterpreterClass. > >> > >> I don't know if this is in any official release yet, or scheduled for one. > >> > >> Some relevant change sets from the Etoys image seem to be > >> > >> http://tinlizzie.org/updates/etoys/updates/1713UnicodeInput1-yo.cs > >> http://tinlizzie.org/updates/etoys/updates/1714UnicodeInput2-yo.cs > >> http://tinlizzie.org/updates/etoys/updates/1925unixLatin1Input-yo.cs > >> http://tinlizzie.org/updates/etoys/updates/1935unicodeFallback-bf.cs > >> > >> - Bert - > >> > >> > >> _______________________________________________ > >> Beginners mailing list > >> Beginners(a)lists.squeakfoundation.org > >> http://lists.squeakfoundation.org/mailman/listinfo/beginners > >> > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > >

July 9, 2008

Re: [Pharo-project] UTF support in Linux

by Serge Stinckwich

UTF input (in VM and image) support in Pharo (or Squeak) is a must ! 2008/7/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > > Begin forwarded message: > >> From: Bert Freudenberg <bert(a)freudenbergs.de> >> Date: July 9, 2008 12:20:52 AM CEDT >> To: "A friendly place to get answers to even the most basic questions >> about Squeak." <beginners(a)lists.squeakfoundation.org> >> Subject: Re: [Newbies] UTF support in Linux? >> Reply-To: "A friendly place to get answers to even the most basic >> questions about Squeak." <beginners(a)lists.squeakfoundation.org> >> >> >> Am 08.07.2008 um 23:09 schrieb smith02243: >> >>> >>> Hi all, >>> >>> In the Linux VM, when I try to input, via paste or the right alt >>> combination, non-ascii characters, like 'Ã¶' or 'Ã©' for example, Squeak >>> merely shows 'o?' or 'e?' I researched into this and accordingly chose a >>> font that supports UTF-8 and set the locale and VM command line options >>> appropriately: >>> >>> export LC_CTYPE="en_IE.UTF-8" >>> locale-gen en_IE.UTF-8 >>> (...which claims that locale is upto date...) >>> sudo dpkg-reconfigure -plow locales >>> (...which outputs en_IE.UTF-8... done among other things....) >>> squeak -encoding UTF-8 -textenc UTF-8 -pathenc UTF-8 >>> Squeak3.10.2-7179-basic.image >>> >>> Now when I try to input the aforementioned characters I encounter a debug >>> message: "Error subscript is out of bound." >>> >>> However, I have set Squeak's language to Spanish and then German, and the >>> characters display perfectly well in the menus. Although, the same cannot >>> be >>> said for the any files with non-ascii characters in the file dialogue. >>> So, >>> it seems it's an input problem. >>> >>> Anyone with any ideas? Thanks. >> >> This has only been addressed recently, and may not have found its way into >> a release yet. >> >> You need the very latest Squeak VM (3.10-1 at least). It supports Unicode >> keyboard events (which are passed to the image as UTF32). >> >> To make use of these events your image needs to be using >> UTF32InputInterpreter. Evaluate >> >> ActiveHand keyboardInterpreter >> >> to see the currently used one. It can be changed by patching >> Latin1Environment class>>inputInterpreterClass. >> >> I don't know if this is in any official release yet, or scheduled for one. >> >> Some relevant change sets from the Etoys image seem to be >> >> http://tinlizzie.org/updates/etoys/updates/1713UnicodeInput1-yo.cs >> http://tinlizzie.org/updates/etoys/updates/1714UnicodeInput2-yo.cs >> http://tinlizzie.org/updates/etoys/updates/1925unixLatin1Input-yo.cs >> http://tinlizzie.org/updates/etoys/updates/1935unicodeFallback-bf.cs >> >> - Bert - >> >> >> _______________________________________________ >> Beginners mailing list >> Beginners(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/beginners >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

July 9, 2008

Re: [Pharo-project] Keeping track of external issues

by Adrian Lienhard

On Jul 9, 2008, at 11:15 , Norbert Hartl wrote: > On Wed, 2008-07-09 at 10:53 +0300, Adrian Lienhard wrote: >> My suggestion is that we add a comment in Mantis as follows: >> >> "This issue is also tracked by Pharo: http://code.google.com/p/pharo/issues/detail?id=XY >> " >> >> So this comment does not say whether we eventually integrated it or >> not (this can be simply found out by following the link). So the >> comment can be added already earlier in the process, which makes it >> easier. >> >> Anybody has a better idea? >> > At the moment we track Mantis tickets that we are interested in. So > we link to Mantis. What purpose is served by linking back from Mantis? just so that if you look at Mantis you can easily see whether this was treated in Pharo without needing to search in our issue tracker. Maybe its not needed, I'm not sure. So we can also go without it for now and if we see that it would be nice to have the links, we can add them later. > Is there a possibility to get a listing of bugs that pharo isn't > aware of? I have some problems understanding the intended workflow. > I added the Mantis bug numbers to the title of each issue so we can > easily get an overview of the mantis tickets we track. I think how you did it is exactly the right way. > However if we acknowledge on your proposal than the squeak issues > I created aren't the right way to do. A squeak version can include > many mantis tickets. If we like to integrate only some of them that > leads to confusion. I don't think so. The link on Mantis would just be for convenience. Say, you find an important fix on Mantis that was recently added and you want to integrate it into Pharo. The note would then be convenient to quickly see whether somebody else had already done this. > Btw. if I understand Stef correct than we shouldn't > try to integrate all 3.10 fixes but to really analyze what pharo > needs. I agree. I would focus on the important ones. > This way it would be better to get rid of the Type-squeak tickets and > to create a pharo issue Type_Mantis for every ticket we track. This > way > it would make sense to link back from mantis. I think it works well how we started. Cheers, Adrian Btw, I'm slowly going through your changes to verify them. > > > my 2 Rappen :) > > Norbert > >> Adrian >> >> On Jul 8, 2008, at 21:39 , StÃ©phane Ducasse wrote: >> >>> >>> On Jul 8, 2008, at 4:58 PM, Adrian Lienhard wrote: >>> >>>> nice >>>> >>>> Have we decided how we want to tag the Mantis issues that are >>>> integrated in Pharo? I remember we discussed >>>> - adding a comment, and >>>> - having one empty issue of which all other issues are children. >>> >>> oops I missed the second item >>> >>>> >>>> >>>> Adrian >>>> >>>> On Jul 8, 2008, at 15:46 , Norbert Hartl wrote: >>>> >>>>> I played a little with the squeak and the mantis tickets. >>>>> First, I decided to use the usual way to indicate a mantis >>>>> bug number: >>>>> >>>>> M1234. >>>>> >>>>> This way it is easily distinguishable from other version >>>>> numbers. Then I changed the title of the mantis tickets >>>>> to follow the number convention. >>>>> >>>>> M6355: [ENH] Lots of tests for Collections >>>>> >>>>> I started to change the squeak issues to include the mantis >>>>> numbers in the title. It is in () at the end of the title. E.g. >>>>> >>>>> 7073 CollectionAndCollectionTest (M3574 M5700 M6367 M6777) >>>>> >>>>> So, if you are looking for a mantis number just search for >>>>> Mantis and Squeak Tickets: >>>>> >>>>> http://code.google.com/p/pharo/issues/list?can=1&q=label%3AType-Mantis >>>>> +OR+label%3AType-Squeak >>>>> >>>>> You get a page with all mantis numbers on it. I think this >>>>> way it is not too hard to keep track. >>>>> >>>>> If you have a shell und you love nasty one liners you can do: >>>>> >>>>> wget -O - >>>>> "http://code.google.com/p/pharo/issues/list?q=label:Type-Mantis >>>>> %20OR% >>>>> 20label:Type-Squeak&can=1" | perl -ne 'while(m/(M[0-9]+)/g) >>>>> { print "$1 >>>>> \n"; }' | sort >>>>> >>>>> which outputs: >>>>> >>>>> M2446 >>>>> M3568 >>>>> M3574 >>>>> M4654 >>>>> M5251 >>>>> M5392 >>>>> M5567 >>>>> M5619 >>>>> M5641 >>>>> M5700 >>>>> M5704 >>>>> M6070 >>>>> M6355 >>>>> M6367 >>>>> M6402 >>>>> M6405 >>>>> M6520 >>>>> M6702 >>>>> M6711 >>>>> M6777 >>>>> M7090 >>>>> M7107 >>>>> >>>>> hope you like it, >>>>> >>>>> Norbert >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 9, 2008

Re: [Pharo-project] Keeping track of external issues

by Norbert Hartl

On Wed, 2008-07-09 at 10:53 +0300, Adrian Lienhard wrote: > My suggestion is that we add a comment in Mantis as follows: > > "This issue is also tracked by Pharo: http://code.google.com/p/pharo/issues/detail?id=XY > " > > So this comment does not say whether we eventually integrated it or > not (this can be simply found out by following the link). So the > comment can be added already earlier in the process, which makes it > easier. > > Anybody has a better idea? > At the moment we track Mantis tickets that we are interested in. So we link to Mantis. What purpose is served by linking back from Mantis? Is there a possibility to get a listing of bugs that pharo isn't aware of? I have some problems understanding the intended workflow. I added the Mantis bug numbers to the title of each issue so we can easily get an overview of the mantis tickets we track. However if we acknowledge on your proposal than the squeak issues I created aren't the right way to do. A squeak version can include many mantis tickets. If we like to integrate only some of them that leads to confusion. Btw. if I understand Stef correct than we shouldn't try to integrate all 3.10 fixes but to really analyze what pharo needs. This way it would be better to get rid of the Type-squeak tickets and to create a pharo issue Type_Mantis for every ticket we track. This way it would make sense to link back from mantis. my 2 Rappen :) Norbert > Adrian > > On Jul 8, 2008, at 21:39 , StÃ©phane Ducasse wrote: > > > > > On Jul 8, 2008, at 4:58 PM, Adrian Lienhard wrote: > > > >> nice > >> > >> Have we decided how we want to tag the Mantis issues that are > >> integrated in Pharo? I remember we discussed > >> - adding a comment, and > >> - having one empty issue of which all other issues are children. > > > > oops I missed the second item > > > >> > >> > >> Adrian > >> > >> On Jul 8, 2008, at 15:46 , Norbert Hartl wrote: > >> > >>> I played a little with the squeak and the mantis tickets. > >>> First, I decided to use the usual way to indicate a mantis > >>> bug number: > >>> > >>> M1234. > >>> > >>> This way it is easily distinguishable from other version > >>> numbers. Then I changed the title of the mantis tickets > >>> to follow the number convention. > >>> > >>> M6355: [ENH] Lots of tests for Collections > >>> > >>> I started to change the squeak issues to include the mantis > >>> numbers in the title. It is in () at the end of the title. E.g. > >>> > >>> 7073 CollectionAndCollectionTest (M3574 M5700 M6367 M6777) > >>> > >>> So, if you are looking for a mantis number just search for > >>> Mantis and Squeak Tickets: > >>> > >>> http://code.google.com/p/pharo/issues/list?can=1&q=label%3AType-Mantis > >>> +OR+label%3AType-Squeak > >>> > >>> You get a page with all mantis numbers on it. I think this > >>> way it is not too hard to keep track. > >>> > >>> If you have a shell und you love nasty one liners you can do: > >>> > >>> wget -O - > >>> "http://code.google.com/p/pharo/issues/list?q=label:Type-Mantis > >>> %20OR% > >>> 20label:Type-Squeak&can=1" | perl -ne 'while(m/(M[0-9]+)/g) > >>> { print "$1 > >>> \n"; }' | sort > >>> > >>> which outputs: > >>> > >>> M2446 > >>> M3568 > >>> M3574 > >>> M4654 > >>> M5251 > >>> M5392 > >>> M5567 > >>> M5619 > >>> M5641 > >>> M5700 > >>> M5704 > >>> M6070 > >>> M6355 > >>> M6367 > >>> M6402 > >>> M6405 > >>> M6520 > >>> M6702 > >>> M6711 > >>> M6777 > >>> M7090 > >>> M7107 > >>> > >>> hope you like it, > >>> > >>> Norbert > >>> > >>> > >>> _______________________________________________ > >>> 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

July 9, 2008

Re: [Pharo-project] Keeping track of external issues

by Adrian Lienhard

My suggestion is that we add a comment in Mantis as follows: "This issue is also tracked by Pharo: http://code.google.com/p/pharo/issues/detail?id=XY " So this comment does not say whether we eventually integrated it or not (this can be simply found out by following the link). So the comment can be added already earlier in the process, which makes it easier. Anybody has a better idea? Adrian On Jul 8, 2008, at 21:39 , StÃ©phane Ducasse wrote: > > On Jul 8, 2008, at 4:58 PM, Adrian Lienhard wrote: > >> nice >> >> Have we decided how we want to tag the Mantis issues that are >> integrated in Pharo? I remember we discussed >> - adding a comment, and >> - having one empty issue of which all other issues are children. > > oops I missed the second item > >> >> >> Adrian >> >> On Jul 8, 2008, at 15:46 , Norbert Hartl wrote: >> >>> I played a little with the squeak and the mantis tickets. >>> First, I decided to use the usual way to indicate a mantis >>> bug number: >>> >>> M1234. >>> >>> This way it is easily distinguishable from other version >>> numbers. Then I changed the title of the mantis tickets >>> to follow the number convention. >>> >>> M6355: [ENH] Lots of tests for Collections >>> >>> I started to change the squeak issues to include the mantis >>> numbers in the title. It is in () at the end of the title. E.g. >>> >>> 7073 CollectionAndCollectionTest (M3574 M5700 M6367 M6777) >>> >>> So, if you are looking for a mantis number just search for >>> Mantis and Squeak Tickets: >>> >>> http://code.google.com/p/pharo/issues/list?can=1&q=label%3AType-Mantis >>> +OR+label%3AType-Squeak >>> >>> You get a page with all mantis numbers on it. I think this >>> way it is not too hard to keep track. >>> >>> If you have a shell und you love nasty one liners you can do: >>> >>> wget -O - >>> "http://code.google.com/p/pharo/issues/list?q=label:Type-Mantis >>> %20OR% >>> 20label:Type-Squeak&can=1" | perl -ne 'while(m/(M[0-9]+)/g) >>> { print "$1 >>> \n"; }' | sort >>> >>> which outputs: >>> >>> M2446 >>> M3568 >>> M3574 >>> M4654 >>> M5251 >>> M5392 >>> M5567 >>> M5619 >>> M5641 >>> M5700 >>> M5704 >>> M6070 >>> M6355 >>> M6367 >>> M6402 >>> M6405 >>> M6520 >>> M6702 >>> M6711 >>> M6777 >>> M7090 >>> M7107 >>> >>> hope you like it, >>> >>> Norbert >>> >>> >>> _______________________________________________ >>> 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

July 9, 2008