- Pharo-users - lists.pharo.org

interview on .Net Rocks! about Moose, humane assessment, Pharo and GT

by Tudor Girba

Hi, I had the pleasure of giving an interview for the .Net Rocks! podcast. It was quite fun and I managed to mention Moose, humane assessment, Pharo and GT in 45 minutes. It was not as smooth as a presentation but I still think it's a useful advertisement. Let me know what you think, and feel free to promote it further: https://dotnetrocks.com/default.aspx?showNum=1172 http://www.tudorgirba.com/blog/dotnetrocks-interview-moose-humane-assessmen… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

July 30, 2015

Re: [Pharo-users] VM Crash after adding ram

by Esteban Lorenzano

Hi, did you try a fresh Pharo image (without loaded code)? ExternalObject and ExternalAddress are FFI soâ¦ problem *could* be thereâ¦ no idea what can be happening, but wellâ¦ it could be there :) cheers, Esteban > On 30 Jul 2015, at 20:27, Ramon Leon <ramon.leon(a)allresnet.com> wrote: > > So I've just upgraded my Ubuntu 14.04 machine to 16 gig of ram from 8 gig of ram and suddenly I can no longer start my Pharo VM; I don't understand why adding ram would make the vm stop working, I've been using it for year without problems. Can anyone interpret this: > > no objects after the end of memory > > pharo VM version: 3.9-7 #1 Tue May 6 08:26:29 UTC 2014 gcc 4.8.1 [Production ITHB VM] > Built from: NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 > With: NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 > Revision: https://github.com/pharo-project/pharo-vm.git Commit: ef5832e6f70e5b24e8b9b1f4b8509a62b6c88040 Date: 2014-01-26 15:34:28 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14794 > Build host: Linux wani07 2.6.24-32-xen #1 SMP Mon Dec 3 16:12:25 UTC 2012 i686 i686 i686 GNU/Linux > plugin path: /usr/lib/pharo-vm/ [default: /usr/lib/pharo-vm/] > > > C stack backtrace: > /usr/lib/pharo-vm/pharo-vm[0x809add3] > /usr/lib/pharo-vm/pharo-vm(error+0x17)[0x809af37] > /usr/lib/pharo-vm/pharo-vm[0x806ee94] > [0xb72ca6cd] > [0xb72b0700] > [0xb72ca2ca] > [0xb72b0ccd] > [0xb72b1989] > [0xb72b0c5b] > [0xb72b0700] > [0xb8080227] > [0xb807c7e1] > [0xb807ca01] > [0xb72b05c0] > > > Smalltalk stack dump: > 0xffa39fc8 M ExternalAddress class(Behavior)>allInstancesDo: 0xb86ca450: a(n) ExternalAddress class > 0xffa39fec I ExternalAddress class>startUp: 0xb86ca450: a(n) ExternalAddress class > 0xffa3a008 M ExternalObject class>startUp: 0xb86c8820: a(n) ExternalObject class > 0xffa3a030 M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a04c M BlockClosure>on:do: 0xc30bd160: a(n) BlockClosure > 0xffa3a07c M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a0a4 I OrderedCollection>do: 0xb75c4d54: a(n) OrderedCollection > 0xffa3a0cc I SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a0f8 I SmalltalkImage>processStartUpList: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a124 I SmalltalkImage>snapshot:andQuit:embedded: 0xb75c4c24: a(n) SmalltalkImage > 0xc26d5f90 s SmalltalkImage>snapshot:andQuit: > 0xc2bff710 s WorldState class>saveAndQuit > 0xc2bff76c s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0xc2bff7c8 s BlockClosure>ensure: > 0xc26d5114 s CursorWithMask(Cursor)>showWhile: > 0xc26d50a4 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0xc2bff824 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: > 0xc2bff880 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: > 0xc2bff8dc s MouseButtonEvent>sentTo: > 0xc2bff938 s ToggleMenuItemMorph(Morph)>handleEvent: > 0xc26d4f80 s MorphicEventDispatcher>dispatchDefault:with: > 0xc26d4fdc s MorphicEventDispatcher>dispatchEvent:with: > 0xc2bfefe0 s ToggleMenuItemMorph(Morph)>processEvent:using: > 0xc2bff03c s MorphicEventDispatcher>dispatchDefault:with: > 0xc2bff098 s MorphicEventDispatcher>dispatchEvent:with: > 0xc2bff0f4 s MenuMorph(Morph)>processEvent:using: > 0xc2bff150 s MenuMorph(Morph)>processEvent: > 0xc2bff1ac s MenuMorph>handleFocusEvent: > 0xc2bff208 s [] in HandMorph>sendFocusEvent:to:clear: > 0xc2bff264 s [] in PasteUpMorph>becomeActiveDuring: > 0xc2bff2c0 s BlockClosure>on:do: > 0xc26d4e8c s PasteUpMorph>becomeActiveDuring: > 0xc26d4e14 s HandMorph>sendFocusEvent:to:clear: > 0xc2bff9f0 s HandMorph>sendEvent:focus:clear: > 0xc26d4da0 s HandMorph>sendMouseEvent: > 0xc26d4d38 s HandMorph>handleEvent: > 0xc2bffa4c s HandMorph>processEvents > 0xc2bffaa8 s [] in WorldState>doOneCycleNowFor: > 0xc2bffb04 s Array(SequenceableCollection)>do: > 0xc2bffb60 s WorldState>handsDo: > 0xc26d4bd4 s WorldState>doOneCycleNowFor: > 0xc2bffbbc s WorldState>doOneCycleFor: > 0xc2bffc18 s PasteUpMorph>doOneCycle > 0xc240332c s [] in Project class>spawnNewProcess > 0xc2403078 s [] in BlockClosure>newProcess > > Most recent primitives > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > < > basicNew: > findSubstringViaPrimitive:in:startingAt:matchTable: > new: > basicNew > new: > at:put: > at:put: > perform:with: > perform:with: > at: > at: > perform:with: > perform:with: > someInstance > nextInstance > millisecondClockValue > signal > at:put: > at:put: > primSignal:atMilliseconds: > millisecondClockValue > wait > primGetNextEvent: > millisecondClockValue > wait > signal > at:put: > at:put: > millisecondClockValue > primSignal:atMilliseconds: > millisecondClockValue > wait > signal > wait > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > > stack page bytes 4096 available headroom 3300 minimum unused headroom 3540 > > (no objects after the end of memory) > Aborted (core dumped) > > -- > Ramon Leon > >

