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

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

by pharo＠googlecode.com

Comment #2 on issue 3708 by stephane...(a)gmail.com: Selection text color enh http://code.google.com/p/pharo/issues/detail?id=3708 in 13057

Feb. 16, 2011

Re: [Pharo-project] Smalltalk string API

by Serge Stinckwich

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: <, >, ... -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Feb. 16, 2011

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

by pharo＠googlecode.com

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

Feb. 16, 2011

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

by Johan Brichau

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

[Pharo-project] [update 1.3] #13056

by StÃ©phane Ducasse

13056 ----- Issue 3583 - FixWorkspace1.3.1 - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.2 and some more coming. Just 30 min spend on that one. Stef

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Nicolas Petton

Le mercredi 16 fÃ©vrier 2011 Ã 09:33 +0100, Torsten Bergmann a Ã©crit : > Anyone know something about the current state > of this project. Looks like it is not developed open > enough ... at least one is not able to follow any > progress or give feedback. Hi Torsten, I'm one of the guys behind SmalltalkHub. I understand your concerns, and you're right, the project is not open. Not *yet*. The reason is that we want to wait until we have a first prototype to show to the community. We can't ask for feedbacks if we don't have anything to show. Unfortunately we are a bit late, but as soon as we have something, we'll open the repository and put the prototype online for testing and feedbacks. Cheers, Nicolas

Feb. 16, 2011

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

by pharo＠googlecode.com

Updates: Status: Closed Comment #81 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 1h30 spent on that.

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Janko MivÅ¡ek

On 16. 02. 2011 08:31, Geert Claes wrote: > > I only just now noticed the interesting > http://blog.doit.st/2011/02/15/cloudforksso-openid-and-oauth-support-for-sm… > cloudforksso post on the seaside forum. Even though SmalltalkSource (if > that will be its new name?) is an > http://forum.world.st/good-news-of-the-year-tt3083142.html#a3086645 Iliad > project I reckon it would be great if it would be able to use such a single > sign-on. It would be nice to rebirth back past Squeak People into something like Smalltalk People on http://people.world.st and use account there for single sign-on on all other Smalltalk websites, what do you think? We'd need that for our GSoC site for instance, to avoid that painful registration process needed to differentiate real Smalltalkers from spammers... Janko > Ref: > http://blog.doit.st/2011/02/15/cloudforksso-openid-and-oauth-support-for-sm… > http://blog.doit.st/2011/02/15/cloudforksso-openid-and-oauth-support-for-sm… > http://forum.world.st/good-news-of-the-year-tt3083142.html#a3086645 > http://forum.world.st/good-news-of-the-year-tt3083142.html#a3086645 > > -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Feb. 16, 2011

[Pharo-project] Smalltalk string API

by Nicolas Cellier

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

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

by pharo＠googlecode.com

Comment #80 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 - FixWorkspace1.3.1 - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.2 in 1.3

Feb. 16, 2011