November 2010 - Pharo-users

Re: [Pharo-users] How to make a Morph that gets to handle all arrow-key-events?

by StÃ©phane Ducasse

Change your alias. It is childish to ask for help in programming if you do not want to program. Use any funny alias but not that one! Stef > > hi, > for a game i want one Morph to get all the arrow-key-events, whether it has > the focus or not. > what is the best way to make this happen? > > is it a good idea anyway? One Morph-Object can be moved around the screen > using arrow keys. i thought it would be the best if it would listen to the > arrow-key-events itself? > > thank you very much for help. > -- > View this message in context: http://forum.world.st/How-to-make-a-Morph-that-gets-to-handle-all-arrow-key… > 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. 22, 2010

How to make a Morph that gets to handle all arrow-key-events?

by reluctant

hi, for a game i want one Morph to get all the arrow-key-events, whether it has the focus or not. what is the best way to make this happen? is it a good idea anyway? One Morph-Object can be moved around the screen using arrow keys. i thought it would be the best if it would listen to the arrow-key-events itself? thank you very much for help. -- View this message in context: http://forum.world.st/How-to-make-a-Morph-that-gets-to-handle-all-arrow-key… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 21, 2010

Re: [Pharo-users] Private methods

by StÃ©phane Ducasse

gone with the wind. end of discussion. On Nov 19, 2010, at 7:42 PM, Mariano Martinez Peck wrote: > At some point, I don't know now, you could create methods like #pvtMethod (notice the pvt prefix), and then there was a hack somewhere (maybe in Compiler) where you only could send those methods from self. > > I don't know the status of that. Something similar was in VAST (if I remember correclty) where you could put methods in a 'private' category and then someone trows and error if the message was sent from outside self.... > > cheers > > mariano > > On Wed, Nov 3, 2010 at 10:42 AM, Simon Denier <Simon.Denier(a)inria.fr> wrote: > > On 3 nov. 2010, at 05:47, Igor Stasenko wrote: > > > 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. > > > Indeed, for such rules, I think Lint should be the platform of choice (using the parse tree search if necessary). > > > > > > 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. > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > Simon > > > > > _______________________________________________ > 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. 20, 2010

Re: [Pharo-users] [Pharo-project] could not search contents at http://book.pharo-project.org

by Mariano Martinez Peck

hello? I think this is important. We should be able to search. Cheers mariano On Wed, Oct 13, 2010 at 12:39 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Can someone take a look? how can we get the pier image? > > > On Sun, Oct 10, 2010 at 12:46 PM, Tudor Girba <tudor.girba(a)gmail.com>wrote: > >> Hi, >> >> Unfortunately, I cannot help much at this moment. The problem is due to a >> bug in Pier that crashes when there is a strange character in one of the >> pages. I believe this was fixed at some point, but I am not sure. Someone >> would have to update the Pier image. >> >> Cheers, >> Doru >> >> >> On 10 Oct 2010, at 11:53, Mariano Martinez Peck wrote: >> >> > Thanks! I can reproduce. >> > >> > Doru can you help us? >> > >> > Thanks >> > >> > Mariano >> > >> > On Thu, Oct 7, 2010 at 10:40 PM, Bernardo Ezequiel Contreras < >> vonbecmann(a)gmail.com> wrote: >> > Hi All, >> > >> > Description: >> > Could not search contents at http://book.pharo-project.org. >> > I would like to search some expression in the contents of the book. >> > >> > Steps to reproduce: >> > * goto to http://book.pharo-project.org >> > * click on main image >> > * add any string on search contents and press Enter >> > Actual Result: >> > Seaside Walkback >> > >> > Error: subscript is out of bounds: 8218 >> > >> > Expected Result: >> > a list of results that matches your input string >> > >> > >> > Thanks, >> > >> > >> > _______________________________________________ >> > Pharo-users mailing list >> > Pharo-users(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "In a world where everything is moving ever faster, >> one might have better chances to win by moving slower." >> >> >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > >

Nov. 19, 2010

Re: [Pharo-users] Private methods

by Mariano Martinez Peck

At some point, I don't know now, you could create methods like #pvtMethod (notice the pvt prefix), and then there was a hack somewhere (maybe in Compiler) where you only could send those methods from self. I don't know the status of that. Something similar was in VAST (if I remember correclty) where you could put methods in a 'private' category and then someone trows and error if the message was sent from outside self.... cheers mariano On Wed, Nov 3, 2010 at 10:42 AM, Simon Denier <Simon.Denier(a)inria.fr> wrote: > > On 3 nov. 2010, at 05:47, Igor Stasenko wrote: > > > 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. > > > Indeed, for such rules, I think Lint should be the platform of choice > (using the parse tree search if necessary). > > > > > > 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. > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > Simon > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

