June 2014 - Pharo-dev - lists.pharo.org

Refactorings - Push down several instVars

by phil＠highoctane.be

It is only possible to do this one variable at a time... How to do a set of vars all at once? Same story for quite a couple of refactorings... Thanks in advance! Phil

June 26, 2014

Re: [Pharo-dev] about ~=

by Max Leske

On 26.06.2014, at 10:15, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Hi, > > I would like to make a suggestion that may lead to a long debate but let's go: What do you think about deprecating ~= and replace it with != for example? > Why? In mathematics the symbol ~ is used for equivalence. To me (and I think any newcomer to Smalltalk) the first guess of the meaning of ~= is equivalent to => missed. The meaning is totally different: "Answer whether the receiver and the argument do not represent the same object.â +1 But then I also want to suggest #!== for negating identity. > > I never used this method because it is too confusing for me. I prefer to use (a = b) not or (a = b) ifFalse:. > So, the discussion is open ... > > Christophe

June 26, 2014

Re: [Pharo-dev] Spec Button Shortcut Indication

by Benjamin

On 25 Jun 2014, at 20:40, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Benjamin Van Ryseghem (Pharo) wrote >> Itâs intentional that the C is underlined. > > Cool!! One of the few good ideas from Windozeâ¦ Now we have to remove it! ;) Ben > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spec-Button-Shortcut-Indication-tp4764414p4764778.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 26, 2014

about ~=

by Christophe Demarey

Hi, I would like to make a suggestion that may lead to a long debate but let's go: What do you think about deprecating ~= and replace it with != for example? Why? In mathematics the symbol ~ is used for equivalence. To me (and I think any newcomer to Smalltalk) the first guess of the meaning of ~= is equivalent to => missed. The meaning is totally different: "Answer whether the receiver and the argument do not represent the same object." I never used this method because it is too confusing for me. I prefer to use (a = b) not or (a = b) ifFalse:. So, the discussion is open ... Christophe

June 26, 2014

Re: [Pharo-dev] R: [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

On 26 Jun 2014, at 09:24, Lorenzo Schiavina <lorenzo(a)edor.it> wrote: > Great job Sven, I felt young again. > > Thank you. > > Lorenzo Yeah, I am beginning to realise that being interested in historic calculators puts you in a certain age bracket ;-) I am glad you liked it. Sven

June 26, 2014

Pharo and Amber relationship

by Torsten Bergmann

Hi, as I read somewhere that Amber want to stay compatible with Pharo (at least with the core classes) I wonder how this compatibility is measured/enforced these days. Are there tools to exchange code between the two? I also wonder if what would be necessary to run Amber on Java Nashorn (a JS engine that comes with the JDK 8). Could serve as a horse to also run on JVM... Why I'm asking: I think one of our goals should be to make Pharo more widely usable to not end up as an island. If Pharo and Amber stay compatible to a certain amount Amber could open the door for Pharo to other target platforms (browser, mobile devices, other language runtimes) as JS is available nearly everywhere. Thx T.

June 26, 2014

Re: [Pharo-dev] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

On 25 Jun 2014, at 17:05, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Apparently it already got posted on YC News > > https://news.ycombinator.com/item?id=7943876 > > so it needs votes and comments to survive. Let's try again - it is hard to get up the rankings, both votes & comments help - thanks.

June 26, 2014

Re: [Pharo-dev] Nautilus memory leak/hog crashing Pharo

by Goubier Thierry

Sorry to ask then, but: would it be possible to profile a configurationOf... load with and without a Nautilus open? Time spent handling announcements should be visible, and, yes, when loading code, Browsers have to be aware the code is being changed. I spent some time optimizing that for AltBrowser, and it can very significantly increase the loading time, without counting in side effects such as over-caching (and I know Nautilus does some caching, but I'm not sure I understand why). Thierry Le 25/06/2014 20:20, phil(a)highoctane.be a Ã©crit : > Maybe due to some Annoucement being picked up by Nautilus? > > Phil > > > > On Wed, Jun 25, 2014 at 7:57 PM, Johan Brichau <johan(a)inceptive.be > <mailto:johan@inceptive.be>> wrote: > > Hi, > > It seems that when even a single Nautilus system browser is open and > you do a load (using Metacello), there is a huge amount of objects > that get created and persisted in the image. > This even leads to the point that the image crashes when I try to > load our code using a ConfigurationOf. After some time, the Pharo > process is stuck at 100%, image size is over 500MB and the entire > image becomes unresponsive, finally crashing after an hour or so. > > I have not yet found which objects or why, but I just wrestled with > this all day to find out what was going on. I first thought that > Metacello was in an infinite loop but after noticing that the image > was so large (500MB) and that it got reduced to 20% of its size > after closing the browser window, I can say that Nautilus is > gathering garbage. It is definitely not Metacello because I can > trigger the same problem doing a load via Monticello only. > > When I load the ConfigurationOf without a single browser open, it > loads 5x faster and the image size stays reasonable. > > Is this a known issue? Any thoughts on what may be causing this? > > regards! > Johan > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 26, 2014

super initialize

by Torsten Bergmann

When you create a new instance with #new automatically #initialize is sent. The default #initialize is provided in ProtoObject at the highest level of the class hierarchy (doing nothing). If you look deeper in the hierarchy you will notice that - some subclasses of Object override the #initialize method and call "super initialize" - some subclasses of Object override the #initialize method without calling "super initialize" No problem at the moment as there is no initialization done in Object or ProtoObject at the current point in time. But the question is should we care if there may be in the future? Thx T.

June 26, 2014

R: [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Lorenzo Schiavina

Great job Sven, I felt young again. Thank you. Lorenzo Da: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Per conto di Sven Van Caekenberghe Inviato: mercoledÃ¬ 25 giugno 2014 15:29 A: Pharo Development List; Any question about pharo is welcome Oggetto: [Pharo-dev] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator Hi, I have written a new, extensive, long form, introductory article about Pharo. Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator A tutorial on Pharo, test and specification based immersive programming https://medium.com/@svenvc/rediscovering-the-ux-of-the-legendary-hp-35-scien tific-pocket-calculator-d1d497ece999 It is a bit different because - it is based on a non-trivial example - it uses a backdrop story unrelated to Pharo - it uses several multimedia elements - it is published on medium.com which is a general publishing platform The appendix describes several ways you can get the code. I think building both a Spec and Seaside UI from the same specification as well as reusing functional tests in different contexts is cool. Anyway, I hope you enjoy it. Sven -- Sven Van Caekenberghe Proudly supporting Pharo <http://pharo.org> http://pharo.org <http://association.pharo.org> http://association.pharo.org <http://consortium.pharo.org> http://consortium.pharo.org

June 26, 2014