- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Re: GTDebugger raising an emergency debugger
by Tudor Girba Jan. 5, 2015

Jan. 5, 2015

Great! Now, the Moose 5.1 image is usable on top of Pharo 4.0! There are still some red tests, but it works reasonably. It took about 1 day of work and it was mostly due to problems related with the GTDebugger (which I do not expect other projects to have ;)). Cheers, Doru On Mon, Jan 5, 2015 at 4:33 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > I fixed the problem with the debugger. Let me know if you encounter any > other problems. > > Cheers, > Andrei > > On Mon, Jan 5, 2015 at 4:26 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Yes. That one is based on Pharo 4.0 and it is not ready for consumption >> yet. >> >> Doru >> >> On Mon, Jan 5, 2015 at 3:08 PM, Alexandre Bergel <alexandre.bergel(a)me.com >> > wrote: >> >>> https://ci.inria.fr/moose/job/moose-5.1/3/artifact/moose-5.1.zip >>> https://ci.inria.fr/moose/job/moose-5.1/3/ >>> >>> Alexandre >>> >>> > On Jan 5, 2015, at 10:48 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> > >>> > Which job? :) >>> > >>> > Doru >>> > >>> > On Mon, Jan 5, 2015 at 2:27 PM, Alexandre Bergel < >>> alexandre.bergel(a)me.com> wrote: >>> > I have downloaded the last version of Moose, directly from jenkins >>> > >>> > Alexandre >>> > >>> > >>> > > On Jan 5, 2015, at 10:18 AM, Tudor Girba <tudor(a)tudorgirba.com> >>> wrote: >>> > > >>> > > Hi, >>> > > >>> > > I moved most of the jobs to use Pharo 4, and indeed, we have an >>> issue with the GTDebugger. >>> > > >>> > > What image are you using? >>> > > >>> > > Cheers, >>> > > Doru >>> > > >>> > > >>> > > >>> > > On Mon, Jan 5, 2015 at 2:07 PM, Alexandre Bergel < >>> alexandre.bergel(a)me.com> wrote: >>> > > Hi! >>> > > >>> > > I wanted to have a look at why some tests are failing in the last >>> version of moose. >>> > > But I cannot even open a debugger. >>> > > Maybe some classes are missing. I see SystemDictionary>>at: in the >>> call stack. >>> > > >>> > > Cheers, >>> > > Alexandre >>> > > -- >>> > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > > Alexandre Bergel http://www.bergel.eu >>> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > > >>> > > >>> > > >>> > > >>> > > _______________________________________________ >>> > > Moose-dev mailing list >>> > > Moose-dev(a)iam.unibe.ch >>> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> > > >>> > > >>> > > >>> > > -- >>> > > www.tudorgirba.com >>> > > >>> > > "Every thing has its own flow" >>> > > _______________________________________________ >>> > > Moose-dev mailing list >>> > > Moose-dev(a)iam.unibe.ch >>> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> > >>> > -- >>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > Alexandre Bergel http://www.bergel.eu >>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > Moose-dev mailing list >>> > Moose-dev(a)iam.unibe.ch >>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> > >>> > >>> > >>> > -- >>> > www.tudorgirba.com >>> > >>> > "Every thing has its own flow" >>> > _______________________________________________ >>> > Moose-dev mailing list >>> > Moose-dev(a)iam.unibe.ch >>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> 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 > > -- www.tudorgirba.com "Every thing has its own flow"

1 0

Old inspector and explorer
by Norbert Hartl Jan. 5, 2015

Jan. 5, 2015

Is there a way to get the old tools via shortcut? I started something new with pharo 4.0 today. I discovered a bug in Nautilus where every rename or deletion of a method raises a debugger. I tried finding the bug but struggled because to me the new inspector is really confusing. If I "just" want to unfold a few levels of references to get a glimpse of the structure the new tool prevents me from doing that. There is just to much information in this window and too much happening to me. To me it looks like a power tool you need to get used to. So it is probably not the best tool for simple tasks and people new to this environment might be overwhelmed. At least I would like to be able to use the old tools. Norbert

11 50

[pharo-project/pharo-core] a28e71: 40429
by GitHub Jan. 5, 2015

Jan. 5, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a28e7177916f5db79ce3ca9b60d4bc0f5e7cad9c https://github.com/pharo-project/pharo-core/commit/a28e7177916f5db79ce3ca9b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-05 (Mon, 05 Jan 2015) Changed paths: M Kernel.package/Float.class/class/instance creation/fromIEEE32Bit_.st A KernelTests.package/FloatTest.class/instance/tests - IEEE 754/test32bitConversion.st A Morphic-Core.package/HandMorph.class/class/events-processing/cleanUp.st A Morphic-Core.package/HandMorph.class/class/events-processing/eventStats.st A Morphic-Core.package/HandMorph.class/class/events-processing/logEventStatsStart.st A Morphic-Core.package/HandMorph.class/class/events-processing/logEventStatsStop.st A Morphic-Core.package/HandMorph.class/class/events-processing/logEventStats_.st A Morphic-Core.package/HandMorph.class/class/settings/logEventStatsEnabled.st A Morphic-Core.package/HandMorph.class/class/settings/logEventStatsEnabled_.st A Morphic-Core.package/HandMorph.class/class/settings/settingsOn_.st M Morphic-Core.package/HandMorph.class/instance/events-processing/handleEvent_.st R Morphic-Core.package/HandMorph.class/instance/events-processing/logEventStats_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script429.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40429.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40429 14668 HandMorph event statistics should be off by default with preference https://pharo.fogbugz.com/f/cases/14668 14652 Float class fromIEEE32Bit: gradual underflow handling is buggy https://pharo.fogbugz.com/f/cases/14652 http://files.pharo.org/image/40/40429.zip

