November 2010 - Pharo-users

Re: [Pharo-users] Minimum spec

by Lukas Renggli

Yeah, try one of the builds from my server, e.g. one that contains all the development tools: http://hudson.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifact… I don't load OCompletion ("intellisense"), but eCompletion that only pops up when you press tab. It is much faster. Lukas On 3 November 2010 09:15, Stanislav Paskalev <kshorg(a)gmail.com> wrote: > I've experienced the same using the initial 1.1 one-click release. > Using the latest one-click build from Luka's hudson - the issue is > gone. > Stanislav Paskalev > > > > On Wed, Nov 3, 2010 at 9:49 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Strange >> is ti on long text? >> or even on Â small methods? >> >> On Nov 3, 2010, at 2:52 AM, Jeff Gray wrote: >> >>> >>> Thanks Stef. >>> >>> I'm running Pharo-1.1-11411 >>> >>> The symptom is when I press the keyboard arrows I get the delay. >>> Eg If perhaps 3 options pop up and I immediately press down arrow once and >>> enter key then, after a long delay, the 2nd item in the list is used as >>> expected. >>> -- >>> View this message in context: http://forum.world.st/Minimum-spec-tp3022984p3024757.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Pharo-users mailing list >>> Pharo-users(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > -- Lukas Renggli www.lukas-renggli.ch

Nov. 3, 2010

Re: [Pharo-users] Minimum spec

by Stanislav Paskalev

I've experienced the same using the initial 1.1 one-click release. Using the latest one-click build from Luka's hudson - the issue is gone. Stanislav Paskalev On Wed, Nov 3, 2010 at 9:49 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Strange > is ti on long text? > or even on Â small methods? > > On Nov 3, 2010, at 2:52 AM, Jeff Gray wrote: > >> >> Thanks Stef. >> >> I'm running Pharo-1.1-11411 >> >> The symptom is when I press the keyboard arrows I get the delay. >> Eg If perhaps 3 options pop up and I immediately press down arrow once and >> enter key then, after a long delay, the 2nd item in the list is used as >> expected. >> -- >> View this message in context: http://forum.world.st/Minimum-spec-tp3022984p3024757.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

Nov. 3, 2010

Re: [Pharo-users] Minimum spec

by StÃ©phane Ducasse

Strange is ti on long text? or even on small methods? On Nov 3, 2010, at 2:52 AM, Jeff Gray wrote: > > Thanks Stef. > > I'm running Pharo-1.1-11411 > > The symptom is when I press the keyboard arrows I get the delay. > Eg If perhaps 3 options pop up and I immediately press down arrow once and > enter key then, after a long delay, the 2nd item in the list is used as > expected. > -- > View this message in context: http://forum.world.st/Minimum-spec-tp3022984p3024757.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

Nov. 3, 2010

Re: [Pharo-users] Private methods

by Igor Stasenko

Coding in smalltalk for last 4 years, i seen no problems with having no run-time, no compile-time , but instead a coder-time private methods check. As to me, the benefits of having such constraints in language are exaggerated. On 3 November 2010 01:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I removed that in pharo since it was a hack working only on squeak and not even well because what happens if > I do an alias to self > > Â Â Â Â obj := self. > > Â Â Â Â obj pvt.... > > or with passing a ref to me around and client invoke the method. > > aA foo: self > > A>>foo: aA > > Â Â Â Â aA pvt > > For people that want to read a nice paper on private methods I suggest: > Â Â Â Â Encapsulation in a dynamic language by nathanael scharly > Â Â Â Â Â Â Â Â => only self send (using self keywords could be potential private call) I like the idea and the reasoning behind. > > Â Â Â Â and freezable traits to a certain extent > > > Stef > >> >> Hi >> >> Am 2010-11-02 um 10:24 schrieb eMko: >>> There is a convention of naming private methods - instead of naming it just >>> "methodName" you can use "myMethodName". >>> >>> I have seen this convention in some tutorials at squeak wiki but have not >>> seen a system class in squeak or pharo which uses this. But I do in my >>> programs. A different naming convention of private/protected methods is >>> quite common in other programming or scripting languages like Perl, Python, >>> PHP ... >> >> Incidentally, if you name your method "pvtMethodName" it is expected that >> this message is only sent to self. >> >> So if you have a class >> "--" >> Object subclass: #Foobar >> Â Â Â instanceVariableNames: '' >> Â Â Â classVariableNames: '' >> Â Â Â poolDictionaries: '' >> Â Â Â category: 'TMP' >> "--" >> >> with >> Foobar>>pvtTest >> >> Â Â Â Transcript show: 'Foobar'. >> >> and then do >> >> | a | >> a := Foobar new. >> a pvtTest. >> >> you'll end up with the Compiler telling you >> that âPrivate messages may only be sent to selfâ. >> >> However, according to Smalltalk conventions, you should >> use these âprivateâ methods scarcely. In fact, it is easy to >> circumvent this check: >> >> | a | >> a := Foobar new. >> a Â perform: #pvtTest a Foobar >> >> works easily, so don't rely on the privateness. However, >> whatever one sends to your object is up to her/him and >> she/he is responsible for the outcome ;) >> >> HTH >> >> So Long, >> Â Â Â -Tobias >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > -- Best regards, Igor Stasenko AKA sig.

