December 2015 - Pharo-users

Re: [Pharo-users] Rocket Chat - An open source alternative to Slack

by Craig Johnson

The windows client is a b***h to work with. The channel list is very long and unordered, and there's no search. Craig On 2015/12/17 08:20 AM, John Pfersich wrote: > I set up a public #pharo channel. Join it! > > Sent from my iPad > > On Dec 16, 2015, at 02:04, Dimitris Chloupis <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com>> wrote: > >> So since Slack has been so successful for our community , far more >> that IRC has been in terms of participation and useful discussions >> (at least the 2 years I have been around) >> >> it made me wonder if I could find an open source alternative to Slack >> that is at least as good as it if not better without a very different >> workflow (so we have to learn everything from zero) all the big pros >> and something that could easily interface with Pharo. >> >> Ladies and gentlemen meet Rocket Chat >> >> https://rocket.chat/ >> >> The good news about Rocket chat is that it seems to have all the pros >> of Slack like close integration with tweeter, github etc etc . It has >> clients for all OS and mobile devices. But not the big cons like the >> 10.000 messages limit ( which we have long exceeded). Its open source >> and most importantly written in javascript and we know that pharo can >> interface with javascript in many diffirent ways . >> >> Hosted on Github and deployable with open source technologies. >> >> And even its license is MIT. >> >> The reviews I have read about it are very positive. >> >> So what do you think ?

Dec. 17, 2015

Re: [Pharo-users] Adieu, abschied, addio, despedida, afscheid, farvÃ¤l, Ð¿ÑÐ¾ÑÐ°Ð»ÑÐ½ÑÐ¹ Ð¿ÑÐ¸Ð²ÐµÑ.

by Sven Van Caekenberghe

> On 17 Dec 2015, at 11:21, Richard Eng <horrido.hobbies(a)gmail.com> wrote: > > I bid farewell to everyone. Best of luck to Pharo. > > https://medium.com/@richardeng/today-is-the-first-anniversary-of-smalltalk-… > > Cheers, > Richard Thanks for trying, you took on an impossible job (to promote a programming language full on). Your last message at the bottom would seem to suggest that we might hear from you again. Maybe you can find a smaller nice within our ecosystem to work on and contribute to. Sven

Dec. 17, 2015

Re: [Pharo-users] Adieu, abschied, addio, despedida, afscheid, farvÃ¤l, Ð¿ÑÐ¾ÑÐ°Ð»ÑÐ½ÑÐ¹ Ð¿ÑÐ¸Ð²ÐµÑ.

by Esteban Lorenzano

thanks for you efforts. > On 17 Dec 2015, at 11:21, Richard Eng <horrido.hobbies(a)gmail.com> wrote: > > I bid farewell to everyone. Best of luck to Pharo. > > https://medium.com/@richardeng/today-is-the-first-anniversary-of-smalltalk-… <https://medium.com/@richardeng/today-is-the-first-anniversary-of-smalltalk-…> > > Cheers, > Richard

Dec. 17, 2015

What Strides In Pharo?

by horrido

