May 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] SLICE-RelicensingPart1

by Yoshiki Ohshima

At Thu, 28 May 2009 23:12:23 +0200, Michael Rueger wrote: > > My first and pretty much most embarrassing > realization when first traveling to Japan. What happened? > Not counting all the other > screw-ups that I probably didn't even realize... Oh, these ones. ^^; -- Yoshiki

May 28, 2009

Re: [Pharo-project] Transcript does not handle multiple thread access

by FranÃ§ois Tanguy

Name: Nile-Clients-damiencassou.101 Author: damiencassou Time: 17 February 2009, 6:29:21 pm UUID: c84dacab-8c7e-48b4-b9ff-31f712051122 Ancestors: Nile-Clients-damiencassou.99, Nile-Clients-damiencassou.100 FranÃ§ois Le 28 mai 09 Ã 23:19, StÃ©phane Ducasse a Ã©crit : > Which version of threadSafeTrasncruipt do you have > > I have > > > clear > "Clear all characters and redisplay the view" > > self changed: #clearText. > accessSemaphore > critical: [ stream reset ] > > Stef > > > On May 28, 2009, at 11:06 PM, FranÃ§ois Tanguy wrote: > >> Yes I already tried but a DNU showed up when trying to execute >> "STranscript clear". >> The method reset does not exist. See the implementation below. >> >> clear >> "Clear all characters and redisplay the view" >> >> accessSemaphore critical: >> [ self changed: #clearText. >> self reset ] >> >> FranÃ§ois >> >> Le 28 mai 09 Ã 22:56, StÃ©phane Ducasse a Ã©crit : >> >>> francois >>> >>> on squeaksource there is a threadsafeTranscript >>> can you try it? >>> The idea is to get it to replace the non thread safe (= defult one). >>> >>> Stef >>> On May 28, 2009, at 10:49 PM, FranÃ§ois Tanguy wrote: >>> >>>> Hello, >>>> >>>> try this in a workspace (image 10319) : >>>> >>>> "First open a Transcript via the world menu" >>>> Transcript clear. >>>> 5 timesRepeat: [ [Transcript show: 'Hello'] fork ] >>>> >>>> Behavior is bad. >>>> >>>> >>>> Now, try the following: >>>> >>>> Transcript clear. >>>> Transcript open. >>>> 5 timesRepeat: [ [Transcript show: 'Hello'] fork ] >>>> >>>> It is always working. >>>> >>>> >>>> Is it a known problem ? Should we open an issue ? >>>> >>>> FranÃ§ois >>>> _______________________________________________ >>>> 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

May 28, 2009

[Pharo-project] License cleaning: 74 methods left

by Adrian Lienhard

I did the check again for Pharo #10310 and now we are down at 74 dirty methods. I removed all remaining methods of Richard A. Harmon (RAH) from the list of dirty methods because, as I figured out just now, they originate from the SqueakSource package "ANSI Compatibility", which is released under SqueakL. @Gabriel: this means it would be possible to use the old versions of methods, like #codePoint, you have been working on. The up to date list can be found as usual at: http://code.google.com/p/pharo/wiki/ResultofRelicensing Further help (thanks Gabriel!) is welcome... Cheers, Adrian

May 28, 2009

Re: [Pharo-project] Please change my account

by StÃ©phane Ducasse

done On May 28, 2009, at 11:18 PM, Norbert Hartl wrote: > Hi, > > I was just wondering that I wasn't able to change the ticket > status on google. I was signed in with the wrong account. > Can anyone of the admins please change my subscription from > norbert(a)hartl.name to norbert.hartl(a)googlemail.com?? > > thanks, > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 28, 2009

Re: [Pharo-project] struggeling along

by Norbert Hartl

On Thu, 2009-05-28 at 14:15 -0700, Dale Henrichs wrote: > Norbert, > > I would recommend using an older version of Pharo for GemTools - the one-click GemTools 2.3.1 preview (based on an earlier version of Pharo) is the best option, in my opinion. > Yes, you told me already. I just opened a new pharo after some time and was greedy to have all the new stuff like ocompletion. So I just gave it a try. My one click gemtools image is totally rugged at the moment. I cannot open a class browser on the pharo side anymore. Usually I don't need these because I only use the gemstone ones but.... > I am waiting for the rate of change to slow down a bit, before trying GemTools on the latest version of Pharo. > > On the other hand if you get GemTools running, let me know and I'll take it for a whirl:) > Dale, that was exactly my intention! Would be great for me to do it and tell _you_ how it works ;) Well, at least I saw that my debugging capabilities have improved in the last months *g* Norbert > Dale > > ----- "Norbert Hartl" <norbert(a)hartl.name> wrote: > > | Hi, > | > | I can't really follow the mailing list so some of these might > | already known and fixed. I just tried to install a gemtools > | client from universe. I'm using the latest pharo-dev. > | > | Installing FFI brought up an syntax error because there is > | an attempt writing to a temp. Did this change with the > | closures? I think this is fixed by the version some can load > | via the ScriptLoader. > | > | Next I encountered a problem with MIMEDocument. I think it > | is Issue-631. There is an incorrect usage of the MIMEDocument > | interface. I changed it but wanted to store it in PharoInbox > | but my image crashes if I try to. > | > | It is: > | > | Segmentation fault > | > | -1178673304 UUID>initialize > | -1178673420 Behavior>new: > | -1178673512 >new > | > | I updated my vm to exupery-0.15.1 but still has the same behaviour. > | > | I attached a patch for the MIMEDocument issue on Issue-631. > | > | Than I met InputSensor. InputSensor default returns an instance > | of InputEventSensor. This looks just strange to me. Is this right? > | > | 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

