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

[Pharo-project] [COTDC] 11 - ColorMappingCanvas

by laurent laffont

Today: ColorMappingCanvas Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

Feb. 14, 2011

Re: [Pharo-project] [COTDC] 10 - DummyUIManager

by laurent laffont

Can someone confirm please ? Laurent On Mon, Feb 14, 2011 at 3:18 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > If I understand: > > I'm an alternative UIManager used to run an the image without GUI. I > redefine methods which requires user input as these requests are irrelevant > in a headless environment. > > Laurent. > > > On Sun, Feb 13, 2011 at 11:40 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: > >> On 13 February 2011 19:48, laurent laffont <laurent.laffont(a)gmail.com> >> wrote: >> > Today: DummyUIManager >> > >> >> Since i went into that area not long ago.. i can give it a try. >> >> Hmm.. I'm not sure we need it anymore.. >> Maybe we still need it in a sense, that you don't want quit image on >> errors (like NonInteractiveIUManager). >> I am not an author of this class, so i can only guess what its purpose >> and so if NonInteractiveIUManager having the same one, >> then we should simply get rid of it. >> Oh yeah.. if someone wiil give an elaborate comment about its purpose >> we can see :) >> >> > Comment Of The Day Contest - One Day One Comment >> > Rules: >> > #1: Each day a not commented class is elected. Each day the best comment >> > will be integrated with name of the author(s). >> > #2: If you cannot comment it, deprecate it. >> > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> > Laurent >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> >

Feb. 14, 2011

Re: [Pharo-project] External Browser

by Hilaire Fernandes

Hello Alexander, Did you get a chance to take a look? Hilaire Le 12/02/2011 11:19, Alexander LazareviÄ a Ã©crit : > I will have a look at it > > 2011/2/12 Hilaire Fernandes > <hilaire.fernandes(a)gmail.com > <mailto:hilaire.fernandes@gmail.com>> > > Waht I meant is External Web Browser does not seem to work with > Pharo1.2/Ubuntu 10.4. Or could it be related to the VM ? > > Hilaire > > > Le 11/02/2011 16:41, Hilaire Fernandes a Ã©crit : > > I am just testing this package (installed with the metacello > > configuration) under Ubuntu 10.04, so far this method returns false: > > > > ExternalWebBrowserUnix suitsPlatform > > > > and particularly > > > > ExternalWebBrowserUnix isCLibAvailable returns false > > > > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

Feb. 14, 2011

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

by Igor Stasenko

On 14 February 2011 15:57, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > I agree with both Igor and Levente. > > Uses of caseOf: is often times solvable in more "elegant" ways. > > Though, I think in f.ex. HandMorph>>#processEvents Â and > UTF8TextConverter>>nextFromStream:, it would actually *improve* readability > to use it. > > Got any good refactoring to symbolics for those two, Igor? ;) > Yes, i having the code somewhere for translating evtBuf to nice events. So the HandMorph>>processEvents then will be: Sensor nextEvent dispatchOn: self at some day :-) As for UTF8, the caseOf is not clearly applicable, because it using ranged comparison, so you can't dispatch using the table: nextUTF8Char | value1 value2 value3 value4 | (value1 := self nextByte) ifNil: [^ self endOfStreamAction value]. value1 <= 127 ifTrue: [ "1-byte character" ^ Character value: value1 ]. "at least 2-byte character" (value2 := self nextByte) ifNil: [^self errorMalformedInput]. value1 <= 2r11011111 ifTrue: [ ^ Unicode charFromUnicode: ((value1 bitAnd: 31) bitShift: 6) + (value2 bitAnd: 63). ]. "at least 3-byte character" (value3 := self nextByte) ifNil: [^self errorMalformedInput]. (value1 <= 2r11101111) ifTrue: [ ^ Unicode charFromUnicode: ((value1 bitAnd: 15) bitShift: 12) + ((value2 bitAnd: 63) bitShift: 6) + (value3 bitAnd: 63). ]. "4-byte character" (value1 <= 2r11110111) ifTrue: [ (value4 := self nextByte) ifNil: [^self errorMalformedInput]. ^ Unicode charFromUnicode: ((value1 bitAnd: 16r7) bitShift: 18) + ((value2 bitAnd: 63) bitShift: 12) + ((value3 bitAnd: 63) bitShift: 6) + (value4 bitAnd: 63). ]. ^self errorMalformedInput > Cheers, > Henry > > -1 for removal/deprecation from me (from the system, not necessarily as > special cases for the compiler) > -- > View this message in context: http://forum.world.st/could-we-agree-to-remove-caseOf-and-caseOf-otherwise-… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko AKA sig.

