May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GitFiletree conf for pharo 5

by Yuriy Tymchuk

Yes, sure. No hurry. Thanks! > On 17 May 2015, at 17:32, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 17/05/2015 15:29, Yuriy Tymchuk a Ã©crit : >> Hi, >> >> GitFiletree is not available in the configuration browser of Pharo 5. I usually load if from the meta repo for pharo 4 and it works, but can we get it in pharo 5 meta repo, because itâs a pain to manually load it :) >> >> Uko >> > > Hi Uko, > > I haven't yet started to work on Pharo 5, so I'll have to do that a bit later. Can you wait until the end of next week? > > Regards, > > Thierry >

May 17, 2015

Re: [Pharo-dev] GitFiletree conf for pharo 5

by Thierry Goubier

Le 17/05/2015 15:29, Yuriy Tymchuk a Ã©crit : > Hi, > > GitFiletree is not available in the configuration browser of Pharo 5. I usually load if from the meta repo for pharo 4 and it works, but can we get it in pharo 5 meta repo, because itâs a pain to manually load it :) > > Uko > Hi Uko, I haven't yet started to work on Pharo 5, so I'll have to do that a bit later. Can you wait until the end of next week? Regards, Thierry

May 17, 2015

Re: [Pharo-dev] Manifest class values - instance or class side

by Sergio Fedi