Perhaps one of you can respond to this guy *at Reddit*. I'm not up with all the Pharo developments. He has used Pharo and he seems to be most displeased with it... https://www.reddit.com/r/programming/comments/3wv7ik/who_uses_smalltalk/cy2… <https://www.reddit.com/r/programming/comments/3wv7ik/who_uses_smalltalk/cy2…> "What strides? How about you write an article explaining that? I've used Pharo extensively and the biggest language-level change that has come about is slots. That's hardly a huge revolutionary change (it's also an exceptionally complex model for what it is!). The point releases of Python or Ruby, see bigger changes than this! [0] Now the Pharo guys have done a fantastic job cleaning up the image. But there's a long long way to go there, and there's the tiny fact that no available Smalltalk system bootstraps! Until that happens, and Smalltalk has a reasonable deployment model (writing scripts to strip objects from the image and crossing your fingers doesn't count!), it's hard to take even this clean up effort seriously. [0] The biggest changes in Smalltalk since Smalltalk 80 have been syntax for dynamic arrays, which nobody uses, because it's non-standard; Traits, which nobody uses, because it's non-standard, and the vendor specific syntax for dealing with packages. You can keep saying it until you're blue in the face but in comparison to just about every other language, these are not major changes! This is no "modernizing." -- View this message in context: http://forum.world.st/What-Strides-In-Pharo-tp4867485.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 17, 2015

Adieu, abschied, addio, despedida, afscheid, farvÃ¤l, Ð¿ÑÐ¾ÑÐ°Ð»ÑÐ½ÑÐ¹ Ð¿ÑÐ¸Ð²ÐµÑ.

by Richard Eng

I bid farewell to everyone. Best of luck to Pharo. https://medium.com/@richardeng/today-is-the-first-anniversary-of-smalltalk-… Cheers, Richard

Dec. 17, 2015

Re: [Pharo-users] Someone broke startup scripts on ubuntu

by Dimitris Chloupis

And the problem has been fixed, now my startup works fine. Thank you Esteban , you are awesome :) On Tue, Dec 15, 2015 at 4:06 PM Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > No problemo Esteban , take your time. We just reporting :) > > On Tue, Dec 15, 2015 at 3:41 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> yes, you are using alpha, which means pharo 5.0, which means spur, which >> means it is still now working :) >> >> Esteban >> >> On 15 Dec 2015, at 11:14, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >> I get my pharo on ubuntu 14 64 bit with >> >> cd Ephestos; wget -O- get.pharo.org/alpha+vmLatest | bash >> >> looks like startup scripts on ubuntu has been broken >> >> StartupPreferencesLoader preferencesGeneralFolder . >> >> returns nil, looking inside the method's source if I do >> >> FileLocator preferences asFileReference >> >> gives me a nice error Cant find the requested origin >> >> trying with >> >> cd Ephestos; wget -O- get.pharo.org/alpha+vm | bash >> >> for getting the stable default vm, same problem, so I assume this is an >> image problem >> >> here is the stack >> >> UnixResolver(PlatformResolver)>>cantFindOriginError [ self >> cantFindOriginError ] in >> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed: in Block: [ >> self cantFindOriginError ] [ ^ aBlock value ] in >> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: in Block: >> [ ^ aBlock value ] BlockClosure>>cull: Context>>evaluateSignal: >> Context>>handleSignal: Error(Exception)>>signal Error(Exception)>>signal: >> Error class(Exception class)>>signal: FFICallout>>loaderForArgNamed: >> FFICallout>>loaderForArgNamed:indirectIndex: >> FFICallout>>argName:indirectIndex:type:ptrArity: >> FFIFunctionParser>>parseArgument FFIFunctionParser>>parseArguments >> FFIFunctionParser>>parseNamedFunction: >> FFICalloutMethodBuilder>>parseSignature: FFICalloutMethodBuilder>>generate >> FFICalloutMethodBuilder>>build: FFICalloutAPI>>function:module: >> UnixEnvironment(Object)>>ffiCall:module: >> UnixEnvironment(OSEnvironment)>>getEnv: >> UnixEnvironment(OSEnvironment)>>at:ifAbsent: [ Smalltalk os environment at: >> aString ifAbsent: [ nil ] ] in >> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: in Block: >> [ Smalltalk os environment at: aString ifAbsent: [...etc... >> BlockClosure>>on:do: >> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: >> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed: >> UnixResolver>>home [ self home / '.config' ] in UnixResolver>>preferences >> in Block: [ self home / '.config' ] [ ^ aBlock value ] in >> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: in Block: >> [ ^ aBlock value ] BlockClosure>>cull: >> >> >>

Dec. 17, 2015

Re: [Pharo-users] Rocket Chat - An open source alternative to Slack

by Dimitris Chloupis

Where ? On Thu, 17 Dec 2015 at 08:21, John Pfersich <jpfersich(a)gmail.com> wrote: > I set up a public #pharo channel. Join it! > > Sent from my iPad > > On Dec 16, 2015, at 02:04, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > So since Slack has been so successful for our community , far more that > IRC has been in terms of participation and useful discussions (at least the > 2 years I have been around) > > it made me wonder if I could find an open source alternative to Slack that > is at least as good as it if not better without a very different workflow > (so we have to learn everything from zero) all the big pros and something > that could easily interface with Pharo. > > Ladies and gentlemen meet Rocket Chat > > https://rocket.chat/ > > The good news about Rocket chat is that it seems to have all the pros of > Slack like close integration with tweeter, github etc etc . It has clients > for all OS and mobile devices. But not the big cons like the 10.000 > messages limit ( which we have long exceeded). Its open source and most > importantly written in javascript and we know that pharo can interface with > javascript in many diffirent ways . > > Hosted on Github and deployable with open source technologies. > > And even its license is MIT. > > The reviews I have read about it are very positive. > > So what do you think ? > >

Dec. 17, 2015

Re: [Pharo-users] Rocket Chat - An open source alternative to Slack

by John Pfersich

I set up a public #pharo channel. Join it! Sent from my iPad > On Dec 16, 2015, at 02:04, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > So since Slack has been so successful for our community , far more that IRC has been in terms of participation and useful discussions (at least the 2 years I have been around) > > it made me wonder if I could find an open source alternative to Slack that is at least as good as it if not better without a very different workflow (so we have to learn everything from zero) all the big pros and something that could easily interface with Pharo. > > Ladies and gentlemen meet Rocket Chat > > https://rocket.chat/ > > The good news about Rocket chat is that it seems to have all the pros of Slack like close integration with tweeter, github etc etc . It has clients for all OS and mobile devices. But not the big cons like the 10.000 messages limit ( which we have long exceeded). Its open source and most importantly written in javascript and we know that pharo can interface with javascript in many diffirent ways . > > Hosted on Github and deployable with open source technologies. > > And even its license is MIT. > > The reviews I have read about it are very positive. > > So what do you think ?