Feb. 14, 2011

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

by Henrik Sperre Johansen

I agree with both Igor and Levente. Uses of caseOf: is often times solvable in more "elegant" ways. Though, I think in f.ex. HandMorph>>#processEvents and UTF8TextConverter>>nextFromStream:, it would actually *improve* readability to use it. Got any good refactoring to symbolics for those two, Igor? ;) Cheers, Henry -1 for removal/deprecation from me (from the system, not necessarily as special cases for the compiler) -- View this message in context: http://forum.world.st/could-we-agree-to-remove-caseOf-and-caseOf-otherwise-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 14, 2011

Re: [Pharo-project] OCompletion Settings

by laurent laffont

On Mon, Feb 14, 2011 at 2:12 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > In my 1.2 images, I have OCompletion settings twice in the Settings > browser: once on there own, once under Code browsing. Is that normal ? > No. See http://code.google.com/p/pharo/issues/detail?id=3620 Laurent. > > Sven > > >

Feb. 14, 2011

Re: [Pharo-project] A new GUI visual designer

by Henrik Sperre Johansen

Sven Van Caekenberghe wrote: > > > I know what UTF-8 encoding is and I know the date. However, then the > Tirade spec should say, all data is encoded in UTF-8 by default, leaving > it open like this is asking for problems. > > But even then, for a data interchange format I think that ASCII + > enscaping is a better deal that will cause less problems. > > Sven > > We are still talking about Tirade right? A Smalltalk-specific interchange format, built-in-20XX, with no existing consumers to worry about? I don't really think choosing UTF8 from the start will cause more problems for anyone, though I agree it should be an explicit fact. Cheers, Henry -- View this message in context: http://forum.world.st/A-new-GUI-visual-designer-tp3067111p3305093.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 14, 2011

Re: [Pharo-project] [COTDC] 10 - DummyUIManager

by laurent laffont

If I understand: I'm an alternative UIManager used to run an the image without GUI. I redefine methods which requires user input as these requests are irrelevant in a headless environment. Laurent. On Sun, Feb 13, 2011 at 11:40 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 13 February 2011 19:48, laurent laffont <laurent.laffont(a)gmail.com> > wrote: > > Today: DummyUIManager > > > > Since i went into that area not long ago.. i can give it a try. > > Hmm.. I'm not sure we need it anymore.. > Maybe we still need it in a sense, that you don't want quit image on > errors (like NonInteractiveIUManager). > I am not an author of this class, so i can only guess what its purpose > and so if NonInteractiveIUManager having the same one, > then we should simply get rid of it. > Oh yeah.. if someone wiil give an elaborate comment about its purpose > we can see :) > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Feb. 14, 2011

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

by pharo＠googlecode.com

Comment #59 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 I checked the latest 1.2 build based on 12335. The Debugger works great, but the Workspace still does not offer highlighting.

Feb. 14, 2011

[Pharo-project] OCompletion Settings

by Sven Van Caekenberghe

In my 1.2 images, I have OCompletion settings twice in the Settings browser: once on there own, once under Code browsing. Is that normal ? Sven

Feb. 14, 2011