July 30, 2015

Re: [Pharo-users] [Moose-dev] Re: Script of the day

by H. Hirzel

Is it possible to use a tree map? --Hannes On 7/30/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I gave a try, and I did not find anything weird. > I guess your document folder contains many files, as Doru said > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jul 30, 2015, at 5:51 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >> Frankly I dont mind big images or big data , neither I share the obsession >> to shrink things down to few mbs in a time that we are talking in TBs . >> >> Anyway you asked for the image and this is a link to it >> >> https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0 >> <https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0> >> >> I dont think you will find anything abnormal about it though. >> >> I was wondering whether it would worth the effort beyond the unit tests >> that check for behaviour of the code to have also benchmark tests that >> will have to pass specific standards so that specific method must perform >> under a strict timetable specific tasks, this way CI may alert not only >> unit tests that fail but also benchmarks that fail , automagically. >> >> Maybe some food for thought. >> >> Personally I am far more worried how much CPU Pharo consumes than how much >> RAM. >> >> On Wed, Jul 29, 2015 at 11:54 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> Not sure if there is any downside (I've been using it for a long time >> without problems), but image cleanup often does wonders for me. >> >> Moose image >> 410 MB => cleanup (World -> System -> Do Image Cleanup) => save => 237 >> MB >> and I even had situations where it went from ~600 MB to ~60 MB. >> (As to why my images are so massive... right now there are 19 windows >> opened inside most of them with opened roassal visualization... and I am >> saving like every five minutes... but that is just a guess.) >> >> But image cleanup is supposed to break things, so better to backup the >> folder first. >> Plus is cache really necessary? I mean it's a cache. .image + .changes >> should usually suffice. >> >> Peter >> >> On Wed, Jul 29, 2015 at 10:45 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> Tudor I dont know if you received my message but I already answered that >> with this: >> >> "ah ok then its normal. Yes the structure is extensive, its 13 folders >> (the rest 71 are files some of them very big), I would not be surprised if >> each contains 100 files in its own subfolders." >> >> >> >> On Wed, Jul 29, 2015 at 11:30 PM Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> Hi, >> >> But, do you confirm that you have many files under the mentioned folder? >> >> Cheers, >> Doru >> >> >> >> On Wed, Jul 29, 2015 at 10:25 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> the image is 180 mb, changes are another 15, there are several other >> folders that raise the total size to 250 mb, monticello-cache and >> github-cache prodominately. >> >> Hmm ok my bad, the size of the zip is 89 MB not 200 mb. Still will take me >> 1-2 hours to upload on this connection. So if you guys still need the >> image i can upload tommorow from work, though it seems my slow down is >> normal. >> >> Afterall I am sure you can test it yourselves on complex file structures >> to see if it has delays as long as 20 minutes. >> >> >> >> On Wed, Jul 29, 2015 at 11:01 PM Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu>> wrote: >> >> > On 29 Jul 2015, at 21:33, Dimitris Chloupis <kilon.alios(a)gmail.com >> > <mailto:kilon.alios@gmail.com>> wrote: >> > >> > well i can send you the image tommorow because its huge (200 MB ziped) >> > for my pathetically slow internet connection at home. I will send it >> > from work which is 8 times faster. >> >> If the image is 200 MB zipped, how large is it in its normal state ? >> >> For me, a 100 MB image file is already quite large, that would compress to >> maybe 20/30 MB. >> >> This doesn't sound right to me, unless you explicitly tried to store a lot >> of data. >> >> Maybe something else is wrong that would explain the slowness. >> >> > I can tell you that I am on MacOS Yosemite , I get my image with >> > pharolauncher, the image was dowloaded at 27-07-15 some of the 84 items >> > are folders that contain many sub folders. No idea if that matters. >> > >> > I got Roassal 2 using the Package Browser in Pharo 5 (the new >> > configuration browser). >> > >> > On Wed, Jul 29, 2015 at 8:17 PM Alexandre Bergel >> > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> > Are you using windows? I know it may has problems regarding the source >> > code. You have 84 items and the visualization is slow? How is this >> > possible. >> > >> > Can I have a look at your image? >> > >> > Cheers, >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> >> On Jul 29, 2015, at 12:26 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> >> <mailto:kilon.alios@gmail.com>> wrote: >> >> >> >> thats ok it unfroze after 20 minutes or so . I managed to inspect the b >> >> but its incredible slow to navigate and use . Even moving the inspector >> >> around is incredible slow. My Documents folder contains 84 items, maybe >> >> it cant handle so well this amount of datea ? >> >> >> >> On Wed, Jul 29, 2015 at 5:55 PM Alexandre Bergel >> >> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Ohâ¦ sorry. Was not my intention >> >> >> >> Alexandre >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >>> On Jul 29, 2015, at 11:24 AM, Dimitris Chloupis <kilon.alios(a)gmail.com >> >>> <mailto:kilon.alios@gmail.com>> wrote: >> >>> >> >>> that was a nice way to freeze my image, thank you :D >> >>> >> >>> On Wed, Jul 29, 2015 at 4:27 PM Alexandre Bergel >> >>> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >>> Hi! >> >>> >> >>> Just to share a couple of experiment. I have tried the following in a >> >>> playground: >> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >>> b := RTMondrian new. >> >>> >> >>> b shape rectangle >> >>> if: [ :aFile | aFile path basename beginsWith: '.' ] color: Color >> >>> red. >> >>> b nodes: FileLocator documents allChildren. >> >>> b edges connectFrom: #parent. >> >>> b normalizer >> >>> normalizeSize: #size using: #sqrt. >> >>> b layout tree. >> >>> b >> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >>> >> >>> It shows a tree of the file system. Thanks to GT, simply clicking on a >> >>> file may show you the content and other things. >> >>> <Screen Shot 2015-07-29 at 10.23.51 AM.png> >> >>> >> >>> You can also use the cluster layout: >> >>> <Screen Shot 2015-07-29 at 10.25.11 AM.png> >> >>> >> >>> I have tried this on OS X, since the pointed folder is ~/Documents. >> >>> >> >>> Cheers, >> >>> Alexandre >> >>> -- >> >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> Moose-dev mailing list >> >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

July 30, 2015

VM Crash after adding ram

by Ramon Leon

So I've just upgraded my Ubuntu 14.04 machine to 16 gig of ram from 8 gig of ram and suddenly I can no longer start my Pharo VM; I don't understand why adding ram would make the vm stop working, I've been using it for year without problems. Can anyone interpret this: no objects after the end of memory pharo VM version: 3.9-7 #1 Tue May 6 08:26:29 UTC 2014 gcc 4.8.1 [Production ITHB VM] Built from: NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 With: NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 Revision: https://github.com/pharo-project/pharo-vm.git Commit: ef5832e6f70e5b24e8b9b1f4b8509a62b6c88040 Date: 2014-01-26 15:34:28 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14794 Build host: Linux wani07 2.6.24-32-xen #1 SMP Mon Dec 3 16:12:25 UTC 2012 i686 i686 i686 GNU/Linux plugin path: /usr/lib/pharo-vm/ [default: /usr/lib/pharo-vm/] C stack backtrace: /usr/lib/pharo-vm/pharo-vm[0x809add3] /usr/lib/pharo-vm/pharo-vm(error+0x17)[0x809af37] /usr/lib/pharo-vm/pharo-vm[0x806ee94] [0xb72ca6cd] [0xb72b0700] [0xb72ca2ca] [0xb72b0ccd] [0xb72b1989] [0xb72b0c5b] [0xb72b0700] [0xb8080227] [0xb807c7e1] [0xb807ca01] [0xb72b05c0] Smalltalk stack dump: 0xffa39fc8 M ExternalAddress class(Behavior)>allInstancesDo: 0xb86ca450: a(n) ExternalAddress class 0xffa39fec I ExternalAddress class>startUp: 0xb86ca450: a(n) ExternalAddress class 0xffa3a008 M ExternalObject class>startUp: 0xb86c8820: a(n) ExternalObject class 0xffa3a030 M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a04c M BlockClosure>on:do: 0xc30bd160: a(n) BlockClosure 0xffa3a07c M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a0a4 I OrderedCollection>do: 0xb75c4d54: a(n) OrderedCollection 0xffa3a0cc I SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a0f8 I SmalltalkImage>processStartUpList: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a124 I SmalltalkImage>snapshot:andQuit:embedded: 0xb75c4c24: a(n) SmalltalkImage 0xc26d5f90 s SmalltalkImage>snapshot:andQuit: 0xc2bff710 s WorldState class>saveAndQuit 0xc2bff76c s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: 0xc2bff7c8 s BlockClosure>ensure: 0xc26d5114 s CursorWithMask(Cursor)>showWhile: 0xc26d50a4 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: 0xc2bff824 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: 0xc2bff880 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: 0xc2bff8dc s MouseButtonEvent>sentTo: 0xc2bff938 s ToggleMenuItemMorph(Morph)>handleEvent: 0xc26d4f80 s MorphicEventDispatcher>dispatchDefault:with: 0xc26d4fdc s MorphicEventDispatcher>dispatchEvent:with: 0xc2bfefe0 s ToggleMenuItemMorph(Morph)>processEvent:using: 0xc2bff03c s MorphicEventDispatcher>dispatchDefault:with: 0xc2bff098 s MorphicEventDispatcher>dispatchEvent:with: 0xc2bff0f4 s MenuMorph(Morph)>processEvent:using: 0xc2bff150 s MenuMorph(Morph)>processEvent: 0xc2bff1ac s MenuMorph>handleFocusEvent: 0xc2bff208 s [] in HandMorph>sendFocusEvent:to:clear: 0xc2bff264 s [] in PasteUpMorph>becomeActiveDuring: 0xc2bff2c0 s BlockClosure>on:do: 0xc26d4e8c s PasteUpMorph>becomeActiveDuring: 0xc26d4e14 s HandMorph>sendFocusEvent:to:clear: 0xc2bff9f0 s HandMorph>sendEvent:focus:clear: 0xc26d4da0 s HandMorph>sendMouseEvent: 0xc26d4d38 s HandMorph>handleEvent: 0xc2bffa4c s HandMorph>processEvents 0xc2bffaa8 s [] in WorldState>doOneCycleNowFor: 0xc2bffb04 s Array(SequenceableCollection)>do: 0xc2bffb60 s WorldState>handsDo: 0xc26d4bd4 s WorldState>doOneCycleNowFor: 0xc2bffbbc s WorldState>doOneCycleFor: 0xc2bffc18 s PasteUpMorph>doOneCycle 0xc240332c s [] in Project class>spawnNewProcess 0xc2403078 s [] in BlockClosure>newProcess Most recent primitives at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: < basicNew: findSubstringViaPrimitive:in:startingAt:matchTable: new: basicNew new: at:put: at:put: perform:with: perform:with: at: at: perform:with: perform:with: someInstance nextInstance millisecondClockValue signal at:put: at:put: primSignal:atMilliseconds: millisecondClockValue wait primGetNextEvent: millisecondClockValue wait signal at:put: at:put: millisecondClockValue primSignal:atMilliseconds: millisecondClockValue wait signal wait atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance stack page bytes 4096 available headroom 3300 minimum unused headroom 3540 (no objects after the end of memory) Aborted (core dumped) -- Ramon Leon

July 30, 2015

Re: [Pharo-users] AST visualization with Roassal

by Alexandre Bergel

Excellent! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jul 30, 2015, at 12:40 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Yes, we checked. This explains the strange âtoo largeâ rectangle :-)

