December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] #deepCollect:

by dimitris chloupis

ÏÏÎµÎ¹Î»Îµ Î¼Î¿Ï ÏÎ·Î½ ÏÎ¬Î»Î¹ ÏÏÎ¿ kilon.alios(a)gmail.com Î³Î¹Î±ÏÎ¯ ÎµÎ´Ï Î¼ÏÎ±Î¯Î½Ï ÏÎ»ÎÎ¿Î½ ÏÏÎ¬Î½Î¹Î± ÎºÎ±Î¹ Î³Î¹Î± ÎºÎ¬ÏÎ¿Î¹Î¿ Î»ÏÎ³Î¿ Î´ÎµÎ½ Î¼Î¿Ï ÎºÎ±ÏÎµÎ²Î¬Î¶ÎµÎ¹ ÏÎ¿ Î±ÏÏÎµÎ¯Î¿ ÏÎ¿Ï. Â Î£ÏÏÏÏ ÏÎ¿Ï ÏÎµ Î¾ÎÏÎ±ÏÎ± ÏÎ¹Î»Î±ÏÎ¬ÎºÎ¹ Î±Î»Î»Î¬ Î±ÏÏÎ® ÏÎ·Î½ ÎµÎ²Î´Î¿Î¼Î¬Î´Î± Î´ÎµÎ½ Î®Î¼Î¿ÏÎ½ ÎºÎ±Î¹ ÏÎ¿Î»Ï ÏÏÎ± ÎºÎ±Î»Î¬ Î¼Î¿Ï. Î£ÏÎ·Î½ ÎµÎ¯ÏÎ± Î½Î± ÏÎ·Î½ Î³ÏÎ¬ÏÎµÎ¹Ï ÎÏÏÎ¹ Î³Î¹Î± ÏÎ¿ ÏÏÏÎ¹ÎºÏ ÏÎ·Ï ÏÏÏÎ¸ÎµÏÎ·Ï , Î½Î¿Î¼Î¹ÎºÎ¬ Î´ÎµÎ½ ÏÎ±Î¯Î¶ÎµÎ¹ Î¼ÎµÎ³Î¬Î»Î¿ ÏÏÎ»Î¿ Î±ÏÎ¿ ÏÎ·Î½ ÏÏÎ¹Î³Î¼Î® ÏÎ¿Ï ÎÏÎ¿ÏÎ½ Î»Î¬Î²ÎµÎ¹ Î³Î½ÏÏÎ· Î´Î·Î»Î±Î´Î® Î³Î½ÏÏÎ¯Î¶Î¿ÏÎ½ ÏÎ·Î½ ÏÎµÏÎ¯ÏÏÏÏÎ· ÏÎ¿Ï.Â On Friday, 13 December 2013, 23:29, Tudor Girba <tudor(a)tudorgirba.com> wrote: Hi Esteban, Indeed, I pondered on the issue of extending Object with the deep* methods. In the end, I chose to extend it because traversals are not a cherry on top, they are rather essential for significant analysis. >From my point of view, Pharo has to become a platform in which understanding and manipulating objects is an essential concern. The reason is that in the long run, it is precisely assessment-related activities that account for the largest development costs. I detailed a bit this idea here: http://www.humane-assessment.com/blog/choose-your-technology-for-the-long-r… For this we need a powerful toolkit that makes crafting custom analyses cheap, and traversals has a prominent place in it. Cheers, Doru On Fri, Dec 13, 2013 at 6:17 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: To avoid such kind of situations I would implement all the traversal methods as >a) Traits or >b) Class side methods of DeepTraversal (you choose the name) to which >you'll have to pass the collection and the block. > >E.g. DeepTraversal deep: aCollection do: aBlock >DeepTraversal flatten: aCollection thenDo: aBlock > >I, personally, don't like adding methods to Object unless it's >unavoidable(*). And in those cases I choose to prefix them with >something that is separate from the semantic, usually the >package/framework prefix. > >Regards, > >(*)I did that for years and in the long term it hits you back. >Esteban A. Maringolo > > >2013/12/13 Chris Cunningham <cunningham.cb(a)gmail.com>: > >> Hi. >> >> I was reading with interest the blog post on Traversal-enabled objects ( >> http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects ) when >> I noticed the method #deepCollect: referenced. Â Interestingly, I have a >> method called #deepCollect: that is use (wtih related methods like #deepDo: >> and #deepSelect:). Â I suspect these uses may be compatible, with the >> traveral versions being more generic. >> >> My set of #deep methods allow arbitrary flattening of collections. Â The >> #flatCollect: suite in Pharo today flattens objects 1 level; the >> #deepCollect: flattens the collections as many levels deep as they are >> nested. Â I found this to be a really useful ability when I work with >> PetitParser parsings, which tend give back massively nested Arrays by >> default. >> >> If you are interested, it is published at: >> http://www.smalltalkhub.com/#!/~cbc/DeepCollection/ . >> >> -cbc > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 21, 2013

