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

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Comment #3 on issue 3707 by tudor.gi...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 In the latest version of GLMUITheme (from squeaksource.com/Glamour) you get a setPreferredShoutColors which pretty much reproduces the old highlighting. Just note that this is subject to change - if I manage to find some references for what makes a good highlighting scheme :).

Feb. 16, 2011

Re: [Pharo-project] [squeak-dev] Re: Smalltalk string API

by Bert Freudenberg

On 16.02.2011, at 10:39, Serge Stinckwich wrote: > On Wed, Feb 16, 2011 at 4:24 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> I started referencing Smalltalk idioms at >> http://en.wikipedia.org/wiki/Comparison_of_programming_languages_(string_fu… >> I could have focused on ANSI but have chosen Squeak/Pharo. Feel free >> to correct me and to complete me. >> >> This is a very enlighting exercize, especially for pointing when API >> turns to be not that bright. >> During my perigrination, I notably noticed this: >> >> #compare: returns 1, 2, or 3 : this is both very object oriented, very >> intuitive and very standard and the rest of the world is stupid, >> unless... > > Yes, really stupid, but maybe Squeak/Pharo should align here to the > rest of the world or > better, remove this method. We could use comparaison methods instead: <, >, ... It is a low-level primitive, better indeed to use those operators instead, not call the compare* methods directly. For case-insensitive comparisons you should use e.g. caseInsensitiveLessOrEqual:. If we want to provide a method that answers -1, 0, and 1 I'd leave the #compare: family alone, and instead add the operator <=> as in Ruby (which would be case-sensitive). My 0.02â¬ - Bert -

Feb. 16, 2011

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Comment #2 on issue 3707 by Benjamin...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 You can change that in your settings. I can maybe propose a fix to change default value :)

Feb. 16, 2011

Re: [Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

would something like that more readable? On Feb 16, 2011, at 10:37 AM, Johan Brichau wrote: > This is a good effort. I have the letter ready for submission. > > May I ask what the 'conditions for membership' are likely to be? By signing the letter, we acknowledge our intent to join the consortium 'subject to the conditions for membership'. I would at least like to know what these are ;-) > > Johan > > On 15 Feb 2011, at 15:49, Adrian Lienhard wrote: > >> BTW, the call is also online at http://pharo-project.org/community/consortium >> >> Adrian >> >> On Feb 15, 2011, at 14:02 , StÃ©phane Ducasse wrote: >> >>> Please distribute this message around >>> >>> >>> Dear Pharoers >>> >>> We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. >>> >>> We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) >>> >>> Thanks for your support >>> >>> The Pharo Board >>> >>> M. Denker, S. Ducasse, and A. Lienhard >>> >>> >>> <Pharo-LetterOfSupport-EN.doc> >> >> > >

Feb. 16, 2011

Re: [Pharo-project] Issue 3697 in pharo: UI Enhancements

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3697 by stephane...(a)gmail.com: UI Enhancements http://code.google.com/p/pharo/issues/detail?id=3697 in 13057

Feb. 16, 2011

Re: [Pharo-project] Smalltalk string API

by StÃ©phane Ducasse

Hi nicolas propose something and we can react :) I'm busy with project proposal, teaching and 1.2 right now. Stef On Feb 16, 2011, at 10:24 AM, Nicolas Cellier wrote: > I started referencing Smalltalk idioms at > http://en.wikipedia.org/wiki/Comparison_of_programming_languages_(string_fu… > I could have focused on ANSI but have chosen Squeak/Pharo. Feel free > to correct me and to complete me. > > This is a very enlighting exercize, especially for pointing when API > turns to be not that bright. > During my perigrination, I notably noticed this: > > #compare: returns 1, 2, or 3 : this is both very object oriented, very > intuitive and very standard and the rest of the world is stupid, > unless... > > #findLastOccurrenceOfString:startingAt: in its current form is stupid > to my taste, because > 1) implementation is inefficient > 2) the startingAt: only skip the beginning of the string which seems > odd for a rfind operation > I would rather expect this kind of usage: > last := aString findLastOccurrenceOfString: 'to' startingAt: aString size. > lastButOne := aString findLastOccurrenceOfString: 'to' startingAt: last - 1. > > The CamelCase is sometimes abusive like #includesSubString: > > There is no format. I know, purists will tell me that encoding a > format in a cryptic string is not in the Smalltalk spirit, but please > then tell me how to specify a formatting efficiently and also remove > cryptic regex encoding (a pity, it's not in trunk). > > I let a few holes (split/join etc...) > > Cheers >

Feb. 16, 2011

[Pharo-project] Issue 3715 in pharo: Workspace shouting after switching between shout/unshout

by pharo＠googlecode.com

Status: Accepted Owner: Benjamin...(a)gmail.com New issue 3715 by Benjamin...(a)gmail.com: Workspace shouting after switching between shout/unshout http://code.google.com/p/pharo/issues/detail?id=3715 I do not know why but when you switch unshout -> shout again in the menu, then when you automatically declare a variable, this one is not correctly shouted But first, I will fix the bold issue ^^

Feb. 16, 2011

Re: [Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

On Feb 16, 2011, at 10:37 AM, Johan Brichau wrote: > This is a good effort. I have the letter ready for submission. Thanks Johan!!! > > May I ask what the 'conditions for membership' are likely to be? By signing the letter, we acknowledge our intent to join the consortium 'subject to the conditions for membership'. I would at least like to know what these are ;-) The idea is that we do not know. We are prospecting to see if this is worth the pain (I believ it does but chekcing is always better). I thought that the english ('subject to the conditions for membership') wanted to say that depending on the condition so may be I should change the letter to make this part clearer. > > Johan > > On 15 Feb 2011, at 15:49, Adrian Lienhard wrote: > >> BTW, the call is also online at http://pharo-project.org/community/consortium >> >> Adrian >> >> On Feb 15, 2011, at 14:02 , StÃ©phane Ducasse wrote: >> >>> Please distribute this message around >>> >>> >>> Dear Pharoers >>> >>> We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. >>> >>> We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) >>> >>> Thanks for your support >>> >>> The Pharo Board >>> >>> M. Denker, S. Ducasse, and A. Lienhard >>> >>> >>> <Pharo-LetterOfSupport-EN.doc> >> >> > >

Feb. 16, 2011

Re: [Pharo-project] Issue 3708 in pharo: Selection text color enh

by pharo＠googlecode.com

Comment #3 on issue 3708 by stephane...(a)gmail.com: Selection text color enh http://code.google.com/p/pharo/issues/detail?id=3708 Alain apparently your slice removed classes that are needed by UIFinder. I cannot cherry pick your change so it would be nice if you could republish it.

Feb. 16, 2011

Re: [Pharo-project] Issue 3710 in pharo: Get Rid of PluggableShoutMorph References

by pharo＠googlecode.com

Updates: Cc: laurent.laffont Comment #1 on issue 3710 by stephane...(a)gmail.com: Get Rid of PluggableShoutMorph References http://code.google.com/p/pharo/issues/detail?id=3710 laurent can you fix profStef?

Feb. 16, 2011