July 30, 2015

Re: [Pharo-users] AST visualization with Roassal

by Mark Rizun

Great, everybody is happy ;) Thanks Alex ! 30 Ð»Ð¸Ð¿. 2015 5:40 Ð¿Ð¿ "Marcus Denker" <marcus.denker(a)inria.fr> Ð¿Ð¸ÑÐµ: > > > On 30 Jul 2015, at 17:26, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > Hi Mark, > > > > I have introduced a class RTIdentityGroup. > > > > You can do: > > > > -=-=-= -=-=-= -=-=-= -=-=-= > > ast := RBParser parseExpression: 'self foo. self foo'. > > builder := RTMondrian new. > > builder shape ellipse size: 15. > > nodes := builder nodes: ast allChildren. > > builder edges > > elements: nodes asIdentityGroup; > > connectFrom: #parent. > > builder layout tree. > > builder > > -=-=-= -=-=-= -=-=-= -=-=-= > > > > You obtain this: > > <Screen Shot 2015-07-30 at 12.25.25 PM.png> > > > > Maybe Marcus will have the same problem. > > Yes, we checked. This explains the strange âtoo largeâ rectangle :-) > > Marcus > > >

July 30, 2015

Re: [Pharo-users] AST visualization with Roassal

by Marcus Denker

