- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 2.0] #20433

by Esteban Lorenzano

yeah, is broken... I'm reverting the change On Dec 12, 2012, at 1:50 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Well :-) then what issues because it seem that it broke Pharo Kernel 2.0 Seaside job: > > https://ci.inria.fr/pharo/job/Pharo%20Kernel%202.0%20Seaside/45/console > > -- Pavel > > On Wed, Dec 12, 2012 at 1:40 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > oops! > my mistake... is not that issue who is integrated > > (that happens when you just copy and paste without looking :P) > > On Dec 12, 2012, at 1:36 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> Why so many dirty packages? It seems that there are more changes than only this one issue. >> >> -- Pavel >> >> On Wed, Dec 12, 2012 at 1:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> 20433 >> ----- >> >> Issue 7062: Package extensions not present in the package >> http://code.google.com/p/pharo/issues/detail?id=7062 >> >> Diff information: >> http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1001.diff >> http://ss3.gemstone.com/ss/Pharo20/Text-EstebanLorenzano.44.diff >> http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.757.diff >> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1304.diff >> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.733.diff >> http://ss3.gemstone.com/ss/Pharo20/KeyChain-EstebanLorenzano.21.diff >> >> >> > >

Dec. 12, 2012

Re: [Pharo-project] [update 2.0] #20433

by Pavel Krivanek

Well :-) then what issues because it seem that it broke Pharo Kernel 2.0 Seaside job: https://ci.inria.fr/pharo/job/Pharo%20Kernel%202.0%20Seaside/45/console -- Pavel On Wed, Dec 12, 2012 at 1:40 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > oops! > my mistake... is not that issue who is integrated > > (that happens when you just copy and paste without looking :P) > > On Dec 12, 2012, at 1:36 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > Why so many dirty packages? It seems that there are more changes than only > this one issue. > > -- Pavel > > On Wed, Dec 12, 2012 at 1:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> 20433 >> ----- >> >> Issue 7062: Package extensions not present in the package >> http://code.google.com/p/pharo/issues/detail?id=7062 >> >> Diff information: >> http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1001.diff >> http://ss3.gemstone.com/ss/Pharo20/Text-EstebanLorenzano.44.diff >> >> http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.757.diff >> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1304.diff >> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.733.diff >> http://ss3.gemstone.com/ss/Pharo20/KeyChain-EstebanLorenzano.21.diff >> >> >> > >

Dec. 12, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 500 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Dec. 12, 2012

Re: [Pharo-project] [update 2.0] #20433

by Esteban Lorenzano

oops! my mistake... is not that issue who is integrated (that happens when you just copy and paste without looking :P) On Dec 12, 2012, at 1:36 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Why so many dirty packages? It seems that there are more changes than only this one issue. > > -- Pavel > > On Wed, Dec 12, 2012 at 1:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 20433 > ----- > > Issue 7062: Package extensions not present in the package > http://code.google.com/p/pharo/issues/detail?id=7062 > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1001.diff > http://ss3.gemstone.com/ss/Pharo20/Text-EstebanLorenzano.44.diff > http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.757.diff > http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1304.diff > http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.733.diff > http://ss3.gemstone.com/ss/Pharo20/KeyChain-EstebanLorenzano.21.diff > > >

Dec. 12, 2012

Re: [Pharo-project] [update 2.0] #20433

by Pavel Krivanek

Why so many dirty packages? It seems that there are more changes than only this one issue. -- Pavel On Wed, Dec 12, 2012 at 1:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > 20433 > ----- > > Issue 7062: Package extensions not present in the package > http://code.google.com/p/pharo/issues/detail?id=7062 > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1001.diff > http://ss3.gemstone.com/ss/Pharo20/Text-EstebanLorenzano.44.diff > http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.757.diff > http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1304.diff > http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.733.diff > http://ss3.gemstone.com/ss/Pharo20/KeyChain-EstebanLorenzano.21.diff > > >

Dec. 12, 2012

[Pharo-project] [update 2.0] #20433

by Esteban Lorenzano

20433 ----- Issue 7062: Package extensions not present in the package http://code.google.com/p/pharo/issues/detail?id=7062 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-EstebanLorenzano.1001.diff http://ss3.gemstone.com/ss/Pharo20/Text-EstebanLorenzano.44.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.757.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1304.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.733.diff http://ss3.gemstone.com/ss/Pharo20/KeyChain-EstebanLorenzano.21.diff

