- Pharo-users - lists.pharo.org

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

[ 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