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

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

by StÃ©phane Ducasse

alain do you always color? or do you rely on shout? 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] struggeling along

by Benoit St-Jean

Hey Reg! Long time no talk !!!! Depends on what you want to do... Experiment or need something stable ? ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: Reg Krock <rkrock(a)locksleycreeksoftware.com> To: Pharo-project(a)lists.gforge.inria.fr; dale.henrichs(a)gemstone.com Sent: Thursday, May 28, 2009 8:01:00 PM Subject: Re: [Pharo-project] struggeling along 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 __________________________________________________________________ Get a sneak peak at messages with a handy reading pane with All new Yahoo! Mail: http://ca.promos.yahoo.com/newmail/overview2/

May 29, 2009

Re: [Pharo-project] Finding code

by Schwab,Wilhelm K

Sebastian, Thanks for confirming the problem. Your suggested solution is natural, except that the image kept locking up during the direct approach. Hopefully my changeset idea will get around that. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Sebastian Sastre Sent: Friday, May 29, 2009 6:26 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Finding code Hi Bill, AFAIK monticello use to get the first part of the class category to define if code goes into a package or not. Why don't you make your code go into a category named differently than something named as an existent package? cheers, sebastian > -----Mensaje original----- > De: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] En nombre de > Schwab,Wilhelm K Enviado el: Friday, May 29, 2009 03:56 > Para: Pharo-project(a)lists.gforge.inria.fr > Asunto: [Pharo-project] Finding code > > I am finding that OB, Moniticello, or just plain gremlins are making > life hard on me. I have code that I want to package; more > specifically, I need to repackage some of it. I thought it might make > sense to name something Seaside-ThisOrThat, but that turns out to get > burried in the Seaside 2 category, and moving clases and methods to > SeasideThisOrThat or another package frequently locks up the image. > > I have all of the relevant code captured in a change set. Is it safe > to edit the categories in the chunks and file that into a new image? > I did that (hopefully correctly) to a copy of the change set in the > hopes tha a new image would see things in the correct place from the > bginning. > > If any of this sounds like typical newbie (re Monticello) growing > pains, please say so. > > Bill > > > _______________________________________________ > 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] Finding code

by Sebastian Sastre

Hi Bill, AFAIK monticello use to get the first part of the class category to define if code goes into a package or not. Why don't you make your code go into a category named differently than something named as an existent package? cheers, sebastian > -----Mensaje original----- > De: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] En > nombre de Schwab,Wilhelm K > Enviado el: Friday, May 29, 2009 03:56 > Para: Pharo-project(a)lists.gforge.inria.fr > Asunto: [Pharo-project] Finding code > > I am finding that OB, Moniticello, or just plain gremlins are > making life hard on me. I have code that I want to package; > more specifically, I need to repackage some of it. I thought > it might make sense to name something Seaside-ThisOrThat, but > that turns out to get burried in the Seaside 2 category, and > moving clases and methods to SeasideThisOrThat or another > package frequently locks up the image. > > I have all of the relevant code captured in a change set. Is > it safe to edit the categories in the chunks and file that > into a new image? I did that (hopefully correctly) to a copy > of the change set in the hopes tha a new image would see > things in the correct place from the bginning. > > If any of this sounds like typical newbie (re Monticello) > growing pains, please say so. > > Bill > > > _______________________________________________ > 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 FranÃ§ois Tanguy

Stef, I loaded the ThreadSafeTranscript package from squeaksource and found out one problem. The stream is not correctly reset after each access. Original code uses "stream reset" but using "stream resetContents" works much better. 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

May 29, 2009

Re: [Pharo-project] Can't update pharo0.1-10318dev09.05.4

by Oscar Nierstrasz

Ah -- must be related to all the morph issues that have been posted. I think it is not the update at all that is the problem. - on On May 29, 2009, at 9:42, Oscar Nierstrasz wrote: > > Hi Folks, > > I just downloaded the latest pharo-dev and tried to update it. I got > 12 "Undefined Object>>doesNotUnderstand: #includes" messages. > > I don't see any issue logged for this yet. Anyone else seen this? > > - on > > _______________________________________________ > 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 Romain Robbes

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

May 29, 2009

[Pharo-project] Can't update pharo0.1-10318dev09.05.4

by Oscar Nierstrasz

Hi Folks, I just downloaded the latest pharo-dev and tried to update it. I got 12 "Undefined Object>>doesNotUnderstand: #includes" messages. I don't see any issue logged for this yet. Anyone else seen this? - on

May 29, 2009

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

by Alain Plantec

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:)

May 29, 2009

[Pharo-project] Finding code

by Schwab,Wilhelm K

I am finding that OB, Moniticello, or just plain gremlins are making life hard on me. I have code that I want to package; more specifically, I need to repackage some of it. I thought it might make sense to name something Seaside-ThisOrThat, but that turns out to get burried in the Seaside 2 category, and moving clases and methods to SeasideThisOrThat or another package frequently locks up the image. I have all of the relevant code captured in a change set. Is it safe to edit the categories in the chunks and file that into a new image? I did that (hopefully correctly) to a copy of the change set in the hopes tha a new image would see things in the correct place from the bginning. If any of this sounds like typical newbie (re Monticello) growing pains, please say so. Bill

May 29, 2009