Dec. 12, 2012

Re: [Pharo-project] Nautilus and grey out text

by dimitris chloupis

Noted and subscribed will ask nooby questions there from there on in combination with stackoverflow. Be prepared to be bombared by questions , raise your shields :D The more I discover about pharo (and smalltalk in general) the more I believe that pharo is the right choice for my project Ephestos. For example visual coding wise(an area that I want to focus on)Â i found thanks to PharoCasts Roassal http://www.pharocasts.com/2012/09/roassal.html?utm_source=BP_recent and some cool thing one can do with morphs and physics http://www.pharocasts.com/2012/01/morphic-and-physics.html?utm_source=BP_re… and I am especially interest in nautilus, glamour, ring, lumiere and all these new things for me that feels like an early christmas present.Â But yes definetly will ask those questions in the users mailing list after i read the documentation. ________________________________ From: Sven Van Caekenberghe <sven(a)stfx.eu> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> Sent: Wednesday, 12 December 2012, 12:52 Subject: Re: [Pharo-project] Nautilus and grey out text On 12 Dec 2012, at 11:20, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > ok I understand now thank you all for the clarifications. > Very exciting and powerful stuff, the more I learn about pharo and smalltalk the more I love it. Yes, Dimitris, that is the idea. But you have been warned: once you get infected it is hard to go back ;-) One other thing: there is a Pharo-Users mailing list as well, it has less traffic, but the idea is that conversations like the one in this thread (how do I do this or that ? what does this or that mean ?) are better held there. http://www.pharo-project.org/community Keep on asking questions ! > From: Esteban Lorenzano <estebanlm(a)gmail.com> > To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> > Sent: Wednesday, 12 December 2012, 12:15 > Subject: Re: [Pharo-project] Nautilus and grey out text > > No, just a method added to a class, and categorized with a special name: *NameOfThePackageWhereItBelongs > > Esteban > > On Dec 12, 2012, at 11:11 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > >> Oh I see, very clever, are those methods traits ? >> >> From: Pavel Krivanek <pavel.krivanek(a)gmail.com> >> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >> Sent: Wednesday, 12 December 2012, 11:48 >> Subject: Re: [Pharo-project] Nautilus and grey out text >> >> If you have got a package named MyPackage then if some class that is not part of this package has got some methods in categories named like *MyPackage(-Something) (star, package name, optional category) then this methods are bundled together with MyPackage. >> >> -- Pavel >> >> On Wed, Dec 12, 2012 at 10:38 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> thanks added to my list of things to study :) >> >> From: Sven Van Caekenberghe <sven(a)stfx.eu> >> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >> Sent: Wednesday, 12 December 2012, 11:33 >> >> Subject: Re: [Pharo-project] Nautilus and grey out text >> >> >> On 12 Dec 2012, at 10:25, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> >> > Thanks for the reply , by "extension" you mean inheritance ? Package A class subclasses package B class ? >> >> No, it is extension with respect to Monticello/RPackage packaging. >> >> > From: Pavel Krivanek <pavel.krivanek(a)gmail.com> >> > To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >> > Sent: Wednesday, 12 December 2012, 11:19 >> > Subject: Re: [Pharo-project] Nautilus and grey out text >> > >> > If a package A adds an exteinson to a class from different package B then the extended class from package B is grayed out and all methods that are not part of the package A too. >> > >> > -- Pavel >> > >> > On Wed, Dec 12, 2012 at 10:03 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> > I went through the Nautilus pdf and it seems to explains most of the thing but the grey out text. Any idea why some classess and methods are grey out ? >> > >> > By the way congratulation to Nautilus author and all people contributing to it , it certainly looksÂ like a big improvement over the classic system browser. >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> >> >> >> >> > > > > > -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 12, 2012

[Pharo-project] Pharo Job Posting on Twitter

by Marcus Denker

There is a job posting for Seaside and Pharo on Twitter: Want to #code #Smalltalk with #Pharo@PharoProject and #Seaside @seaside_st at an amazing company? Contact me!#ImTheEmployerNotARecruiter https://twitter.com/lhazlewood/status/277239669194895360

Dec. 12, 2012

Re: [Pharo-project] WebSockets and Session

by Sven Van Caekenberghe

