- Pharo-dev - lists.pharo.org

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

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