Aye, I will. Although we already changed it in our PackageComments fix. But it's probably better to resolve ir separately as a different case. On the same line, I noted that the PackageManifest and ManifestKernel have instance methods (rejectClasses, rejectRules and ruleConsistencyCheckRuleV1FalsePositive) But those don't make sense if you always use the class. I don't know if that's an issue right now, but I'm pointing it out just in case. PD: I'm having trouble with the site (https://pharo.fogbugz.com/f/) right now. I'll create and resolve it later.

May 17, 2015

Re: [Pharo-dev] Project set up

by Cyril Ferlicot

You can create some .exe, .sh to launch an image with your project. You can check that: http://www.drgeo.eu/ I think that's what you want! On 17 May 2015 at 16:55, valmy roi <roykenvalmy(a)gmail.com> wrote: > Hi, > Is there a way to export a project from pharo? I explain: create a set > up of a project (game for example) so that i can give it to someone > to play, and he will not need to import it in pharo. > If it doesn't exist, it should de created > > -- > Kenfack Valmy-Roi > IngÃ©nieur des travaux en Informatique de Gestion/ Analyste Programmeur > ElÃ¨ve ingÃ©nieur de conception en gÃ©nie logiciel > Institut SupÃ©rieur du Sahel > Email : roykenvalmy(a)gmail.com > Tel: +237 22 11 01 87/ +237 676 94 23 01 / +237 699 04 0612 > -- Cheers Cyril Ferlicot

May 17, 2015

Project set up

by valmy roi

Hi, Is there a way to export a project from pharo? I explain: create a set up of a project (game for example) so that i can give it to someone to play, and he will not need to import it in pharo. If it doesn't exist, it should de created -- Kenfack Valmy-Roi IngÃ©nieur des travaux en Informatique de Gestion/ Analyste Programmeur ElÃ¨ve ingÃ©nieur de conception en gÃ©nie logiciel Institut SupÃ©rieur du Sahel Email : roykenvalmy(a)gmail.com Tel: +237 22 11 01 87/ +237 676 94 23 01 / +237 699 04 0612

May 17, 2015

Re: [Pharo-dev] Getting all classes referenced by a method

by Yuriy Tymchuk

I think that it makes sense to do it on ast level. As you may know Iâm working with SmallLint rules. And in a first place I want to get them working on CompiledMethods. But another issue is that you cannot run the rules on RBMethods or RGMethods. Uko > On 17 May 2015, at 16:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > That is my suggestion, too. See the bug entry. > > Now, we might choose to not do it at the CompiledMethod level, but in RGMethodDefinition. That is why I would like to have a discussion about it. > > Cheers, > Doru > > On Sun, May 17, 2015 at 4:14 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > Can we add an implementation for method and the one for class will reuse it? > > Uko > > Sent from my iPhone > > On 17 May 2015, at 16:01, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > >> Indeed. I took again a look at it, and I found two bugs. The method looks like this: >> >> TBehavior>>referencedClasses >> "Return the set of classes that are directly referenced by my methods" >> | answer | >> answer := Set new. >> self methods do: [ :cm | >> answer addAll: >> ( cm literals select: [ :l | l isKindOf: Association ] thenCollect: #value ) ]. >> ^ answer >> >> >> 1. The last literal of a method because the last literal always points to the class of the method. >> >> Object methods collectAsSet: [ : cm | cm literals last value ] >> ==> "a Set(Object)" >> >> So, we need to ignore the last literal >> >> >> 2. The literals that are Associations can also point to other global literals that are not classes: >> (ASTCache class>>#initialize) literals allButLast >> select: [ :l | l isKindOf: Association ] >> thenCollect: #value >> ==> "{Smalltalk}" >> >> So, a better implementation for a method is: >> >> >> (Object>>#actionMap) literals allButLast >> select: [ :l | l value isKindOf: Class ] >> thenCollect: #value >> >> I opened a bug: >> https://pharo.fogbugz.com/f/cases/15550/TBehavior-referencedClasses-is-wrong <https://pharo.fogbugz.com/f/cases/15550/TBehavior-referencedClasses-is-wrong> >> >> Cheers, >> Doru >> >> >> >> On Sun, May 17, 2015 at 12:24 PM, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> 2015-05-17 11:34 GMT+02:00 stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>>: >> >> >> Le 17/5/15 11:07, Yuriy Tymchuk a Ã©crit : >> Hi, it want to rewrite the SmallLint rule which checks whether an abstract class is referenced. First question is whether the rule is really important, because sometimes there are abstract classes with some utility class methods, so maybe we should check whether they are âinstantiatedâ with #new or #basicNew. >> >> indeed this rule is not really revelant. >> >> >> Now the real question is how do you get all classes referenced by a method. So instead of performing a rule check on a class, do it on a method and find if any of the accessed classes is abstract. >> >> check the literal frame of the methods. When a method refers to a class the class binding is in the literal frame of the compiled method. >> >> There is one method to get all referenced classes by a class >> >> Morph referencedClasses -> MorphLostFocus MorphChanged PolygonMorph SystemWindow IdentityTransform GLMUIThemeExtraIcons RGMethodDefinition GTObjectPrinter ..... >> >> It is defined by TBehavior. >> >> >> >> >> >> >> >> Uko >> >> >> >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

May 17, 2015

Re: [Pharo-dev] Getting all classes referenced by a method

by Tudor Girba

That is my suggestion, too. See the bug entry. Now, we might choose to not do it at the CompiledMethod level, but in RGMethodDefinition. That is why I would like to have a discussion about it. Cheers, Doru On Sun, May 17, 2015 at 4:14 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Can we add an implementation for method and the one for class will reuse > it? > > Uko > > Sent from my iPhone > > On 17 May 2015, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Indeed. I took again a look at it, and I found two bugs. The method looks > like this: > > TBehavior>>referencedClasses > "Return the set of classes that are directly referenced by my methods" > | answer | > answer := Set new. > self methods do: [ :cm | > answer addAll: > ( cm literals select: [ :l | l isKindOf: Association ] thenCollect: #value > ) ]. > ^ answer > > > 1. The last literal of a method because the last literal always points to > the class of the method. > > Object methods collectAsSet: [ : cm | cm literals last value ] > ==> "a Set(Object)" > > So, we need to ignore the last literal > > > 2. The literals that are Associations can also point to other global > literals that are not classes: > (ASTCache class>>#initialize) literals allButLast > select: [ :l | l isKindOf: Association ] > thenCollect: #value > ==> "{Smalltalk}" > > So, a better implementation for a method is: > > > (Object>>#actionMap) literals *allButLast* > select: [ :l | l *value* isKindOf: *Class* ] > thenCollect: #value > > I opened a bug: > > https://pharo.fogbugz.com/f/cases/15550/TBehavior-referencedClasses-is-wrong > > Cheers, > Doru > > > > On Sun, May 17, 2015 at 12:24 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> >> >> 2015-05-17 11:34 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >>> >>> >>> Le 17/5/15 11:07, Yuriy Tymchuk a Ã©crit : >>> >>>> Hi, it want to rewrite the SmallLint rule which checks whether an >>>> abstract class is referenced. First question is whether the rule is really >>>> important, because sometimes there are abstract classes with some utility >>>> class methods, so maybe we should check whether they are âinstantiatedâ >>>> with #new or #basicNew. >>>> >>> >>> indeed this rule is not really revelant. >>> >>> >>>> Now the real question is how do you get all classes referenced by a >>>> method. So instead of performing a rule check on a class, do it on a method >>>> and find if any of the accessed classes is abstract. >>>> >>> >>> check the literal frame of the methods. When a method refers to a class >>> the class binding is in the literal frame of the compiled method. >>> >> >> There is one method to get all referenced classes by a class >> >> Morph referencedClasses -> MorphLostFocus MorphChanged PolygonMorph >> SystemWindow IdentityTransform GLMUIThemeExtraIcons RGMethodDefinition >> GTObjectPrinter ..... >> >> It is defined by TBehavior. >> >> >> >> >> >> >>> >>> >>>> Uko >>>> >>>> >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > -- www.tudorgirba.com "Every thing has its own flow"

May 17, 2015

Re: [Pharo-dev] [Pharo-users] [OT] Pharo pi machine

by Tudor Girba

Really cool. I just do not understand what is the purpose of the pink marker :). Cheers, Doru On Sun, May 17, 2015 at 2:26 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Got my Raspberry Pi B+ with a TontecÂ® 3.5 touch screen display > to bootstrap into Pharo. > > The Raspberry Pi from CI (https://ci.inria.fr/pharo/view/RaspberryPi/) > worked out of the box on Raspbian. Nice! > -- www.tudorgirba.com "Every thing has its own flow"

May 17, 2015

Re: [Pharo-dev] Getting all classes referenced by a method

by Yuriy Tymchuk

Can we add an implementation for method and the one for class will reuse it? Uko Sent from my iPhone > On 17 May 2015, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Indeed. I took again a look at it, and I found two bugs. The method looks like this: > > TBehavior>>referencedClasses > "Return the set of classes that are directly referenced by my methods" > | answer | > answer := Set new. > self methods do: [ :cm | > answer addAll: > ( cm literals select: [ :l | l isKindOf: Association ] thenCollect: #value ) ]. > ^ answer > > > 1. The last literal of a method because the last literal always points to the class of the method. > > Object methods collectAsSet: [ : cm | cm literals last value ] > ==> "a Set(Object)" > > So, we need to ignore the last literal > > > 2. The literals that are Associations can also point to other global literals that are not classes: > (ASTCache class>>#initialize) literals allButLast > select: [ :l | l isKindOf: Association ] > thenCollect: #value > ==> "{Smalltalk}" > > So, a better implementation for a method is: > > > (Object>>#actionMap) literals allButLast > select: [ :l | l value isKindOf: Class ] > thenCollect: #value > > I opened a bug: > https://pharo.fogbugz.com/f/cases/15550/TBehavior-referencedClasses-is-wrong > > Cheers, > Doru > > > >> On Sun, May 17, 2015 at 12:24 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> >> 2015-05-17 11:34 GMT+02:00 stepharo <stepharo(a)free.fr>: >>> >>> >>> Le 17/5/15 11:07, Yuriy Tymchuk a Ã©crit : >>>> Hi, it want to rewrite the SmallLint rule which checks whether an abstract class is referenced. First question is whether the rule is really important, because sometimes there are abstract classes with some utility class methods, so maybe we should check whether they are âinstantiatedâ with #new or #basicNew. >>> >>> indeed this rule is not really revelant. >>> >>>> >>>> Now the real question is how do you get all classes referenced by a method. So instead of performing a rule check on a class, do it on a method and find if any of the accessed classes is abstract. >>> >>> check the literal frame of the methods. When a method refers to a class the class binding is in the literal frame of the compiled method. >> >> There is one method to get all referenced classes by a class >> >> Morph referencedClasses -> MorphLostFocus MorphChanged PolygonMorph SystemWindow IdentityTransform GLMUIThemeExtraIcons RGMethodDefinition GTObjectPrinter ..... >> >> It is defined by TBehavior. >> >> >> >> >> >>> >>>> >>>> Uko > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

May 17, 2015

Re: [Pharo-dev] [Ann] System monitoring for pharo images

by Tudor Girba

Indeed, this is ingenious. And yet, so straightforward :) Doru On Sun, May 17, 2015 at 3:51 PM, Ben Coman <btc(a)openinworld.com> wrote: > Thanks for sharing. Running a Zinc server in an insightful way to provide > data to an external monitoring tool. > > cheers -ben > > On Sun, May 17, 2015 at 2:03 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> Thanks for this!! >> Phil >> Le 17 mai 2015 01:49, "Norbert Hartl" <norbert(a)hartl.name> a Ã©crit : >> >>> Finally I've found some time to release some of my code I've been using >>> the last years. It is a project around system monitoring. It defines system >>> parameters to watch and integrates them with popular tools like munin, >>> monit and nagios/icinga/... As an example the following picture shows the >>> monitoring of the vm memory over a day. >>> >>> >>> >>> System monitoring is basically about monitoring system parameters in >>> order to send alerts when thresholds are exceeded or to plot graphs that >>> enables one to estimate further progression of image behaviour. >>> >>> The code is here >>> >>> http://smalltalkhub.com/#!/~NorbertHartl/Monitoring >>> >>> and an introduction article (more will follow) to it is here >>> >>> >>> http://norbert.hartl.name/blog/2015/05/16/system-monitoring-for-pharo-image… >>> >>> Feedback is welcomed! >>> >>> Hopy you enjoy it. And bug me if you have questions or something is not >>> working. >>> >>> Norbert >>> >>> > -- www.tudorgirba.com "Every thing has its own flow"

May 17, 2015