1 0

[pharo-project/pharo-core]
by GitHub Jan. 5, 2015

Jan. 5, 2015

Branch: refs/tags/40429 Home: https://github.com/pharo-project/pharo-core

1 0

WhatsUp from: 2015-01-05 until: 2015-01-18
by seaside＠rmod.lille.inria.fr Jan. 5, 2015

Jan. 5, 2015

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-01-18 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

4 3

CubeHelix integration (issue 14648 in update #40423)
by Torsten Bergmann Jan. 5, 2015

Jan. 5, 2015

What is the reasons for integration of class "CubeHelix" into standard Pharo image: https://pharo.fogbugz.com/f/cases/14648 So far the class is not (yet) referenced. Would'nt it make sense to have "Chroma-CubeHelix" as external loadable package? Thanks for any clarification! Bye T.

2 1

My New Year present to Pharo
by kilon alios Jan. 4, 2015

Jan. 4, 2015

Happy new year pharoers , I wish health and hapiness to all of you . Secretly these past few month I have been working on a 3d graphics wallpaper for Pharo. Finally I manage to create something worthy for Pharo which I present now to you This an actual lighthouse which is located in the Greek island of Andros. Its small, elegant and beautiful like Pharo ;) More info can be found here http://www.amazingplacesonearth.com/tourlitis-lighthouse-andros-island-gree… I release this image under CC license , you are welcome to use it anywhere you like as long as you credit me and even in commercial projects , completely free . You can also modify and redistribute it in any way again as long as you credit me. I hope you like it , I definitely had fun creating it :) PS: I also added it as attachment in case the inlining does not work â

3 6

Re: [Pharo-dev] The Smalltalk Renaissance Program
by Ben Coman Jan. 4, 2015

Jan. 4, 2015

On Thursday, January 1, 2015, Ben Coman wrote: > I refer to the two paragraphs following "On pharo being a new language". > I think Sven's response addressed these the best. > > Now I wonder if a history of evolving features from Smalltalk-72 "in the > context of Pharo" being another step of evolution would be a useful > addition to the Pharo story. > > Cheers -Ben > > On Wednesday, December 31, 2014, horrido <horrido.hobbies(a)gmail.com > <javascript:_e(%7B%7D,'cvml','horrido.hobbies(a)gmail.com');>> wrote: > >> Thank you very much. So please explain how the PR message is not aligned >> with >> the technical vision. I don't see any inconsistency. >> >> >> >> Ben Coman wrote >> > On Wednesday, December 31, 2014, Ben Coman wrote: >> > >> >> >> >> >> >> On Wednesday, December 31, 2014, horrido < >> >> > horrido.hobbies@ >> >> > > <javascript:_e(%7B%7D,'cvml',' >> >> > horrido.hobbies@ >> >> > ');>> wrote: >> >> >> >>> And, yes, I did not do my most thorough homework regarding Pharo, as >> >>> several >> >>> of you have pointed out. Frankly, I don't have /that/ much time and >> >>> energy. >> >>> I'm old and retired. I'm just doing this for pleasure. >> >>> >> >>> So I rely on /you/ to set me straight. >> >> >> >> >> >> In process :) >> >> >> >> >> >>> I remind you that I'm just the >> >>> coordinator of the campaign, because I'm sure none of you have that >> much >> >>> time to do what I'm doing. >> >> >> >> >> >> >> >> >> >> >> >>> >> >>> Marcus suggested that anyone can create a Google+ page, but he misses >> >>> the >> >>> point. The Google+ page is just one brick in the foundation of the >> >>> campaign. >> >>> It's part of a whole. >> >>> >> >>> Norbert suggests that I think I know what to do. No, I have ideas and >> I >> >>> have >> >>> a plan. There's no guarantee that it will work. Either you buy into my >> >>> plan, >> >>> or you don't. Either I have your support, or I don't. If the latter, I >> >>> shan't waste any more time (yours or mind). >> >>> >> >>> >> >> >> >> It's not just a matter of time, but inclination. If you are inclined >> to >> >>> do this, then it should be supported - but it's a matter of getting >> the >> >>> PR message aligned with the technical vision. We don't want the >> market >> >>> being told one thing then getting a different message here in-list. >> So >> >>> you made a misstep here. That's okay, you learn more that way than >> doing >> >>> nothing. It may take some more back-n-forth. I hope you continue. >> >> >> >> >> >> -Ben >> >> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797416.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >>

9 22

[story] using the inspector to debug a metacello configuration problem
by Tudor Girba Jan. 4, 2015

Jan. 4, 2015

Hi, Happy New Year! The GTInspector reaches its full potential when it is being extended to meet custom needs. I will try to document more scenarios to show how this works in practice and how programming changes as a result. Here is a story that describes a session of debugging a Metacello configuration problem: http://www.humane-assessment.com/blog/identifying-a-configuration-problem-w… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

2 1

HandMorph.EventStats
by Ben Coman Jan. 3, 2015

Jan. 3, 2015

Looking at HandMorph>>logEventStats: this is the only method to reference EventStats variable. Should we zero these values as part of release process? cheers -ben

2 2