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

Re: [Pharo-project] java has yet another strike against it now

by David Mitchell

Read the thread. The collector is GPL and part of OpenJDK. Sun (soon to be Oracle) will only support it if you buy a support contract. No big deal. 2009/5/29 Steve Wirts <stevewirts(a)gmail.com>: > http://tech.slashdot.org/story/09/05/29/1711203/Java-Gets-New-Garbage-Colle… > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 29, 2009

[Pharo-project] Fwd: preferences to settings refactoring: #colorWhenPrettyPrinting case

by StÃ©phane Ducasse

>> StÃ©phane Ducasse a Ã©crit : >>> alain >>> >> This slice removes the preference from the core, so it has nothing >> to do with Shout. >> As noticed in the issue comment, because colorWhenPrettyPretting >> has already no effect when set this slice consists more in a clean- >> up. >>> do you always color? >> so, never in core >>> or do you rely on shout? >> and color in pharo (aka pharo-dev) relies on shout as always. > > ok this is what I wanted to know. > > Stef >> >> >> alain >>> >>> Stef >>> >>> On May 29, 2009, at 9:39 AM, Alain Plantec wrote: >>> >>>> Hi, >>>> A slice is upload in pharoInbox. >>>> Cheers >>>> Alain >>>> >>>> Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 >>>> Dependencies: Compiler-alain_plantec.104, >>>> Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, >>>> Polymorph-Tools-Diff-alain_plantec.21, >>>> System-FilePackage-alain_plantec.6, System-Support-alain_plantec. >>>> 27, >>>> Tools-alain_plantec.154, Traits-alain_plantec.279 >>>> >>>> Remove the #colorWhenPrettyPrinting preference. >>>> As a consequence, some code formatting methods are refactored >>>> (The major remodelling is the >>>> Compiler>>#format:in:notifying:decorated: >>>> removal, replaced by Compiler>>#format:in:notifying:) >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >> >> > > > >

May 29, 2009

[Pharo-project] java has yet another strike against it now

by Steve Wirts

http://tech.slashdot.org/story/09/05/29/1711203/Java-Gets-New-Garbage-Colle…

May 29, 2009

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

by StÃ©phane Ducasse

Ok but normally cr does this job. Stef On May 29, 2009, at 5:44 PM, FranÃ§ois Tanguy wrote: > See below my answer. > > Le 29 mai 09 Ã 17:34, StÃ©phane Ducasse a Ã©crit : > >> Thanks francois. >> >> >> On May 29, 2009, at 11:55 AM, FranÃ§ois Tanguy wrote: >> >>> Stef, >>> >>> I loaded the ThreadSafeTranscript package from squeaksource and >>> found >>> out one problem. >>> >>> The stream is not correctly reset after each access. >> >> why should it be reset after each access? > > If you do something like this > STranscript show: 'a very longggggggggggg message'. > STranscript show: 'a normal message' > > The result in the transcript will be : a very longggggggggggg messagea > normal messageggggg message > > The reason is because the readLimit instance variable from > PositionableStream is not reset to 0 after the first message. > >> >> >>> Original code uses "stream reset" but using "stream resetContents" >>> works much better. > > resetContents makes the same job than reset but it also set readLimit > to 0. > >>> >> >> ok I will check >> I published a new version with << (= show: to be compatible with the >> other streams) support >> >> stef >> >>> >>> >>> Cheers. >>> >>> FranÃ§ois >>> >>> Le 28 mai 09 Ã 23:52, StÃ©phane Ducasse a Ã©crit : >>> >>>> Not this one. >>>> ThreadSafeTranscript is on squeaksource same name. >>>> Now I just check and I do not know why is shown >>>> Argh >>>> >>>> Stef >>>> >>>> >>>> On May 28, 2009, at 11:27 PM, FranÃ§ois Tanguy wrote: >>>> >>>>> 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 >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >

May 29, 2009