Nov. 19, 2010

Re: [Pharo-users] Bogus

by Lukas Renggli

Yes, the packages Bogus, BogusInfo and BogusExt are used by Monticello 2, OmniBrowser, and Gofer for testing. They contain mock code solely used in test cases. Normally, if you don't have the tests of Monticello 2, OmniBrowser or Gofer loaded, you shouldn't have any of the Bogus packages loaded either. Lukas On 18 November 2010 14:17, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Testing. If you see the category of such methods you see it is > *bogusext-testing > > this means it is an extension from the package bogusext-testing > > I think it is usd by Omnibrowser. > > cheers > > mariano > > On Thu, Nov 11, 2010 at 12:05 AM, Jeff Gray <jeff(a)rogerthedog.com> wrote: >> >> What is the String>>isBogus method for? >> >> -- >> View this message in context: >> http://forum.world.st/Bogus-tp3037199p3037199.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 > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 18, 2010

Re: [Pharo-users] Bogus

by Mariano Martinez Peck

Testing. If you see the category of such methods you see it is *bogusext-testing this means it is an extension from the package bogusext-testing I think it is usd by Omnibrowser. cheers mariano On Thu, Nov 11, 2010 at 12:05 AM, Jeff Gray <jeff(a)rogerthedog.com> wrote: > > What is the String>>isBogus method for? > > -- > View this message in context: > http://forum.world.st/Bogus-tp3037199p3037199.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. 18, 2010

Re: [Pharo-users] Latest windows CogVM + Pharo 1.1 - fail to load system fonts

by Mariano Martinez Peck

Hi Stanislav. The best place to report about Cog is the squeak-vm mailing list (vm-dev(a)lists.squeakfoundation.org ) Cheers Mariano On Nov 3, 2010, at 8:22 AM, Stanislav Paskalev wrote: > Hi, > No errors are reported or anything, it's just that the fonts list is > not populated with CogVM. Using the same image and the pharo 4.0.2 > win32 vm - it's filled ok. > > Where do we report bugs against CogVM ? > > Best regards, > Stanislav Paskalev > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

Nov. 18, 2010

Re: [Pharo-users] Classes of same name

by Miguel Moquillon

Hi, I'm an experienced Java developer and I code in Smalltalk in my spare time. I'm used to using namespaces to structure my code with Java and the lacking of it in Smalltalk was never a problem for me. By my exprience, I don't think namespace support is necessary or a good think. The lacking of namespace support forces developers to think (and thus to name) their class in a more strongly way: a class name should vehicle the concrete (technical or business) concept it represents and simple name should be avoided. Event the most general concepts depend upon the context in which they are used, so their name should be prefixed by a name or keyword that identifies this context. This is just my humble opinion. Mig Le 18/11/2010 05:43, Miguel CobÃ¡ a Ã©crit : > El miÃ©, 17-11-2010 a las 20:12 -0800, Jeff Gray escribiÃ³: >> Sorry for the noob questions... >> >> What do you do if you want to import 2 discreet packages into your image and >> each contains a class of the same name? > As Squeak/Pharo haven't namespaces, you should modify some of them to > other name so that they don't clash. Either rename the class to > something different of add a prefix to one of them. This is the reason > why many packages start by choosing a prefix (2 or 3 chars) that are > used in all the classes of the packages: > > W* for Seaside > Ma* for Magma classes > > etc. > > If you have a .st file with the source code of one of them then open it > in a good text editor and add a prefix to all the classes. > Or load one package in an image, refactor the classes to a new prefix > and then load the second package. > > You can also explore the namespaces implementation that was developed in > the last google summer of code. A presentations and a screencast was > available. Search the archives for them. > > Cheers

Nov. 18, 2010

Re: [Pharo-users] Classes of same name

by Miguel CobÃ¡

El miÃ©, 17-11-2010 a las 20:12 -0800, Jeff Gray escribiÃ³: > Sorry for the noob questions... > > What do you do if you want to import 2 discreet packages into your image and > each contains a class of the same name? As Squeak/Pharo haven't namespaces, you should modify some of them to other name so that they don't clash. Either rename the class to something different of add a prefix to one of them. This is the reason why many packages start by choosing a prefix (2 or 3 chars) that are used in all the classes of the packages: W* for Seaside Ma* for Magma classes etc. If you have a .st file with the source code of one of them then open it in a good text editor and add a prefix to all the classes. Or load one package in an image, refactor the classes to a new prefix and then load the second package. You can also explore the namespaces implementation that was developed in the last google summer of code. A presentations and a screencast was available. Search the archives for them. Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Nov. 18, 2010