December 2015 - Pharo-users

[ ANN ] Pharo Days 2016

by Sven Van Caekenberghe

Dear fellow Pharoers, Mark your calendars: on Thursday March 31 & Friday April 1 we are organising the Pharo Days 2016. This year we moved the location to Namur, Belgium, just a bit south of Brussels, at the very beautiful location of the âCercle de Wallonieâ overlooking the river Meuse. Weâll update the following page moving forward. https://medium.com/concerning-pharo/pharo-days-2016-c52fe4d7caf You can ask questions on any of the Pharo mailing lists or you can email the Pharo Board. Let's make this another success, together ! We hope to see as many of you as possible.

Dec. 9, 2015

Re: [Pharo-users] code coverage tools

by Damien Cassou

Peter Uhnak <i.uhnak(a)gmail.com> writes: > do we have any code coverage tools? in the test runner, press "Run Coverage". This is old stuff that worked, got broken at some point, and seems to be back (at least in Pharo 5). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Dec. 9, 2015

Re: [Pharo-users] code coverage tools

by Alexandre Bergel

Hi! Hapao works great. I am using it almost everyday. In the Catalog, look for Spy2 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Dec 9, 2015, at 7:50 AM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On 12/09, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >> I came across this: >> >> http://objectprofile.com/Hapao.html <http://objectprofile.com/Hapao.html> > > This looks great! > > Thanks >> >> but never used or even digged into. >> >> Phil >> >> On Wed, Dec 9, 2015 at 9:25 AM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >>> Hi, >>> >>> do we have any code coverage tools? >>> >>> -- >>> Peter >>> >>> >>> > > -- > Peter

Dec. 9, 2015

Re: [Pharo-users] code coverage tools

by Peter Uhnak

On 12/09, phil(a)highoctane.be wrote: > I came across this: > > http://objectprofile.com/Hapao.html This looks great! Thanks > > but never used or even digged into. > > Phil > > On Wed, Dec 9, 2015 at 9:25 AM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > Hi, > > > > do we have any code coverage tools? > > > > -- > > Peter > > > > > > -- Peter

Dec. 9, 2015

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

by stepharo

It would be good to add a preLoad and postLoad hook in the Manifest 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 >> <kilon.alios(a)gmail.com <mailto:kilon.alios@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 >> <sven(a)stfx.eu <mailto:sven@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

Re: [Pharo-users] Roassal: Multiple Nesting

by Leonel Merino

Nice, that worked perfect. Thanks Alex ! Sure, the example fits better for Mondrian, however my code is more complex. Best regards, Leonel Leonel Merino PhD student University of Bern +41 78 405 43 38 merino(a)inf.unibe.ch On Tue, Dec 8, 2015 at 10:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Leonel, > > Currently, a roassal element is not composed. So, this means you need to > all the elements to the view, and then define the nesting. > > From your script, you do not gain much by directly talking to Roassal. You > should better use a builder, such as Mondrian. > I think your script can be: > -=-=-=-=-=-=-=-= > packages := { 'Roassal2GT' . 'Trachel' } collect: [ :name | > RPackageOrganizer default packageNamed: name ]. > b := RTMondrian new. > b nodes: packages forEach: [ :pak | > b nodes: pak classes forEach: [ :cls | > b nodes: cls methods. > b layout grid ]. > b layout grid ]. > b > -=-=-=-=-=-=-=-= > > Here is a version of what you try to do using plain Roassal: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > "Packages to visualize" > packages := { 'Roassal2GT' . 'Trachel' } collect: [ :name | > RPackageOrganizer default packageNamed: name ]. > > palette := RTPalette c10. > > v := RTView new. > > packagesElements := (RTBox new color: palette first) elementsOn: packages. > v addAll: packagesElements. > packagesElements @ RTPopup. > > packagesElements do: [ :pakEl | > clsElements := (RTBox new color: palette second) elementsOn: pakEl model > classes. > v addAll: clsElements. > > clsElements do: [ :clsEl | > mtdElements := (RTBox new color: palette third) elementsOn: clsEl model > methods. > v addAll: mtdElements. > mtdElements @ RTPopup. > RTGridLayout on: mtdElements. > RTNest new > on: clsEl nest: mtdElements. > ]. > RTGridLayout on: clsElements. > RTNest new > on: pakEl nest: clsElements. > clsElements @ RTPopup. > ]. > RTGridLayout on: packagesElements. > v > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > With the colors: > > Cheers, > Alexandre > > On Dec 8, 2015, at 1:35 PM, Leonel Merino <merino(a)iam.unibe.ch> wrote: > > Hi all, > > I want to visualise three nested levels of a model. I am not sure if I am > doing it right, since I had to add a reference to the view to the nested > elements manually to make it work. The problem I face now is that elements > in the deepest level do not react to interactions. In the example below, > popup is only shown for the elements in the first two levels. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > v := RTView new. > es := (RTBox new > color: Color white; > borderColor: Color lightGray) > elementsOn: (Array with: RTLayout with: RTShape with: RTBuilder). > v addAll: es. > es @ RTPopup. > RTNest new > for: es > add: > [ :group :model | > elements := (RTBox new color: (Color red alpha: 0.1)) elementsOn: model > withAllSubclasses. > group addAll: elements. > elements @ RTPopup. > elements do: [ :e | e view: v ]. > RTNest new > for: elements > add: > [ :group2 :model2 | > els := (RTBox new color: Color blue) elementsOn: model2 methods. > group2 addAll: els. > els @ RTPopup. > RTTreeLayout on: els edges: edges ]. > RTGridLayout on: elements ]. > RTGridLayout on: es. > v > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Any hint would be much appreciated. > > Best regards, > Leonel > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Dec. 9, 2015

