February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo 1.2 virtual sprint

by StÃ©phane Ducasse

If there is internet connection where I will be hacking with alain we can participate :). Stef On Feb 14, 2011, at 10:01 PM, laurent laffont wrote: > Could we organize a Pharo 1.2 virtual sprint over IRC to resolve, kill, eleminate, eradicate, destroy remaining issues ? and learn together too. > > I can do this next week from monday to wednesday evening (France time zone). > > Laurent

Feb. 15, 2011

Re: [Pharo-project] writing to the transcript stream

by StÃ©phane Ducasse

Yes probably my mistake. I always found strange to mix the view and the model. Because Transcript is either a stream with a UI or a tool. Stef On Feb 14, 2011, at 10:02 PM, Adrien BARREAU wrote: > It inherits from Object, but seems to use a Stream. But it does not support things such as nextPutAll:, ... > >> From: stephane.ducasse(a)inria.fr >> Date: Mon, 14 Feb 2011 21:48:21 +0100 >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] writing to the transcript stream >> >> probably. >> When I did threadsafetranscript I was thinking that transcript is a tool but may be this is a stream. >> >> On Feb 13, 2011, at 3:59 PM, Hilaire Fernandes wrote: >> >>> I try the following >>> >>> Text fromUser storeOn: Transcript >>> >>> It failed, as ThreadTranscript is not a Stream, but according to PBE, >>> Transcript is a Stream. >>> >>> Should I fill a bug ticket or is it a misuse? >>> >>> >>> Hilaire >>> >>> -- >>> Education 0.2 -- http://blog.ofset.org/hilaire >>> >>> >> >>

Feb. 15, 2011

Re: [Pharo-project] [SPAM] text selection feature

by Michael Roberts

fantastic thanks! Mike On Mon, Feb 14, 2011 at 11:24 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: > Hi Micheal > > it is called secondary selection. > there is also the selection bar and the find replace selection. > You can disallow them individually or change the colors > > Cheers > Alain > > > Le 14/02/2011 22:52, Sven Van Caekenberghe a Ã©crit : >> >> Micheal, >> >> On 14 Feb 2011, at 22:40, Michael Roberts wrote: >> >>> Hi, there is a recent (I don't know how old) feature where text areas >>> now highlight the selected text in all parts of the same text pane. >>> Does this feature have a name and a setting to control it? >>> >>> thanks, >>> Mike >> >> Try Settings>> Â Editing>> Â Use the secondary selection >> There is also Settings>> Â Editing>> Â Show the colored bar on the current >> line >> >> HTH, >> >> Sven >> >> >> > > >

Feb. 15, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by StÃ©phane Ducasse

Eliot you use caseOf: for the generation of C in Slang and VM maker. Now this means that - it does not need to be inlined - it could be packaged with VMMaker Are these two points correct? Stef

Feb. 15, 2011

Re: [Pharo-project] Issue 3704 in pharo: remove FakeClassPool adopt: and its senders

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3704 by stephane...(a)gmail.com: remove FakeClassPool adopt: and its senders http://code.google.com/p/pharo/issues/detail?id=3704 **thanks**

Feb. 15, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by StÃ©phane Ducasse

you should follow my lecture if one day they let me do it at Lille. Why Boolean operations are not using ifTrue:ifFalse: everywhere....? I spent two hours explaining that point. Stef On Feb 14, 2011, at 11:33 PM, Adrien BARREAU wrote: > Hi, > > I'm sorry to interrupt that discussion, but I read all the messages about that subject since you started to discuss it and I really would like to understand a thing: > Why does the case structure seem to be so bad in Smalltalk? > > I hope some of you could explain me :) > > Adrien.

Feb. 15, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by StÃ©phane Ducasse

> > > On Fri, Feb 11, 2011 at 1:43 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hi guys > > let us do another pass at cleaning and realigning the system. > Could we agree to deprecate caseOf: and caseOf:otherwise:? > it will simply the compiler, decompiler and also we do not need that at all. > > | z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. #b caseOf: z > > => > "| z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. > z detect: [:each | each key value = #b] " > > there is one user which I fixing right now. > > please don't. It is used in many places in Cog and would be extremely uncomfortable to live without. > Really? How can we help to remove this dependency? Can igor help? This means that the decompiler is more complex (more jump to analyze for a messages that is sent may be 10 times in total in the complete system). I will not compare with ifTrue:ifFalse: and the other inlined selectors that are really used. Stef

Feb. 15, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Updates: Status: Fixed Comment #63 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 (No comment was entered for this change.)

Feb. 15, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #62 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Thanks a lot. Now we should really update ConfigurationOfShout so that this version is for 1.2 and stay like that and we can move on in 1.3. Doru can you have a look at the configuration?

Feb. 15, 2011

Re: [Pharo-project] External Browser

by Yanni Chiu

On 14/02/11 3:29 PM, Hilaire Fernandes wrote: > The executed command is xdg-open "http://www.ofset.org/drgeo" > Strangely, this command works fine from a shell terminal, but not when > interpreted from the Smalltalk system command. Here's a suggestion. 1. In your shell terminal, do "env | sort > /tmp/env.shell" 2. Tweak your Smalltalk code to do "env | sort > /tmp/env.smalltalk" See if the differences, if any, gives you any ideas about what's wrong. You could also try to run a shell, and set up the environment to be exactly the same as you found in env.smalltalk, then run your command, and see if it still works in that environment. HTH

Feb. 15, 2011