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

[Pharo-project] UTF support in Linux

by StÃ©phane Ducasse

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 >

July 9, 2008

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

by StÃ©phane Ducasse

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 >

July 8, 2008

Re: [Pharo-project] How to follow which packages have been integrated ,

by StÃ©phane Ducasse

Yes we did that like that in mantis for 3.9 And this is the minimum we should do. stef On Jul 8, 2008, at 2:34 PM, Norbert Hartl wrote: > On Tue, 2008-07-08 at 15:16 +0300, Adrian Lienhard wrote: >> I think the issue tracker should reflect all changes. Like this, to >> see whether something is harvested you look there instead of the >> SqueakSource repository. I think Stef always updates the status of >> the >> issues when pushing them into the update stream. When they are >> rejected there exists also a special state for this situation. >> >> So maybe PharoRejected is not needed, not sure. >> > +1 > > We should use the tool as far as we can. Stef does indeed add > a comment to the ticket if he harvests it. We did even add > a note to mantis on bugs.squeak.org if the bug is harvested > in pharo. > > Norbert > >> Adrian >> >> On Jul 8, 2008, at 10:21 , StÃ©phane Ducasse wrote: >> >>> why not. I think that this may improve communication. >>> the harvested will have to be more cautious but this is ok for me. >>> >>>> <serge.stinckwich(a)doesnotunderstand.org> wrote: >>>>> I still have some difficulties to know exactly what have been >>>>> integrated in Pharo after putting some .mcz in the PharoInbox. >>>>> I have to check manually if packages have been integrated or just >>>>> put >>>>> in PharoTreated (and i to repropose another version of the fix to >>>>> the >>>>> PharoInbox repository). >>>> >>>> What about a PharoRejected box? >>>> >>>> -- >>>> Damien Cassou >>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >>>> >>>> _______________________________________________ >>>> 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 8, 2008

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

by Adrian Lienhard

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. 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

July 8, 2008

[Pharo-project] Keeping track of external issues

by Norbert Hartl

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

July 8, 2008

Re: [Pharo-project] How to follow which packages have been integrated ,

by Norbert Hartl

On Tue, 2008-07-08 at 15:16 +0300, Adrian Lienhard wrote: > I think the issue tracker should reflect all changes. Like this, to > see whether something is harvested you look there instead of the > SqueakSource repository. I think Stef always updates the status of the > issues when pushing them into the update stream. When they are > rejected there exists also a special state for this situation. > > So maybe PharoRejected is not needed, not sure. > +1 We should use the tool as far as we can. Stef does indeed add a comment to the ticket if he harvests it. We did even add a note to mantis on bugs.squeak.org if the bug is harvested in pharo. Norbert > Adrian > > On Jul 8, 2008, at 10:21 , StÃ©phane Ducasse wrote: > > > why not. I think that this may improve communication. > > the harvested will have to be more cautious but this is ok for me. > > > >> <serge.stinckwich(a)doesnotunderstand.org> wrote: > >>> I still have some difficulties to know exactly what have been > >>> integrated in Pharo after putting some .mcz in the PharoInbox. > >>> I have to check manually if packages have been integrated or just > >>> put > >>> in PharoTreated (and i to repropose another version of the fix to > >>> the > >>> PharoInbox repository). > >> > >> What about a PharoRejected box? > >> > >> -- > >> Damien Cassou > >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >> > >> _______________________________________________ > >> 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 8, 2008

Re: [Pharo-project] How to follow which packages have been integrated ,

by Adrian Lienhard

I think the issue tracker should reflect all changes. Like this, to see whether something is harvested you look there instead of the SqueakSource repository. I think Stef always updates the status of the issues when pushing them into the update stream. When they are rejected there exists also a special state for this situation. So maybe PharoRejected is not needed, not sure. Adrian On Jul 8, 2008, at 10:21 , StÃ©phane Ducasse wrote: > why not. I think that this may improve communication. > the harvested will have to be more cautious but this is ok for me. > >> <serge.stinckwich(a)doesnotunderstand.org> wrote: >>> I still have some difficulties to know exactly what have been >>> integrated in Pharo after putting some .mcz in the PharoInbox. >>> I have to check manually if packages have been integrated or just >>> put >>> in PharoTreated (and i to repropose another version of the fix to >>> the >>> PharoInbox repository). >> >> What about a PharoRejected box? >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >> _______________________________________________ >> 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 8, 2008

Re: [Pharo-project] website design proposal

by Marcus Denker

On 08.07.2008, at 11:39, Norbert Hartl wrote: > On Tue, 2008-07-08 at 11:09 +0200, StÃ©phane Ducasse wrote: >> pharo-project.org is available and we have the design so now .... >> we should get cmsbox :) >> > Ah, you chose Hetzner as hosting provider. Very good. Most of our > servers are there, too :) Is this a dedicated machine or a web hosting > thing? Hetzner just is the domain registrar. CMSBox is a hosted solution, sponsored by cmsbox.ch and netstyle.ch Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

July 8, 2008

Re: [Pharo-project] website design proposal

by Norbert Hartl

On Tue, 2008-07-08 at 11:09 +0200, StÃ©phane Ducasse wrote: > pharo-project.org is available and we have the design so now .... > we should get cmsbox :) > Ah, you chose Hetzner as hosting provider. Very good. Most of our servers are there, too :) Is this a dedicated machine or a web hosting thing? Norbert > Stef > > > On Jul 8, 2008, at 10:54 AM, Damien Cassou wrote: > > > Love it > > > > On Sun, Jul 6, 2008 at 12:51 PM, Samuel MORELLO > > <samuel.morello(a)ouvanous.com> wrote: > >> Hi, > >> > >> Please find enclosed a proposal for the pharo website and a new > >> version of > >> the logo. > >> The website proposal can seems strange at first but i think it can > >> be cool > >> to have something a little bit different and colored like this. > >> > >> I have took for this example the text from IOlanguage because i > >> find this > >> site very good for the organisation and the clarity. > >> There are things to change but would like to have your opinion > >> > >> Hope you will like it > >> > >> > >> regards, > >> > >> Samuel > >> > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > > > > > > > > -- > > Damien Cassou > > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > > > _______________________________________________ > > 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 8, 2008

Re: [Pharo-project] website design proposal

by Samuel MORELLO

I have start to create the css/html template. And will try to send it rapidly. Sam On Tue, Jul 8, 2008 at 11:09 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > pharo-project.org is available and we have the design so now .... > we should get cmsbox :) > > Stef > > > > On Jul 8, 2008, at 10:54 AM, Damien Cassou wrote: > > Love it >> >> On Sun, Jul 6, 2008 at 12:51 PM, Samuel MORELLO >> <samuel.morello(a)ouvanous.com> wrote: >> >>> Hi, >>> >>> Please find enclosed a proposal for the pharo website and a new version >>> of >>> the logo. >>> The website proposal can seems strange at first but i think it can be >>> cool >>> to have something a little bit different and colored like this. >>> >>> I have took for this example the text from IOlanguage because i find this >>> site very good for the organisation and the clarity. >>> There are things to change but would like to have your opinion >>> >>> Hope you will like it >>> >>> >>> regards, >>> >>> Samuel >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> >> >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >> _______________________________________________ >> 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 > -- Samuel +33 (0)6 20 65 22 99

July 8, 2008