December 2015 - Pharo-users

PharoJVM

by Richard Eng

According to TIOBE, which is hardly a reliable metric, this month Java and Python are enjoying a massive upswing in popularity. In fact, TIOBE will most likely name Java *Programming Language of the Year* for 2015. (Both languages have been on an upward trajectory all year.) It's not hard to understand why Java's popularity is improving. Android programming is becoming more important, as the platform has begun to exceed iOS in terms of user experience with the advent of Lollipop and Marshmallow. Then there's the rise of the "Internet of Things," where Java seems to be well-suited. (I'm not sure what explains Python's bump in popularity, though. Maybe there's an increasing appetite for languages that are easy to learn. A clean, simple syntax is very, very important!) I think, more than ever, we need to have Smalltalk on the JVM. Java cannot be allowed to hog the limelight of IT. I was pinning my hopes on Redline, but I'm not sanguine about its future progress. Rather than waste time with PharoJS, wouldn't it be more prudent to focus on putting Pharo on the JVM?

Dec. 11, 2015

a little poll on the importance of architecture

by Tudor Girba

Hi, I created another little poll about the importance of architecture. If you have a Twitter account, feel free to participate: https://twitter.com/girba/status/675330047608299521 Cheers, Doru -- www.tudorgirba.com "Things happen when they happen, not when you talk about them happening."

Dec. 11, 2015

Re: [Pharo-users] seeking your tutorials

by Markus Schlager

Hi Martin, Some material (in German) I use at school (10th Grade, Gymnasium). The Prof-Stef-Tutorial is about pong, developed with pharo 1.3, I guess, but changed a little for pharo 3.0. http://www.gymnasium-untergriesbach.de/system/files/oeffentlich/unterrichts… contains an older Squeak-related tutorial of mine and a "Taxi"-Tutorial I did with Java first (I had to use Java) and later with pharo to have a comparison. A short handout I give to my pupils: http://www.gymnasium-untergriesbach.de/system/files/oeffentlich/unterrichts… There's also a similar Java-Werkzeugkiste on this website covering the same stuff but significantly longer Markus

Dec. 10, 2015

Re: [Pharo-users] seeking your tutorials

by stepharo

For when do you need that? I have the magritte tutorial and we are writing a web tutorial covering Mongo and Seaside. stef Le 9/12/15 10:51, Martin BÃ¤hr a Ã©crit : > hi, > > i again have the privilege to be part of Google Code-In with FOSSASIA. > as last year i am submitting tasks to motivate students to learn smalltalk. > > last year we had great fun working through the tutorials for various > web-frameworks, and this year i want to expand that to any pharo smalltalk > related tutorial. if you have, or know of, any tutorial that can reasonably be > handled by say, someone who read the first 3 chapters in PbE, please send me a link. > > the tutorial should be detailed, but doesn't need to be perfect. if there are > bugs in it, then the students will submit bugreports instead of completing the > tutorial, or they will ask you for help to explain something better. > > if you have a tutorial, here is your chance to get it tested. > > or use this as an opportunity to write a tutorial. > > > more advanced tutorials are also possible, then we just need to find an > easier tutorial that students can do first, before tackling yours. > > > i start students off with reading the first 3 chapters of PbE, and then nudge > them towards any other tutorials that i can find. > > > greetings, martin. >

Dec. 10, 2015

Quantum computers and Pharo

by Dimitris Chloupis

Still far fetched reality for the average pharo coder but Quantum computers are a reality non the less for the supercomputer world. http://9to5google.com/2015/12/08/google-says-it-has-now-proven-that-d-waves… With a claim that is 100.000.000 time faster than the average supercomputer, its hard to compute the potential of Pharo in such a computer. Quite a quantum leap for imagination :) http://arstechnica.com/science/2015/09/d-wave-unveils-new-quantum-computing… http://www.dwavesys.com/blog/2015/08/announcing-d-wave-2x-quantum-computer http://www.dwavesys.com/d-wave-two-system http://www.gizmag.com/silicon-quantum-computer/39711/

Dec. 10, 2015

Re: [Pharo-users] #storeOn: question

by Tudor Girba

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. 9, 2015

Re: [Pharo-users] #storeOn: question

by Tudor Girba

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."

Dec. 9, 2015

Re: [Pharo-users] #storeOn: question

by Tudor Girba

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 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."

Dec. 9, 2015

Re: [Pharo-users] When a metaclass is initialised by the system ?

by Thierry Goubier

Le 09/12/2015 11:22, stepharo a Ã©crit : > It would be good to add a preLoad and postLoad hook in the Manifest +1 Thierry > Stef > > Le 8/12/15 16:53, Christophe Demarey a Ã©crit : >> yes, we miss a package initialize method ... >> >> Le 8 dÃ©c. 2015 Ã 16:35, Mariano Martinez Peck a Ã©crit : >> >>> Dimitris, >>> >>> Relying in class side initialize is not very cool. Mostly, because >>> it's hard to know EXACTLY when Monticello will send it. For sure it's >>> the first time you load that class. But then it could be if such >>> method changes again. But maybe too if you clear some Monticello >>> caches... >>> Also, you may have dependencies (of order execution) with other class >>> side initialize. So...another approaches you can take (depending on >>> your needs) is lazy class var getters with ifNil: or if you have a >>> ConfigurationOfYourApp, you can define #postLoadDoIts in which you >>> can perform the whole initialization of your app. Or ...from the >>> #postLoadDoIts simply delegate to a class MyAppInitialize. >>> >>> I do a bit of all of them hahaha. >>> >>> Cheers, >>> >>> On Mon, Dec 7, 2015 at 9:11 PM, Dimitris Chloupis >>> <<mailto:kilon.alios@gmail.com>kilon.alios(a)gmail.com> wrote: >>> >>> ok that means I cannot rely on it and I will have to initialize >>> my class variables in specific methods. No problem, ifNil here I >>> come :) >>> >>> On Tue, Dec 8, 2015 at 12:24 AM Sven Van Caekenberghe >>> <<mailto:sven@stfx.eu>sven(a)stfx.eu> wrote: >>> >>> Hi Dimitris, >>> >>> > On 07 Dec 2015, at 23:12, Dimitris Chloupis >>> <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >>> > >>> > I have read that a metaclass (class side of the class) is >>> initialised when its loaded to the image by monticello, Are >>> there any other cases when the initialize method of the the >>> metaclass is being called ? >>> >>> Correct: a class #initialize is called when its code is >>> loaded, but only if it is not yet present or different in >>> source code from what is already present (this last point >>> will bite you one day ;-). >>> >>> Else, the #initialize should be called manually (for example >>> to reload some caches, or reset some system state). This >>> sometimes happens in #postLoads or install scripts. >>> >>> I am not aware of any automatic invocations. >>> >>> Sven >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> >> >

Dec. 9, 2015

Online coding playgrounds

by phil＠highoctane.be

I have been coming across quite a bunch of online coding tools lately. e.g. http://www.codeskulptor.org/#demos-starwars.py Would be nice to have something like that in our community. Phil

Dec. 9, 2015