Re: [Pharo-users] code coverage tools

by phil＠highoctane.be

I came across this: http://objectprofile.com/Hapao.html but never used or even digged into. Phil On Wed, Dec 9, 2015 at 9:25 AM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi, > > do we have any code coverage tools? > > -- > Peter > > >

Dec. 9, 2015

seeking your tutorials

by Martin BÃ¤hr

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. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Dec. 9, 2015

Re: [Pharo-users] [squeak-dev] Name change: Mushroom ( was Re: evolutions of squeakelib & crypto)

by phil＠highoctane.be

Things are moving. Now the new thing is http://hortonworks.com/products/dataflow/ Pharo could indeed be embedded at various places (like in MR w/ Hadoop Streaming). It is annoying that it is 32 bits as there is a need to deploy 32 bits libs all over the cluster and that's hard to do in a skunkworks way. We run some C code on the cluster, that's working nicely. Pharo would be nice to run around as the image is reasonably featured, and is one single file, which is better than the jar hell ones get when doing Java. And when doing Scala, it is worse. At this point, Python runs took (Spark) and it is doing well for some workloads. Maybe I can arrange for a project with the client where one has to implement a workload using Pharo. That is when we'll have a Spur based system that doesn't ask for 32 bit libs. And it all runs on CentOS6.x --> making this a prime platform on Linux is key for adoption. Already said, already pushed for it, that's why there is a link on the site but that's still second grade citizenry. Not good for me to push marketing wise. As of Impala, I do not run it, we do HiveQL (cluster is all OpenSource w/ Hortonworks HDP 2.3) Phil On Wed, Dec 9, 2015 at 12:25 AM, Robert Withers <robert.w.withers(a)gmail.com> wrote: > Wait. Kafka is a part of Hadoop, now? Getting some Love! There's a good > match right there. Makes for a very good lambda architecture. They need a > meta. Hello squeak!!! Somebody just needs to build a kafka interface and a > spark callback interface. Get squeak with caching to start grinding data, > it's right there. > > You're right, Phil. Furthermore these names are personable, effective > marketing and they always have something to do with what they do. Taker > flume, sqoop, yarn or impala. I'll take the Impala, thank you. It's vintage. > > In my case, choosing Mushroom has a reasonable descriptive power when > considered in light of mobile code budding out all over the grid. It's a > cloud solution. > > Robert > > On 12/08/2015 05:10 PM, phil(a)highoctane.be wrote: > > Whoever works with Hadoop tech would find names like: > > Hadoop > Spark > Cassandra > HBase > Accumulo > Hive > Pig > Impala > Oozie > YARN > Kafka > Flume > Sqoop > ... > > Go datascience and you'll get: > > R > Shiny > Jupyter > Pandas > Bokeh > D3 > > And in JS: > > Node > Angular > Express > > descriptive names? Not at all. > > What matters is not the name, it is its description. > > And, know what, put a generic name and it will be ungooglable. > > Try with Visual Studio Code ... > > Pfah, descriptive project names... As if these were descriptive: > > Ubuntu 15.10 (Wily Werewolf) > Ubuntu 15.04 (Vivid Vervet) > Ubuntu 14.04.3 LTS (Trusty Tahr) > Ubuntu 12.04.5 LTS (Precise Pangolin) > > Oh yeah super descriptive names: > > Oracle Communications Diameter Signaling Router > > Have a clue? Enjoy, they have a bunch and renamed a few: > <https://www.oracle.com/products/oracle-a-z.html> > https://www.oracle.com/products/oracle-a-z.html > > Want to know? Pay the dues. > > Phil > > > > On Tue, Dec 8, 2015 at 10:20 PM, Robert Withers < > robert.w.withers(a)gmail.com> wrote: > >> I would need to disagree with you as inquiry is possible by description, >> rather than by name, through conversation with those who don't have to >> inquire, due to their knowledge [see Meno's Paradox...]. So, a third >> possibility exists through communal association. Do you know Kevin Bacon? >> ;-) >> >> I've used that language! >> >> On 12/08/2015 04:02 PM, EuanM wrote: >> >>> The philosophical issue behind the disutility of project names like >>> these is "Meno's Paradox" >>> >>> On 8 December 2015 at 21:01, EuanM < <euanmee(a)gmail.com> >>> euanmee(a)gmail.com> wrote: >>> >>>> "I wish people would choose descriptive names for their projects" - Todd >>>> >>>> I agree. >>>> >>>> I went looking for the current state of dbxtalk recently. It seemed >>>> to ba apackage designed for my needs - to X[-over] from a DB to >>>> [small]talk. >>>> >>>> I went there and the the page started talking about "Glorp" and >>>> "Garage". Neither are mnemonic or meaningful >>>> >>>> These projects are just the tip of the iceberg. >>>> >>>> Pharo project names have publisher-only project names. The project >>>> name equivalent of write-only computer languages, like Brain-F**k. >>>> >>>> >>>> On 7 December 2015 at 17:52, Todd Blanchard < <tblanchard(a)mac.com> >>>> tblanchard(a)mac.com> wrote: >>>> >>>>> Sigh. >>>>> >>>>> I wish people would choose descriptive names for their projects. I >>>>> went looking on Smalltalkhub for some capability and what I found are >>>>> thousands of packages with names that mean nothing and no description >>>>> entered either. If you want to make sure nobody ever uses your code you've >>>>> just taken a giant step in the right direction. But if you hope to make >>>>> something lots of people benefit from - nobody is going to look for >>>>> "mushroom" when they want crypto capabilities. >>>>> >>>>> Sorry, this has been really bugging me lately. We, as a community, do >>>>> a lousy job of making our code easy to find. >>>>> >>>>> -Todd Blanchard >>>>> >>>>> On Dec 7, 2015, at 07:38, Ben Coman <btc(a)openInWorld.com> >>>>>> <btc(a)openInWorld.com> wrote: >>>>>> >>>>>> I like it, but it seems you missed my point :) >>>>>> mushroom --> 117,000,000 is two orders of magnitude more hidden. >>>>>> Anyway, maybe I overplay its significance. >>>>>> cheers -ben >>>>>> >>>>>> On Mon, Dec 7, 2015 at 11:11 PM, Robert Withers >>>>>> <robert.w.withers(a)gmail.com> wrote: >>>>>> >>>>>>> I renamed the project to Mushroom and I also dumped the encoding >>>>>>> work to >>>>>>> focus on shutdown, optimization and serialization. Here's the wiki: >>>>>>> https://github.com/SqueakCryptographySquad/Mushroom/wiki >>>>>>> >>>>>>> thanks,Robert >>>>>>> >>>>>>> >>>>>>> On 12/06/2015 01:42 AM, Ben Coman wrote: >>>>>>> >>>>>>>> On Sun, Dec 6, 2015 at 10:42 AM, Robert Withers >>>>>>>> <robert.w.withers(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> On 12/05/2015 09:24 PM, Ben Coman wrote: >>>>>>>>> >>>>>>>>>> On Fri, Dec 4, 2015 at 11:57 PM, Robert Withers >>>>>>>>>> <robert.w.withers(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Now I think you are right on with your observation. >>>>>>>>>>> Additionally, the >>>>>>>>>>> number >>>>>>>>>>> of dialects could increase further with Fuel serialization, just >>>>>>>>>>> port >>>>>>>>>>> SecureSession and bits. >>>>>>>>>>> >>>>>>>>>>> Alright, I came up with a name and it may border on the >>>>>>>>>>> egregious ... >>>>>>>>>>> presenting ... >>>>>>>>>>> >>>>>>>>>>> "Maelstrom" >>>>>>>>>>> >>>>>>>>>> Great sounding name. However some general advice for the >>>>>>>>>> community, >>>>>>>>>> since I see a lot of great sounding project names drowned out in >>>>>>>>>> the >>>>>>>>>> noise of our web-search-centric universe. A litmus test for >>>>>>>>>> project >>>>>>>>>> naming is using google search to find which return low search >>>>>>>>>> results. >>>>>>>>>> Today, its more important to be unique than any other attribute >>>>>>>>>> of a >>>>>>>>>> name. So in general, *dictionary* english words are not the best. >>>>>>>>>> One technique is to intentionally mispell the word you like. >>>>>>>>>> Here are >>>>>>>>>> some comparative examples (note, the surrounding quotes are >>>>>>>>>> required >>>>>>>>>> to avoid google trying to be helpful and correct the spelling)... >>>>>>>>>> >>>>>>>>>> "maelstrom" --> 7,480,000 >>>>>>>>>> "maelstroom" --> 6,200 >>>>>>>>>> "maelstrum" --> 2,280 >>>>>>>>>> "maelstruum" --> 7 >>>>>>>>>> >>>>>>>>>> Lots of interesting other techniques can be found by searching on: >>>>>>>>>> techniques to generate brand names or domain names. >>>>>>>>>> >>>>>>>>>> cheers -ben >>>>>>>>>> >>>>>>>>> >>>>>>>>> I would be happy to change the names to something more unique, >>>>>>>>> though it >>>>>>>>> may >>>>>>>>> take a few. Are you suggesting "maelstruum"? >>>>>>>>> >>>>>>>>> cheers, >>>>>>>>> Robert >>>>>>>>> >>>>>>>>> >>>>>>>>> *Suggesting* yes, but the choice is yours ;) You need to own it. >>>>>>>> >>>>>>>> I think maelstruum is certainly memorable with the double "u", but >>>>>>>> maybe jarring next the the "m". I'm inclined to maelstroom, since I >>>>>>>> associate it with "zoom". I wouldn't necessarily go for the >>>>>>>> absolute >>>>>>>> lowest results. I have an entirely unsubstantiated belief that >>>>>>>> anything less than 10,000 gives a reasonable chance to compete once >>>>>>>> a >>>>>>>> user's browsing history is taken into account. Finally you need to >>>>>>>> check existing results don't return something abhorrent (I didn't do >>>>>>>> this). >>>>>>>> >>>>>>>> I'd encourage to play around testing on google search. Its quick >>>>>>>> and >>>>>>>> easy to generate and test alternatives. I've added a few more below. >>>>>>>> "maelstra" --> 3,560 >>>>>>>> "maelstram" --> 504 >>>>>>>> "maelstrim" --> 1200 >>>>>>>> "maelstroon" --> 58 >>>>>>>> "maelstroomi" --> 4 >>>>>>>> >>>>>>>> btw, I wouldn't swap the order of the "ae" since that would be >>>>>>>> susceptible to real typing errors. >>>>>>>> >>>>>>>> cheers -ben >>>>>>>> >>>>>>>> >>>>>>> >>>>> >> >> >> > >