> On 30 Jul 2015, at 17:26, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Mark, > > I have introduced a class RTIdentityGroup. > > You can do: > > -=-=-= -=-=-= -=-=-= -=-=-= > ast := RBParser parseExpression: 'self foo. self foo'. > builder := RTMondrian new. > builder shape ellipse size: 15. > nodes := builder nodes: ast allChildren. > builder edges > elements: nodes asIdentityGroup; > connectFrom: #parent. > builder layout tree. > builder > -=-=-= -=-=-= -=-=-= -=-=-= > > You obtain this: > <Screen Shot 2015-07-30 at 12.25.25 PM.png> > > Maybe Marcus will have the same problem. Yes, we checked. This explains the strange âtoo largeâ rectangle :-) Marcus

July 30, 2015

Re: [Pharo-users] AST visualization with Roassal

by Alexandre Bergel

Hi Mark, I have introduced a class RTIdentityGroup. You can do: -=-=-= -=-=-= -=-=-= -=-=-= ast := RBParser parseExpression: 'self foo. self foo'. builder := RTMondrian new. builder shape ellipse size: 15. nodes := builder nodes: ast allChildren. builder edges elements: nodes asIdentityGroup; connectFrom: #parent. builder layout tree. builder -=-=-= -=-=-= -=-=-= -=-=-= You obtain this: Maybe Marcus will have the same problem. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jul 30, 2015, at 11:47 AM, Mark Rizun <mrizun(a)gmail.com> wrote: > > Pretty much; there is test for equality > > RTGroup>>elementFromModel: anObject > ^ self detect: [ :el | el model = anObject ] ifNone: [ nil ] > > and equality is more often than not wanted. > > So solution might be to tell Mondrian that you want to compare by identity and not equality? > > Exactly! I'd like to have an option to select how I want to compare objects.