[Post Sprint] reviews + please check issues you worked on

by Marcus Denker

Hi, After the sprintâ¦ -> Please check all the issues you worked on Correctly integrated? If not: - Maybe the monkey put it back to âwork needed?â - someone commented on it? - someone accidentally closed it? And there are issues that are fixed *and* passed the money, yet need someone else to check to make sure the fix is really working and goodâ¦ Marcus

Dec. 21, 2013

Great Sprint Yesterday!

by Marcus Denker

Hi, The Pharo Sprint yesterday was great! We fixed *a lot* (maybe 25-30 issues?). Not everything is integrated yetâ¦ Here are some Photos: https://plus.google.com/photos/100919417187170499293/albums/595963343591172…

Dec. 21, 2013

Re: [Pharo-dev] Problems with Athens Font Rendering

by Igor Stasenko

On 21 December 2013 03:41, J.F. Rick <self(a)je77.com> wrote: > Yes, that code will crash my machine (Ubuntu). I upgraded to the latest > Pharo 3.0 and added the newest Athens-Morphic package to get > AthensWrapMorph. Of the Athens packages, I have the following versions: > Balloon 13 > Cairo 51 > CairoPools 9 > Core 51 > Examples 26 > Morphic 25 > PangoCairo 14 > Text 7 > Tutorial 7 > > Cheers, > > Jeff > > PS Just adding the 30 point string by itself crashes the VM. > > thanks for info. I will try it in my virtual ubuntu image (i also added bug report) https://pharo.fogbugz.com/f/cases/12478/Crash-when-using-fonts-with-Athens-… feel free to add any extra info there, if you find more. > > On Saturday, December 21, 2013, Igor Stasenko wrote: > >> >> >> >> On 20 December 2013 15:35, J.F. Rick <self(a)je77.com> wrote: >> >>> I keep on crashing my VM based on using Athens to render fonts. Some >>> things work; some don't. It is a mystery. >>> >>> I managed to install the TrueType fonts. I'm using StringMorph in an >>> AthensWrapMorph, so it is rendered in Athens. When I do the following, it >>> seems to work fine: >>> >>> string := StringMorph contents: 'HelloWorld' font: (LogicalFont >>> familyName: 'Arial' pointSize: 20). >>> string color: Color white. >>> string position: 100 @ 100. >>> self addMorph: string. >>> >>> When I changed it to 30, it initially crashed. Now it doesn't crash, but >>> the rendering is the same as for 20. When I change it to 40, it crashes. >>> When I add two strings, one of size 20 and one of size 30, it crashes. All >>> of these things render fine outside of Athens (i.e., I just open them in >>> the world). >>> >>> What am I doing wrong? >>> >>> What platform you running, and can you share your code? >> >> Following runs well on my image (mac): >> >> >> | m string | >> m := AthensWrapMorph new. >> >> string := StringMorph contents: 'HelloWorld' font: (LogicalFont >> familyName: 'Arial' pointSize: 20). >> string color: Color red . >> >> m addMorph: string. >> >> string := StringMorph contents: 'HelloWorld' font: (LogicalFont >> familyName: 'Arial' pointSize: 30). >> string color: Color green . >> >> m addMorph: string. >> >> m openInWindow >> >> (image double-sized because of retina display :) >> [image: Inline images 1] >> >> Jeff >>> >>> -- >>> Jochen "Jeff" Rick, Ph.D. >>> http://www.je77.com/ >>> Skype ID: jochenrick >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Best regards, Igor Stasenko.