Dec. 17, 2015

Re: [Pharo-users] #storeOn: question

by Tudor Girba

Hi, I wanted to have an easy way to distinguish between a class that ships with Pharo and another class that is built on top. Unfortunately, I did not find a good enough heuristic (I used to rely on the repository of the package where the class is defined as being the Pharo one), so this was not added until we find a different solution. This is useful in several situations. The one I am in very often is to use extra tools that are in Moose to analyze Pharo. This was the case below where we needed to get the list of the storeOn: senders more accurately. Cheers, Doru > On Dec 16, 2015, at 10:41 PM, stepharo <stepharo(a)free.fr> wrote: > > hi doru > > what is isPharoClass? > Why do you need it? > > Stef > > Le 9/12/15 21:49, Tudor Girba a Ã©crit : >> I created an issue with a slice: >> https://pharo.fogbugz.com/f/cases/17224/TBehavior-isPharo >> >> Cheers, >> Doru >> >> >>> On Dec 9, 2015, at 3:33 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi again, >>> >>>> On Dec 9, 2015, at 3:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> Thanks for the question. I am at a conference, and I just took this problem to explain someone what code querying can mean :). >>>> >>>> Here is the result: >>>> http://ws.stfx.eu/CCSNJVWX3JKS >>>> >>> I just realized that isPharoClass only exists in my image for the moment :) >>> >>> Doru >>> >>> >>>> <storeOn.png> >>>> >>>> I think this is how we should document our communication because now we have the tools. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>>> On Dec 3, 2015, at 7:00 AM, Werner Kassens <wkassens(a)libello.com> wrote: >>>>> >>>>> Hi Stephane, >>>>> there are 89 senders of #storeOn: minus around 30 implementations of #storeOn: minus around 10 tests, also things like the PharoChangesCondenser use it. then there are 26 senders of #storeString (essentially the same functionality implemented via #storeOn:, but returns a string) eg used by the StartupPreferencesLoader. and there are several senders of #store: that are not implementations of #storeOn:. iow deprecating #storeOn: looks a bit complicated to me and is obviously way above my head. >>>>> werner >>>>> >>>>> On 11/30/2015 09:42 PM, stepharo wrote: >>>>>> It would be good to check who is using that and evaluate if we can >>>>>> remove it. >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing should have the right to be different." >>>> >>>> >>>> >>> -- >>> www.tudorgirba.com >>> >>> "One cannot do more than one can do." >> -- >> www.tudorgirba.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> >> > > -- www.tudorgirba.com www.feenk.com "It's not what we do that matters most, it's how we do it."

Dec. 16, 2015

Re: [Pharo-users] #storeOn: question

by stepharo

hi doru what is isPharoClass? Why do you need it? Stef Le 9/12/15 21:49, Tudor Girba a Ã©crit : > I created an issue with a slice: > https://pharo.fogbugz.com/f/cases/17224/TBehavior-isPharo > > Cheers, > Doru > > >> On Dec 9, 2015, at 3:33 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi again, >> >>> On Dec 9, 2015, at 3:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Thanks for the question. I am at a conference, and I just took this problem to explain someone what code querying can mean :). >>> >>> Here is the result: >>> http://ws.stfx.eu/CCSNJVWX3JKS >>> >> I just realized that isPharoClass only exists in my image for the moment :) >> >> Doru >> >> >>> <storeOn.png> >>> >>> I think this is how we should document our communication because now we have the tools. >>> >>> Cheers, >>> Doru >>> >>> >>>> On Dec 3, 2015, at 7:00 AM, Werner Kassens <wkassens(a)libello.com> wrote: >>>> >>>> Hi Stephane, >>>> there are 89 senders of #storeOn: minus around 30 implementations of #storeOn: minus around 10 tests, also things like the PharoChangesCondenser use it. then there are 26 senders of #storeString (essentially the same functionality implemented via #storeOn:, but returns a string) eg used by the StartupPreferencesLoader. and there are several senders of #store: that are not implementations of #storeOn:. iow deprecating #storeOn: looks a bit complicated to me and is obviously way above my head. >>>> werner >>>> >>>> On 11/30/2015 09:42 PM, stepharo wrote: >>>>> It would be good to check who is using that and evaluate if we can >>>>> remove it. >>> -- >>> www.tudorgirba.com >>> >>> "Every thing should have the right to be different." >>> >>> >>> >> -- >> www.tudorgirba.com >> >> "One cannot do more than one can do." > -- > www.tudorgirba.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > >

Dec. 16, 2015