Dec. 9, 2015

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

by Thierry Goubier

Le 09/12/2015 00:15, Mariano Martinez Peck a Ã©crit : > > > On Tue, Dec 8, 2015 at 6:23 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Le 08/12/2015 16:53, Christophe Demarey a Ã©crit : > > yes, we miss a package initialize method ... > > > FileTree, GitFileTree and probably Monticello have support for a > package initialize method. > > > > mmmmmm package initialize method in Monticello? I never saw that. Could > you share more details please? What I see is the following files that are checked when loading a FileTree or GitFileTree package: #('initializers*' 'preamble.st' 'postscript.st' 'preambleOfRemoval*' 'postscriptOfRemoval*') As far as I can follow the code, initializers relates to class initialization (calls to the various class initializers are written there?). Package initialize would be postscript.st. Thierry > > Now, when I was doing my browser, I wondered about giving access to > such code... turns out nobody uses it. > > Thierry > > > 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 > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com> > <mailto:kilon.alios@gmail.com > <mailto:kilon.alios@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 > <sven(a)stfx.eu <mailto:sven@stfx.eu> > <mailto:sven@stfx.eu <mailto:sven@stfx.eu>>> wrote: > > Hi Dimitris, > > > On 07 Dec 2015, at 23:12, Dimitris Chloupis > <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com> <mailto:kilon.alios@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/> > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com

Dec. 9, 2015