Nov. 3, 2010

Re: [Pharo-users] Minimum spec

by Jeff Gray

Thanks Stef. I'm running Pharo-1.1-11411 The symptom is when I press the keyboard arrows I get the delay. Eg If perhaps 3 options pop up and I immediately press down arrow once and enter key then, after a long delay, the 2nd item in the list is used as expected. -- View this message in context: http://forum.world.st/Minimum-spec-tp3022984p3024757.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 3, 2010

Re: [Pharo-users] Private methods

by StÃ©phane Ducasse

I removed that in pharo since it was a hack working only on squeak and not even well because what happens if I do an alias to self obj := self. obj pvt.... or with passing a ref to me around and client invoke the method. aA foo: self A>>foo: aA aA pvt For people that want to read a nice paper on private methods I suggest: Encapsulation in a dynamic language by nathanael scharly => only self send (using self keywords could be potential private call) I like the idea and the reasoning behind. and freezable traits to a certain extent Stef > > Hi > > Am 2010-11-02 um 10:24 schrieb eMko: >> There is a convention of naming private methods - instead of naming it just >> "methodName" you can use "myMethodName". >> >> I have seen this convention in some tutorials at squeak wiki but have not >> seen a system class in squeak or pharo which uses this. But I do in my >> programs. A different naming convention of private/protected methods is >> quite common in other programming or scripting languages like Perl, Python, >> PHP ... > > Incidentally, if you name your method "pvtMethodName" it is expected that > this message is only sent to self. > > So if you have a class > "--" > Object subclass: #Foobar > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'TMP' > "--" > > with > Foobar>>pvtTest > > Transcript show: 'Foobar'. > > and then do > > | a | > a := Foobar new. > a pvtTest. > > you'll end up with the Compiler telling you > that âPrivate messages may only be sent to selfâ. > > However, according to Smalltalk conventions, you should > use these âprivateâ methods scarcely. In fact, it is easy to > circumvent this check: > > | a | > a := Foobar new. > a perform: #pvtTest a Foobar > > works easily, so don't rely on the privateness. However, > whatever one sends to your object is up to her/him and > she/he is responsible for the outcome ;) > > HTH > > So Long, > -Tobias > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

Nov. 2, 2010

Re: [Pharo-users] Minimum spec

by StÃ©phane Ducasse

Welcome jeff. This is strange. which version are you running? Stef > > I run Pharo on Win7 on a netbook and it works well. The only issue I have is > the "intellisense". When I start typing a message it offers me some options > in a list. To select anything but the first in the list takes upwards of 15 > seconds. No biggy and I can certainly work round it. > Is there a minimum spec for Pharo? > > -- > View this message in context: http://forum.world.st/Minimum-spec-tp3022984p3022984.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

Nov. 2, 2010

Pharocasts: the LightsOut game

by laurent laffont

Hi, new screencast: Follow the Lights Out game exercise from the book Pharo By Example. http://www.pharocasts.com/2010/11/lightsout-game.html Don't miss the SmalltalkLabs browser for blogs :) Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Nov. 2, 2010

Re: [Pharo-users] Private methods

by Tobias Pape

Hi Am 2010-11-02 um 10:24 schrieb eMko: > There is a convention of naming private methods - instead of naming it just > "methodName" you can use "myMethodName". > > I have seen this convention in some tutorials at squeak wiki but have not > seen a system class in squeak or pharo which uses this. But I do in my > programs. A different naming convention of private/protected methods is > quite common in other programming or scripting languages like Perl, Python, > PHP ... Incidentally, if you name your method "pvtMethodName" it is expected that this message is only sent to self. So if you have a class "--" Object subclass: #Foobar instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TMP' "--" with Foobar>>pvtTest Transcript show: 'Foobar'. and then do | a | a := Foobar new. a pvtTest. you'll end up with the Compiler telling you that âPrivate messages may only be sent to selfâ. However, according to Smalltalk conventions, you should use these âprivateâ methods scarcely. In fact, it is easy to circumvent this check: | a | a := Foobar new. a perform: #pvtTest a Foobar works easily, so don't rely on the privateness. However, whatever one sends to your object is up to her/him and she/he is responsible for the outcome ;) HTH So Long, -Tobias

Nov. 2, 2010

Re: [Pharo-users] Private methods

by eMko

There is a convention of naming private methods - instead of naming it just "methodName" you can use "myMethodName". I have seen this convention in some tutorials at squeak wiki but have not seen a system class in squeak or pharo which uses this. But I do in my programs. A different naming convention of private/protected methods is quite common in other programming or scripting languages like Perl, Python, PHP ... -- View this message in context: http://forum.world.st/Private-methods-tp3022981p3023395.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 2, 2010