Re: [Pharo-project] preferences to settings refactoring: #colorWhenPrettyPrinting case

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : > alain > This slice removes the preference from the core, so it has nothing to do with Shout. As noticed in the issue comment, because colorWhenPrettyPretting has already no effect when set this slice consists more in a clean-up. > do you always color? so, never in core > or do you rely on shout? and color in pharo (aka pharo-dev) relies on shout as always. alain > > Stef > > On May 29, 2009, at 9:39 AM, Alain Plantec wrote: > >> Hi, >> A slice is upload in pharoInbox. >> Cheers >> Alain >> >> Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 >> Dependencies: Compiler-alain_plantec.104, >> Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, >> Polymorph-Tools-Diff-alain_plantec.21, >> System-FilePackage-alain_plantec.6, System-Support-alain_plantec.27, >> Tools-alain_plantec.154, Traits-alain_plantec.279 >> >> Remove the #colorWhenPrettyPrinting preference. >> As a consequence, some code formatting methods are refactored >> (The major remodelling is the Compiler>>#format:in:notifying:decorated: >> removal, replaced by Compiler>>#format:in:notifying:) >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > >

May 29, 2009

Re: [Pharo-project] Minor test runner bug?

by Mariano Martinez Peck

Ok, I create this one: http://code.google.com/p/pharo/issues/detail?id=859 On Thu, May 28, 2009 at 6:49 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > damien I prefer that we try to confirm this first because after it can > take time to close. > > On May 28, 2009, at 9:00 AM, Damien Cassou wrote: > > > 2009/5/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> Is this a bug ? If someone confirm it I will create a ticket. > > > > Please create a ticket in all cases. We will close it if it's not a > > bug. > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Lambdas are relegated to relative obscurity until Java makes them > > popular by not having them." James Iry > > > > _______________________________________________ > > 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 29, 2009

Re: [Pharo-project] struggeling along

by Dale Henrichs

GemStone does not provide a GUI client. For the GUI we have relied upon other Smalltalks (like VW) to provide the GUI for GemStone. GemTools is the GLASS client GUI (OmniBrowser-based) that runs on Pharo and Squeak and provides development tools for GemStone. See [1] for more details on GemTools. Dale [1] http://gemstonesoup.wordpress.com/2009/03/16/terse-guide-to-the-new-glass-t… ----- "Carlos Crosetti" <carlos(a)mostar.com.ar> wrote: | GemTools: pointers? | | -----Mensaje original----- | De: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Dale | Henrichs | Enviado el: Jueves, 28 de Mayo de 2009 09:11 p.m. | Para: Reg Krock | CC: Pharo-project(a)lists.gforge.inria.fr | Asunto: Re: [Pharo-project] struggeling along | | | The 2.3.1 preview one-click is based on the dev image for 10243 and I | use | 10259 at work, both work fine for GemTools usage. | | Dale | | ----- "Reg Krock" <rkrock(a)locksleycreeksoftware.com> wrote: | | | Which version of Pharo would you recommend? | | | | Reg | | | | On 28-May-09, at 5:15 PM, 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. | | > | | > 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 | | > | | > _______________________________________________ | | > Pharo-project mailing list | | > Pharo-project(a)lists.gforge.inria.fr | | > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | > | | | | Reg Krock | | rkrock(a)locksleycreeksoftware.com | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | | | -- | Internal Virus Database is out-of-date. | Checked by AVG. | Version: 7.5.524 / Virus Database: 270.12.11/2089 - Release Date: | 30/04/2009 | 05:53 p.m.

May 29, 2009

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

by FranÃ§ois Tanguy