Hi Norbert, (I am CCing the mailing list). On 12 Dec 2012, at 11:51, Norbert Hartl <norbert(a)hartl.name> wrote: > Hi Sven, > > I'm playing with your WebSockets stuff at the moment. I'm asking myself how I can identify a client using Websockets. There is one delegate in the ZnServer that gets called from every connection. So I guess I need to use the WebSocket object handed over to the delegate. What would be the best information to use for identification? As there is only SocketStream involved I guess it isn't easy to get the IP address of the stream. > > Any hints appreciated, > > Norbert Some answers/hints in random order: ZnServer indeed has only one delegate but a delegate is just an object implementing #handleRequest: and #value: as a synonym, you can nest them easily. ZnDefaultServerDelegate (and the alternative ZnDispatcherDelegate) can do some primitive routing. Have a look at ZnWebSocketDelegate class>>#installExamplesInServer: to see what I mean. WebSockets constitute a permanent single session connection by design. The easiest way to have some control over who opens a new connection is by relying on the standard HTTP authentication logic, IMO. ZnServer provides an easy to use (server wide) implementation through its authenticator. For example: server authenticator: (ZnBasicAuthenticator username: 'foo' password: 'secret'). Obviously, in real life the authenticator will be a bit more elaborate. But you don't have to use this mechanism, look at its simple implementation and #authenticateRequest:do:, you could easily roll your own in a custom #handleRequest: The ZnServer authenticator makes it pluggable/independent. Regarding the IP address, Zn adds a custom 'X-Zinc-Remote-Address' header to any request it reads. Given a socket stream, you get the IP address of the other side like this: socketStream socket remoteAddress HTH, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 12, 2012

Re: [Pharo-project] Nautilus and grey out text

by Sven Van Caekenberghe

On 12 Dec 2012, at 11:20, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > ok I understand now thank you all for the clarifications. > Very exciting and powerful stuff, the more I learn about pharo and smalltalk the more I love it. Yes, Dimitris, that is the idea. But you have been warned: once you get infected it is hard to go back ;-) One other thing: there is a Pharo-Users mailing list as well, it has less traffic, but the idea is that conversations like the one in this thread (how do I do this or that ? what does this or that mean ?) are better held there. http://www.pharo-project.org/community Keep on asking questions ! > From: Esteban Lorenzano <estebanlm(a)gmail.com> > To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> > Sent: Wednesday, 12 December 2012, 12:15 > Subject: Re: [Pharo-project] Nautilus and grey out text > > No, just a method added to a class, and categorized with a special name: *NameOfThePackageWhereItBelongs > > Esteban > > On Dec 12, 2012, at 11:11 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > >> Oh I see, very clever, are those methods traits ? >> >> From: Pavel Krivanek <pavel.krivanek(a)gmail.com> >> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >> Sent: Wednesday, 12 December 2012, 11:48 >> Subject: Re: [Pharo-project] Nautilus and grey out text >> >> If you have got a package named MyPackage then if some class that is not part of this package has got some methods in categories named like *MyPackage(-Something) (star, package name, optional category) then this methods are bundled together with MyPackage. >> >> -- Pavel >> >> On Wed, Dec 12, 2012 at 10:38 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> thanks added to my list of things to study :) >> >> From: Sven Van Caekenberghe <sven(a)stfx.eu> >> To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >> Sent: Wednesday, 12 December 2012, 11:33 >> >> Subject: Re: [Pharo-project] Nautilus and grey out text >> >> >> On 12 Dec 2012, at 10:25, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> >> > Thanks for the reply , by "extension" you mean inheritance ? Package A class subclasses package B class ? >> >> No, it is extension with respect to Monticello/RPackage packaging. >> >> > From: Pavel Krivanek <pavel.krivanek(a)gmail.com> >> > To: Pharo-project(a)lists.gforge.inria.fr; dimitris chloupis <thekilon(a)yahoo.co.uk> >> > Sent: Wednesday, 12 December 2012, 11:19 >> > Subject: Re: [Pharo-project] Nautilus and grey out text >> > >> > If a package A adds an exteinson to a class from different package B then the extended class from package B is grayed out and all methods that are not part of the package A too. >> > >> > -- Pavel >> > >> > On Wed, Dec 12, 2012 at 10:03 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> > I went through the Nautilus pdf and it seems to explains most of the thing but the grey out text. Any idea why some classess and methods are grey out ? >> > >> > By the way congratulation to Nautilus author and all people contributing to it , it certainly looks like a big improvement over the classic system browser. >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> >> >> >> >> > > > > > -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 12, 2012