Dec. 21, 2013

Re: [Pharo-dev] Problems with Athens Font Rendering

by J.F. Rick

Yes, that code will crash my machine (Ubuntu). I upgraded to the latest Pharo 3.0 and added the newest Athens-Morphic package to get AthensWrapMorph. Of the Athens packages, I have the following versions: Balloon 13 Cairo 51 CairoPools 9 Core 51 Examples 26 Morphic 25 PangoCairo 14 Text 7 Tutorial 7 Cheers, Jeff PS Just adding the 30 point string by itself crashes the VM. On Saturday, December 21, 2013, Igor Stasenko wrote: > > > > On 20 December 2013 15:35, J.F. Rick <self(a)je77.com <javascript:_e({}, > 'cvml', 'self(a)je77.com');>> wrote: > >> I keep on crashing my VM based on using Athens to render fonts. Some >> things work; some don't. It is a mystery. >> >> I managed to install the TrueType fonts. I'm using StringMorph in an >> AthensWrapMorph, so it is rendered in Athens. When I do the following, it >> seems to work fine: >> >> string := StringMorph contents: 'HelloWorld' font: (LogicalFont >> familyName: 'Arial' pointSize: 20). >> string color: Color white. >> string position: 100 @ 100. >> self addMorph: string. >> >> When I changed it to 30, it initially crashed. Now it doesn't crash, but >> the rendering is the same as for 20. When I change it to 40, it crashes. >> When I add two strings, one of size 20 and one of size 30, it crashes. All >> of these things render fine outside of Athens (i.e., I just open them in >> the world). >> >> What am I doing wrong? >> >> What platform you running, and can you share your code? > > Following runs well on my image (mac): > > > | m string | > m := AthensWrapMorph new. > > string := StringMorph contents: 'HelloWorld' font: (LogicalFont > familyName: 'Arial' pointSize: 20). > string color: Color red . > > m addMorph: string. > > string := StringMorph contents: 'HelloWorld' font: (LogicalFont > familyName: 'Arial' pointSize: 30). > string color: Color green . > > m addMorph: string. > > m openInWindow > > (image double-sized because of retina display :) > [image: Inline images 1] > > Jeff >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > > > -- > Best regards, > Igor Stasenko. > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Dec. 21, 2013

Re: [Pharo-dev] Is pharo-project (Pharo-project@lists.gforge.inria.fr) still functioning?

by Sven Van Caekenberghe

The address you are looking for is pharo-dev(a)lists.pharo.org More at http://www.pharo-project.org/community Sven On 21 Dec 2013, at 00:40, vfclists . <vfclists(a)gmail.com> wrote: > There have been no updates to pharo-project (Pharo-project(a)lists.gforge.inria.fr) mailing list of late and mail sent to it is returned. Have I got my filters wrong or has the address changed? > > > > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com

Dec. 21, 2013

Re: [Pharo-dev] Problems with Athens Font Rendering

by Igor Stasenko

