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

Re: [Pharo-project] struggeling along

by Norbert Hartl

On Thu, 2009-05-28 at 23:09 +0200, Michael Rueger wrote: > On Thu, May 28, 2009 at 11:06 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > Than I met InputSensor. InputSensor default returns an instance > > of InputEventSensor. This looks just strange to me. Is this right? > > Welcome to the input event/sensor refactoring ;-) > I take this as a "yes"! :) Norbert

May 28, 2009

Re: [Pharo-project] struggeling along

by Michael Rueger

On Thu, May 28, 2009 at 11:06 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Than I met InputSensor. InputSensor default returns an instance > of InputEventSensor. This looks just strange to me. Is this right? Welcome to the input event/sensor refactoring ;-) Michael

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Lukas Renggli

> 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. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

May 28, 2009

[Pharo-project] struggeling along

by Norbert Hartl

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

May 28, 2009

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

by FranÃ§ois Tanguy

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

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Michael Rueger

On Thu, May 28, 2009 at 10:56 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > It's a matter of priorities. We decided for instance that license > cleaning, closures, and making all tests green is more important than > ANSI compliance. Of course, we could add stuff like ANSI to the list, > but then we will never deliver, not event a first version, because so the comprise for now would be to at least not actively remove methods/classes that are part of the ANSI standard? Michael

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Adrian Lienhard

It's a matter of priorities. We decided for instance that license cleaning, closures, and making all tests green is more important than ANSI compliance. Of course, we could add stuff like ANSI to the list, but then we will never deliver, not event a first version, because there is always something important to be done. Its not a question of will, but of resources. If people feel that Pharo cannot be used because its not compliant they are welcome to provide improvements. If people feel that Pharo cannot be used because its not compliant and they are not able to provide improvements then they can simply choose something else. Adrian On May 28, 2009, at 22:29 , Lukas Renggli wrote: >> Full compliance, on the other hand, is not a primary goal. > > ANSI Smalltalk is nominal. Too minimal for many tasks, and still > people build their frameworks on these foundations to keep their code > portable across platforms. If you undermine the Smalltalk standard, > Pharo simply can't be the choice for open-source development anymore. > Full ANSI compliance must a primary goal. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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

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 >

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Michael Rueger

<OT> > Full ANSI compliance must a primary goal. I politely disagree. ANSI is the least common denominator, the worst of all possible solutions. Just look at German pre-election politics right now and what you get is ANSI. it should be a loadable package, but not be driving design decisions. Just MTM (my two marks, when it still was worth something, like the Swiss Franks back then ;-) ) michael

May 28, 2009

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

by FranÃ§ois Tanguy

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

May 28, 2009