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

Re: [Pharo-dev] [Pharo-users] Great Sprint Yesterday!

by kilon alios

Are you considering organizing a sprint based on google hangout so more people can attend around the world ? Or do I miss the purpose of the sprint ? I am not familiar with this idea. On Sat, Dec 21, 2013 at 6:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > It is really great to see such a group of people coming together to > improve Pharo. > > I know from experience that you learn a lot from going to a sprint. > > Too bad I was unable to come. > > Sven > > On 21 Dec 2013, at 09:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > 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… > > > > <Bb8Hn4YIUAEcPWo.jpg-large.jpeg><IMG_2920.jpeg><IMG_2925.jpeg> > > >

Dec. 21, 2013

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

by kilon alios

"Send me the document to kilon.alios(a)gmail.com because here (yahoo mail) I rarely log in and for some strange reason it has not properly attached your file. Sorry for forgetting to reply to you earlier on my dear friend but this week I was not in the best mood. I told to compose the document this way to be more formal, legally it plays a minor role as long as they are aware of your case". I am a greek lawyer and I was helping a friend to create a letter for his employer for a potential promotion. Yahoo mail has changed recently its interface and it now collapses messages , without being aware it has collapsed the a moose message bellow my friend's message (saw them as "unclassified" ) and went I hit reply I was replying to this thread instead of his own message. I am now in process of migrating to gmail cause yahoo mail became to messy for me. On Sat, Dec 21, 2013 at 12:38 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ok, but now I am curious :). > > Could you translate? > > Doru > > > On Sat, Dec 21, 2013 at 10:26 AM, kilon alios <kilon.alios(a)gmail.com>wrote: > >> sorry for this i mixed up the mailing adresses :D >> >> >> On Sat, Dec 21, 2013 at 11:04 AM, dimitris chloupis <thekilon(a)yahoo.co.uk >> > wrote: >> >>> ÏÏÎµÎ¹Î»Îµ Î¼Î¿Ï ÏÎ·Î½ ÏÎ¬Î»Î¹ ÏÏÎ¿ 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" >>> >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 21, 2013

Re: [Pharo-dev] [Pharo-users] Great Sprint Yesterday!

by Sven Van Caekenberghe

It is really great to see such a group of people coming together to improve Pharo. I know from experience that you learn a lot from going to a sprint. Too bad I was unable to come. Sven On 21 Dec 2013, at 09:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 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… > > <Bb8Hn4YIUAEcPWo.jpg-large.jpeg><IMG_2920.jpeg><IMG_2925.jpeg>

Dec. 21, 2013

Re: [Pharo-dev] FFI loadable in Pharo 3.0

by ClÃ©ment Bera

Yeah Camillo Bruni made a compatibility package for FileDirectory to be able to move from Pharo 1.4 to Pharo 2+ easily. I don't remember where it is... I've just checked repos of the teams Pharo and Pharo extras on smalltalk hub and there's a project named* FileSystemLegacy*<http://smalltalkhub.com/#%21/%7EPharoExtras/FileSystemLegacy> It might be that. 2013/12/21 Sebastian Sastre <sebastian(a)flowingconcept.com> > > On Dec 20, 2013, at 4:06 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > for FileDirectory you have a loadable package. > > > > what you mean? where? > > >

Dec. 21, 2013

Re: [Pharo-dev] FFI loadable in Pharo 3.0

by Sebastian Sastre

On Dec 20, 2013, at 4:06 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > for FileDirectory you have a loadable package. what you mean? where?

Dec. 21, 2013

Are #explorerContents and #hasContentsInExplorer obsolete ?

by Sven Van Caekenberghe

Hi, It seems that #explorerContents and #hasContentsInExplorer are no longer used. Implementing a new Eye inspector with #addSpecialFields: seems to affect both the Inspector view as well as the Tree Inspector. So, should they be removed ? Sven

Dec. 21, 2013

Re: [Pharo-dev] gtinspector deconstructed

by Tudor Girba

Hi Sven, I agree with the underscore point of view, and I like the idea of graying it out. I added an issue for it: https://code.google.com/p/moose-technology/issues/detail?id=1035 Cheers, Doru On Fri, Dec 20, 2013 at 2:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 19 Dec 2013, at 22:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > That is a good observation :). > > > > You do not like the underscore, or the "sel" entry? > > > > If you talk about the underscore, I just wanted a way to distinguish > between special variables. You also see the same "notation" in the debugger > (variables like _self and _thisContext). > > > > If you talk about the entry altogether, this part is more experimental. > Some people did not like the printout in the comment, and then I added > _self to show the print string next to it. I am still not decided on > showing it. What do other think about it? > > > > Cheers, > > Doru > > I guess you need self for objects without instance variables. > > I donât like the underscore, every Smalltalker should know about self, > super and thisContext. You could make them bold or italic or gray. > > > > > On Thu, Dec 19, 2013 at 9:57 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > Ah, yes, and I donât like the _self. Why would you want to do that ?? > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 21, 2013

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

by Alexandre Bergel

We are experimenting the same. Would be great to have that fixed for good. Alexandre > Le 20-12-2013 Ã 15:35, "J.F. Rick" <self(a)je77.com> a Ã©crit : > > 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? > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

Dec. 21, 2013

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

by Tudor Girba

Ok, but now I am curious :). Could you translate? Doru On Sat, Dec 21, 2013 at 10:26 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > sorry for this i mixed up the mailing adresses :D > > > On Sat, Dec 21, 2013 at 11:04 AM, dimitris chloupis <thekilon(a)yahoo.co.uk>wrote: > >> ÏÏÎµÎ¹Î»Îµ Î¼Î¿Ï ÏÎ·Î½ ÏÎ¬Î»Î¹ ÏÏÎ¿ 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" >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 21, 2013

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

by kilon alios

sorry for this i mixed up the mailing adresses :D On Sat, Dec 21, 2013 at 11:04 AM, dimitris chloupis <thekilon(a)yahoo.co.uk>wrote: > ÏÏÎµÎ¹Î»Îµ Î¼Î¿Ï ÏÎ·Î½ ÏÎ¬Î»Î¹ ÏÏÎ¿ 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