On 20 December 2013 15:35, J.F. Rick <self(a)je77.com> wrote: > I keep on crashing my VM based on using Athens to render fonts. Some > things work; some don't. It is a mystery. > > I managed to install the TrueType fonts. I'm using StringMorph in an > AthensWrapMorph, so it is rendered in Athens. When I do the following, it > seems to work fine: > > string := StringMorph contents: 'HelloWorld' font: (LogicalFont > familyName: 'Arial' pointSize: 20). > string color: Color white. > string position: 100 @ 100. > self addMorph: string. > > When I changed it to 30, it initially crashed. Now it doesn't crash, but > the rendering is the same as for 20. When I change it to 40, it crashes. > When I add two strings, one of size 20 and one of size 30, it crashes. All > of these things render fine outside of Athens (i.e., I just open them in > the world). > > What am I doing wrong? > > What platform you running, and can you share your code? Following runs well on my image (mac): | m string | m := AthensWrapMorph new. string := StringMorph contents: 'HelloWorld' font: (LogicalFont familyName: 'Arial' pointSize: 20). string color: Color red . m addMorph: string. string := StringMorph contents: 'HelloWorld' font: (LogicalFont familyName: 'Arial' pointSize: 30). string color: Color green . m addMorph: string. m openInWindow (image double-sized because of retina display :) [image: Inline images 1] Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Best regards, Igor Stasenko.

Dec. 21, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 21, 2013

[pharo-project/pharo-core] 31cb00: 30659

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 31cb00184ef985a5bae1422bdc3dacc213e93769 https://github.com/pharo-project/pharo-core/commit/31cb00184ef985a5bae1422b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-20 (Fri, 20 Dec 2013) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script312.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30659.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Debugger.package/SpecDebugger.class/instance/initialization/initializePresenter.st M Spec-Debugger.package/SpecDebuggerStack.class/class/menu/dynamicStackMenu_.st M Spec-Debugger.package/SpecDebuggerStack.class/definition.st R Spec-Debugger.package/SpecDebuggerStack.class/instance/actions lookup/contextMenuDebuggingActions.st A Spec-Debugger.package/SpecDebuggerStack.class/instance/actions lookup/generateContextMenuDebuggingActions.st M Spec-Debugger.package/SpecDebuggerStack.class/instance/initialization/contextMenu_.st M Spec-Debugger.package/SpecDebuggerStack.class/instance/initialization/initialize.st A Spec-Debugger.package/SpecDebuggerStack.class/instance/updating/updateDebuggingActions.st A Spec-Debugger.package/SpecDebuggerStack.class/instance/updating/updateForSelectionChanged.st M Spec-Debugger.package/extension/DebugAction/instance/asMenuRegistrationIn_.st A Spec-Debugger.package/extension/DebugAction/instance/shortcutCommand.st M System-Tools.package/ToolRegistry.class/instance/convenience-inspecting/inspectorClass.st M Tools.package/FinderNode.class/instance/private/displayString.st R Tools.package/MethodFinder.class/instance/debugging it/test2_.st R Tools.package/MethodFinder.class/instance/debugging it/testRandom.st R Tools.package/MethodFinder.class/instance/initialization/initialize.st A Tools.package/MethodFinder.class/instance/initialize/initialize.st A Tools.package/MethodFinder.class/instance/tests/test2_.st R Tools.package/MethodFinder.class/instance/tests/verify.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testAbs.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testDivision.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testGreaterThanANumber.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testPolynomial.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testPower.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testSearchForAccessAtOne.st A ToolsTest.package/MethodFinderTest.class/instance/test examples/testSearchForOne.st M ToolsTest.package/MethodFinderTest.class/instance/test examples/testSubstraction.st Log Message: ----------- 30659 12477 Move MethodFinder old tests from code to TestsPackages https://pharo.fogbugz.com/f/cases/12477 12055 The Spec Debugger should not require the registered inspector to be built on Spec https://pharo.fogbugz.com/f/cases/12055 11743 Debugger fix the key shortcuts https://pharo.fogbugz.com/f/cases/11743 http://files.pharo.org/image/30/30659.zip

Dec. 21, 2013

Is pharo-project (Pharo-project@lists.gforge.inria.fr) still functioning?

by vfclists .

There have been no updates to pharo-project ( Pharo-project(a)lists.gforge.inria.fr) mailing list of late and mail sent to it is returned. Have I got my filters wrong or has the address changed? -- Frank Church ======================= http://devblog.brahmancreations.com

Dec. 20, 2013