See below my answer. Le 29 mai 09 Ã 17:34, StÃ©phane Ducasse a Ã©crit : > Thanks francois. > > > On May 29, 2009, at 11:55 AM, FranÃ§ois Tanguy wrote: > >> Stef, >> >> I loaded the ThreadSafeTranscript package from squeaksource and found >> out one problem. >> >> The stream is not correctly reset after each access. > > why should it be reset after each access? If you do something like this STranscript show: 'a very longggggggggggg message'. STranscript show: 'a normal message' The result in the transcript will be : a very longggggggggggg messagea normal messageggggg message The reason is because the readLimit instance variable from PositionableStream is not reset to 0 after the first message. > > >> Original code uses "stream reset" but using "stream resetContents" >> works much better. resetContents makes the same job than reset but it also set readLimit to 0. >> > > ok I will check > I published a new version with << (= show: to be compatible with the > other streams) support > > stef > >> >> >> Cheers. >> >> FranÃ§ois >> >> Le 28 mai 09 Ã 23:52, StÃ©phane Ducasse a Ã©crit : >> >>> Not this one. >>> ThreadSafeTranscript is on squeaksource same name. >>> Now I just check and I do not know why is shown >>> Argh >>> >>> Stef >>> >>> >>> On May 28, 2009, at 11:27 PM, FranÃ§ois Tanguy wrote: >>> >>>> 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 >>>> >>>> >>>> _______________________________________________ >>>> 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 29, 2009

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

by StÃ©phane Ducasse

Thanks francois. On May 29, 2009, at 11:55 AM, FranÃ§ois Tanguy wrote: > Stef, > > I loaded the ThreadSafeTranscript package from squeaksource and found > out one problem. > > The stream is not correctly reset after each access. why should it be reset after each access? > Original code uses "stream reset" but using "stream resetContents" > works much better. ok I will check I published a new version with << (= show: to be compatible with the other streams) support stef > > > Cheers. > > FranÃ§ois > > Le 28 mai 09 Ã 23:52, StÃ©phane Ducasse a Ã©crit : > >> Not this one. >> ThreadSafeTranscript is on squeaksource same name. >> Now I just check and I do not know why is shown >> Argh >> >> Stef >> >> >> On May 28, 2009, at 11:27 PM, FranÃ§ois Tanguy wrote: >> >>> 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 >>> >>> >>> _______________________________________________ >>> 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 29, 2009

Re: [Pharo-project] [ANN] update to OCompletion

by StÃ©phane Ducasse

Yes but I work in the core image most of the time.... :) On May 29, 2009, at 10:04 AM, Romain Robbes wrote: > As much as ecompletion does, which is enough. > Try it out! > > Romain > > On May 28, 2009, at 7:56 PM, StÃ©phane Ducasse wrote: > >> Romain >> do you support instance variable completion? :) >> Stef >> >> >> On May 28, 2009, at 2:32 PM, Romain Robbes wrote: >> >>> Of course, I forgot to remind you how to install it. Just execute >>> the >>> following line in a workspace: >>> >>> Installer squeaksource project: 'OCompletion'; install: 'OCLoader'. >>> >>> Cheers, >>> Romain >>> >>> On May 28, 2009, at 2:30 PM, Romain Robbes wrote: >>> >>>> new in this update: >>>> >>>> -OCompletion completes also class names! If the prefix starts with >>>> an >>>> uppercase letter, OCompletion will propose recently changed >>>> classes. >>>> Since it maintains its small list of classes, the speed problem >>>> Hernan >>>> encountered is partially solved (it still slows downs while you >>>> scroll >>>> in the extended list). Also, Henrik's concern about case >>>> sensitivity >>>> is now solved for that case (I still think it should be case- >>>> insensitive after the first letter, but we can discuss this). >>>> -OCompletion uses the default font for menus, which is indeed >>>> nicer ;-) >>>> -OCompletion only proposes matches strictly longer than what was >>>> actually typed. >>>> -Various small bug fixes (thanks Simon!). >>>> >>>> I'm looking forward to your feedback as usual, >>>> Romain >>>> >>>> -- >>>> Romain Robbes >>>> http://www.inf.unisi.ch/phd/robbes >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> Romain Robbes >>> http://www.inf.unisi.ch/phd/robbes >>> >>> >>> _______________________________________________ >>> 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 > > -- > Romain Robbes > http://www.inf.unisi.ch/phd/robbes > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 29, 2009