May 28, 2009

Re: [Pharo-project] Transcript does not handle multiple thread access

by StÃ©phane Ducasse

Which version of threadSafeTrasncruipt do you have I have clear "Clear all characters and redisplay the view" self changed: #clearText. accessSemaphore critical: [ stream reset ] Stef On May 28, 2009, at 11:06 PM, FranÃ§ois Tanguy wrote: > Yes I already tried but a DNU showed up when trying to execute > "STranscript clear". > The method reset does not exist. See the implementation below. > > clear > "Clear all characters and redisplay the view" > > accessSemaphore critical: > [ self changed: #clearText. > self reset ] > > FranÃ§ois > > Le 28 mai 09 Ã 22:56, StÃ©phane Ducasse a Ã©crit : > >> francois >> >> on squeaksource there is a threadsafeTranscript >> can you try it? >> The idea is to get it to replace the non thread safe (= defult one). >> >> Stef >> On May 28, 2009, at 10:49 PM, FranÃ§ois Tanguy wrote: >> >>> Hello, >>> >>> try this in a workspace (image 10319) : >>> >>> "First open a Transcript via the world menu" >>> Transcript clear. >>> 5 timesRepeat: [ [Transcript show: 'Hello'] fork ] >>> >>> Behavior is bad. >>> >>> >>> Now, try the following: >>> >>> Transcript clear. >>> Transcript open. >>> 5 timesRepeat: [ [Transcript show: 'Hello'] fork ] >>> >>> It is always working. >>> >>> >>> Is it a known problem ? Should we open an issue ? >>> >>> FranÃ§ois >>> _______________________________________________ >>> 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 >

May 28, 2009

[Pharo-project] Please change my account

by Norbert Hartl

Hi, I was just wondering that I wasn't able to change the ticket status on google. I was signed in with the wrong account. Can anyone of the admins please change my subscription from norbert(a)hartl.name to norbert.hartl(a)googlemail.com?? thanks, Norbert

May 28, 2009

Re: [Pharo-project] struggeling along

by Dale Henrichs

Norbert, I would recommend using an older version of Pharo for GemTools - the one-click GemTools 2.3.1 preview (based on an earlier version of Pharo) is the best option, in my opinion. I am waiting for the rate of change to slow down a bit, before trying GemTools on the latest version of Pharo. On the other hand if you get GemTools running, let me know and I'll take it for a whirl:) Dale ----- "Norbert Hartl" <norbert(a)hartl.name> wrote: | Hi, | | I can't really follow the mailing list so some of these might | already known and fixed. I just tried to install a gemtools | client from universe. I'm using the latest pharo-dev. | | Installing FFI brought up an syntax error because there is | an attempt writing to a temp. Did this change with the | closures? I think this is fixed by the version some can load | via the ScriptLoader. | | Next I encountered a problem with MIMEDocument. I think it | is Issue-631. There is an incorrect usage of the MIMEDocument | interface. I changed it but wanted to store it in PharoInbox | but my image crashes if I try to. | | It is: | | Segmentation fault | | -1178673304 UUID>initialize | -1178673420 Behavior>new: | -1178673512 >new | | I updated my vm to exupery-0.15.1 but still has the same behaviour. | | I attached a patch for the MIMEDocument issue on Issue-631. | | Than I met InputSensor. InputSensor default returns an instance | of InputEventSensor. This looks just strange to me. Is this right? | | Norbert | | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Adrian Lienhard

On May 28, 2009, at 23:06 , Lukas Renggli wrote: >> so the comprise for now would be to at least not actively remove >> methods/classes that are part of the ANSI standard? Yes. > Yes, this is exactly what I was asking for. I did not suggest to add > new features. Squeak 3.9 already has a pretty good ANSI compliance. This is exactly what I said one hour ago: "- keep already existing ANSI compliant behavior" I don't understand why you reply with "If you undermine the Smalltalk standard" etc. So, it seems, we agree. Adrian

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Michael Rueger

On Thu, May 28, 2009 at 11:06 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >> so the comprise for now would be to at least not actively remove >> methods/classes that are part of the Â ANSI standard? > > Yes, this is exactly what I was asking for. I did not suggest to add > new features. Squeak 3.9 already has a pretty good ANSI compliance. Always remember that sarcasm doesn't translate well into other languages or cultures. My first and pretty much most embarrassing realization when first traveling to Japan. Not counting all the other screw-ups that I probably didn't even realize... michael

May 28, 2009