July 30, 2015

Re: [Pharo-users] ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

by Blondeau Vincent

Hi Yuriy, You have to put the library used by native boost in the VM folder (ie. *.so or *.dll). It should do the trick. Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Yuriy Tymchuk EnvoyÃ© : mardi 28 juillet 2015 22:08 Ã : Any question about pharo is welcome Objet : Re: [Pharo-users] ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule: Alex, Ronie, do you have any idea what can cause the issue? Because Iâve never worked with native boost. Uko On 28 Jul 2015, at 20:52, Rafael Luque <rafael.luque.leiva(a)gmail.com<mailto:rafael.luque.leiva@gmail.com>> wrote: Hi Yuriy, I've tried with the latest changes but the problem described in my previous email still persists: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:" All your recommendations will be very welcomed. Thank you. Rafa 2015-04-24 18:13 GMT+02:00 Rafael Luque <rafael.luque.leiva(a)gmail.com<mailto:rafael.luque.leiva@gmail.com>>: Hi Uko I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:" This is the stack trace for your information: =========================================== NBFFICallout>>loaderForArgNamed: NBFFICallout>>loaderForArgNamed:indirectIndex: NBFFICallout>>argName:indirectIndex:type:ptrArity: NBFnSpecParser>>parseArgument NBFnSpecParser>>parseArguments NBFnSpecParser>>parseAnonFunction: NBFFICallout>>anonSpec: [ :t3 | t3 useEmitCall; callType: conv; sender: context; parseOptions: options; anonSpec: t1; generate: t2 ] in NBFFICalloutAPI>>function:emit: [ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: BlockClosure>>on:do: NBRecursionDetect class>>in:during: NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode: NBFFICalloutAPI>>function:emit: NativeBoostMac32(NativeBoost)>>loadModule: CairoLibraryLoader class>>loadCairoLibrary CairoLibraryLoader class>>getLibraryHandle AthensCairoSurface class>>nbLibraryNameOrHandle AthensCairoSurface class(Object)>>nbCall: AthensCairoSurface class>>primImage:width:height: AthensCairoSurface class>>extent:format: AthensCairoSurface class>>extent: TRCanvas>>initialize TRCanvas class(Behavior)>>new RTView>>initialize RTView class(Behavior)>>new R3View>>initialize R3View class(Behavior)>>new Roassal3DModel>>initialize Roassal3DModel class(Behavior)>>new Roassal3DModel class(ComposableModel class)>>owner: CityBrowser(ComposableModel)>>instantiate: CityBrowser>>initializeWidgets CityBrowser(ComposableModel)>>initialize CityBrowser class(Behavior)>>new CityBrowser class(ComposableModel class)>>owner: VidiBrowser(ComposableModel)>>instantiate: VidiBrowser>>initializeWidgets VidiBrowser(ComposableModel)>>initialize VidiBrowser>>initialize VidiBrowser class(Behavior)>>new ReModel>>vidi VidiSession>>openVidi [ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction [ self value. Processor terminateActive ] in BlockClosure>>newProcess =========================================== Thank you. 2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com<mailto:yuriy.tymchuk@me.com>>: Hi Rafael, now ViDI should work. I havenât been working on it for a while, but feel free to report more issues, as Iâll get back to it soon. Uko On 24 Apr 2015, at 09:57, Rafael Luque <rafael.luque.leiva(a)gmail.com<mailto:rafael.luque.leiva@gmail.com>> wrote: Thank you! I'm looking forward to hearing from you about the new version. 2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com<mailto:yuriy.tymchuk@me.com>>: Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :) Uko On 23 Apr 2015, at 17:46, Rafael Luque <rafael.luque.leiva(a)gmail.com<mailto:rafael.luque.leiva@gmail.com>> wrote: I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2). Thanks 2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com<mailto:yuriy.tymchuk@me.com>>: Hi Rafael, I will take a look. Which operating system are you using? Uko On 23 Apr 2015, at 17:30, Rafael Luque <rafael.luque.leiva(a)gmail.com<mailto:rafael.luque.leiva@gmail.com>> wrote: Hi, I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page: Gofer new smalltalkhubUser: 'YuriyTymchuk' project: 'Configuration'; configurationOf: 'Vidi'; load. #ConfigurationOfVidi asClass loadStable When I launch a review session over any package I always get the following error: "Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:" I'm very interested in this kind of quality assurance tools, so any help will be very welcomed. Thank you. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

July 30, 2015

Re: [Pharo-users] ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

by Alexandre Bergel

NativeBoost create this kind of error if you have the .sources file that is missing. Are you sure this is not the case? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jul 28, 2015, at 5:08 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Alex, Ronie, > > do you have any idea what can cause the issue? Because Iâve never worked with native boost. > > Uko > > >> On 28 Jul 2015, at 20:52, Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>> wrote: >> >> Hi Yuriy, >> >> I've tried with the latest changes but the problem described in my previous email still persists: >> >> "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:" >> >> All your recommendations will be very welcomed. >> >> Thank you. >> >> Rafa >> >> >> >> 2015-04-24 18:13 GMT+02:00 Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>>: >> Hi Uko >> >> I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:" >> >> This is the stack trace for your information: >> >> =========================================== >> >> NBFFICallout>>loaderForArgNamed: >> NBFFICallout>>loaderForArgNamed:indirectIndex: >> NBFFICallout>>argName:indirectIndex:type:ptrArity: >> NBFnSpecParser>>parseArgument >> NBFnSpecParser>>parseArguments >> NBFnSpecParser>>parseAnonFunction: >> NBFFICallout>>anonSpec: >> [ :t3 | >> t3 >> useEmitCall; >> callType: conv; >> sender: context; >> parseOptions: options; >> anonSpec: t1; >> generate: t2 ] in NBFFICalloutAPI>>function:emit: >> [ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: >> BlockClosure>>on:do: >> NBRecursionDetect class>>in:during: >> NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: >> NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode: >> NBFFICalloutAPI>>function:emit: >> NativeBoostMac32(NativeBoost)>>loadModule: >> CairoLibraryLoader class>>loadCairoLibrary >> CairoLibraryLoader class>>getLibraryHandle >> AthensCairoSurface class>>nbLibraryNameOrHandle >> AthensCairoSurface class(Object)>>nbCall: >> AthensCairoSurface class>>primImage:width:height: >> AthensCairoSurface class>>extent:format: >> AthensCairoSurface class>>extent: >> TRCanvas>>initialize >> TRCanvas class(Behavior)>>new >> RTView>>initialize >> RTView class(Behavior)>>new >> R3View>>initialize >> R3View class(Behavior)>>new >> Roassal3DModel>>initialize >> Roassal3DModel class(Behavior)>>new >> Roassal3DModel class(ComposableModel class)>>owner: >> CityBrowser(ComposableModel)>>instantiate: >> CityBrowser>>initializeWidgets >> CityBrowser(ComposableModel)>>initialize >> CityBrowser class(Behavior)>>new >> CityBrowser class(ComposableModel class)>>owner: >> VidiBrowser(ComposableModel)>>instantiate: >> VidiBrowser>>initializeWidgets >> VidiBrowser(ComposableModel)>>initialize >> VidiBrowser>>initialize >> VidiBrowser class(Behavior)>>new >> ReModel>>vidi >> VidiSession>>openVidi >> [ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction >> [ >> self value. >> Processor terminateActive ] in BlockClosure>>newProcess >> >> =========================================== >> >> >> Thank you. >> >> 2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> Hi Rafael, >> >> now ViDI should work. I havenât been working on it for a while, but feel free to report more issues, as Iâll get back to it soon. >> >> Uko >> >> >> >>> On 24 Apr 2015, at 09:57, Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>> wrote: >>> >>> Thank you! I'm looking forward to hearing from you about the new version. >>> >>> 2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>> Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :) >>> >>> Uko >>> >>> >>> >>>> On 23 Apr 2015, at 17:46, Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>> wrote: >>>> >>>> I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2). >>>> >>>> Thanks >>>> >>>> 2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>>> Hi Rafael, >>>> >>>> I will take a look. Which operating system are you using? >>>> >>>> Uko >>>> >>>>> On 23 Apr 2015, at 17:30, Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page: >>>>> >>>>> Gofer new >>>>> smalltalkhubUser: 'YuriyTymchuk' >>>>> project: 'Configuration'; >>>>> configurationOf: 'Vidi'; >>>>> load. >>>>> #ConfigurationOfVidi asClass loadStable >>>>> >>>>> When I launch a review session over any package I always get the following error: >>>>> >>>>> "Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:" >>>>> >>>>> I'm very interested in this kind of quality assurance tools, so any help will be very welcomed. >>>>> >>>>> Thank you. >>>> >>>> >>> >>> >> >> >> >

July 30, 2015