June 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Remove a dependency (was Re: How to do this in Pharo 2?)

by Paul DeBruicker

In Pharo2 you can hit shift+enter to open the 'spotlight' which will search for classes and method implementors. Start typing the class name into the box at the top right of the window. It will then start to autocomplete. You can press the down arrow key to select the class or method name and hit enter to search for that class or method. Once you hit enter a browser will open on the class or the implementors of the method will be shown. Its pretty handy. On 06/29/2013 04:04 PM, Donald wrote: > On 6/29/2013 7:00 PM, Mariano Martinez Peck wrote: >> Hi Donald, >> >> I guess there should be a ConfigurationOfLog4j (or similar name) that >> defines the versions, the baselines, dependencies, etc. Imagine this >> (similarly) as a ConfigurationMap. So I guess what you have to do is >> to take ConfigurationOfLog4j, edit the necessary #baselineXXX method >> and remove the #requires that brings Bindings-Core. >> >> Torsten, where is the conf? > ok. Where does ConfigurationOfLog4j live? > > Sorry to be dense, but Envy takes care of these things for me day to day. > > -- > Donald [|] > > A bad day in [] is better than a good day in {}

June 29, 2013

Re: [Pharo-users] Remove a dependency (was Re: How to do this in Pharo 2?)

by Donald

On 6/29/2013 7:00 PM, Mariano Martinez Peck wrote: > Hi Donald, > > I guess there should be a ConfigurationOfLog4j (or similar name) that > defines the versions, the baselines, dependencies, etc. Imagine this > (similarly) as a ConfigurationMap. So I guess what you have to do is > to take ConfigurationOfLog4j, edit the necessary #baselineXXX method > and remove the #requires that brings Bindings-Core. > > Torsten, where is the conf? ok. Where does ConfigurationOfLog4j live? Sorry to be dense, but Envy takes care of these things for me day to day. -- Donald [|] A bad day in [] is better than a good day in {}

June 29, 2013

Re: [Pharo-users] trait question

by Camillo Bruni

so let's discuss that on monday with the trait specialists Damien et Sebastian :) On 2013-06-29, at 23:34, Igor Stasenko <siguctua(a)gmail.com> wrote: > yes, i don't know if it good or bad, but i'd rather prefer that traits > applied to Behavior, > but not to Class (which has two entangled behaviors). But maybe for > human comprehension it is better.. > but not for implementing, because it certainly makes model more complex. > > On 29 June 2013 22:52, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> On 2013-06-29, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 29 June 2013 21:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> On Jun 29, 2013, at 8:19 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>>> On 29 June 2013 20:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>> Working on the new class builder I have a hard time figuring out the full trait >>>>>> semantics. >>>>>> >>>>>> If I use a trait on instance side, does that imply that its classTrait on the >>>>>> metaclass? >>>> >>>> No. I do not think so (I will have to think). >>>> Normally Trait and ClassTrait are two different classes. NOw I do not remember if a trait is composed >>>> of a classTrait too. >>>> >>> Trait has 'classTrait' >> >> yes, but the strange part is, that if you use a Trait on the instance-side it >> will automatically install the class trait as well. >> >> ClassDescription subclass: #Class >> uses: TClass >> ... >> >> and the users >> >> TClass users => an IdentitySet(Class) >> TClass classTrait users => an IdentitySet(Class class) >> >> so in this case it implies that when you use a Trait on the instance side it will >> apply also it's classTrait to the class side. So is it ok then to enforce that in >> the new class builder? >> >> Currently you can do the following in the new class builder: >> >> PharoClassInstaller make: [:builder| >> builder >> superclass: Object; >> name: 'Foo'; >> traitComposition: TClass ] >> >> which will explicitely NOT install `TClass classTrait` in `Foo class`. >> Does this behavior make sense? > > > > -- > Best regards, > Igor Stasenko. >

June 29, 2013

Re: [Pharo-users] Remove a dependency (was Re: How to do this in Pharo 2?)

by Donald

On 6/29/2013 6:56 PM, Camillo Bruni wrote: > On 2013-06-30, at 00:47, Donald <dmacq(a)instantiations.com> wrote: > >> On 6/29/2013 4:42 PM, Camillo Bruni wrote: >>> look at String >> #format: >> ok, got that fixed. >> >> how do I remove the log4s dependency on >> >> Bindings-Core-tbn.1? >> >> I don't seen anything in the Monticello browser that lets me unload/unlink/remove etc. > I do not fully get what you want to do. > Where did you get this Bindins-Core-tbn.1 from? It was in the log4s 1.4 version. > > Usually you just load it and see what happens when you run the tests. > Undefined globals will raise DNU's at runtime. > > AFAIK you cannot just exclude certain methods from being loaded with Monticello in Pharo. > Did you check if there isn't a Configuration that will load the dependencies? where is the configuration that loads the dependencies? that's what I can't find. -- Donald [|] A bad day in [] is better than a good day in {}

June 29, 2013

Re: [Pharo-users] Remove a dependency (was Re: How to do this in Pharo 2?)

by Mariano Martinez Peck

Hi Donald, I guess there should be a ConfigurationOfLog4j (or similar name) that defines the versions, the baselines, dependencies, etc. Imagine this (similarly) as a ConfigurationMap. So I guess what you have to do is to take ConfigurationOfLog4j, edit the necessary #baselineXXX method and remove the #requires that brings Bindings-Core. Torsten, where is the conf?

June 29, 2013

Re: [Pharo-users] Remove a dependency (was Re: How to do this in Pharo 2?)

by Camillo Bruni

On 2013-06-30, at 00:47, Donald <dmacq(a)instantiations.com> wrote: > On 6/29/2013 4:42 PM, Camillo Bruni wrote: >> look at String >> #format: > ok, got that fixed. > > how do I remove the log4s dependency on > > Bindings-Core-tbn.1? > > I don't seen anything in the Monticello browser that lets me unload/unlink/remove etc. I do not fully get what you want to do. Where did you get this Bindins-Core-tbn.1 from? Usually you just load it and see what happens when you run the tests. Undefined globals will raise DNU's at runtime. AFAIK you cannot just exclude certain methods from being loaded with Monticello in Pharo. Did you check if there isn't a Configuration that will load the dependencies?

June 29, 2013

Remove a dependency (was Re: How to do this in Pharo 2?)

by Donald

On 6/29/2013 4:42 PM, Camillo Bruni wrote: > look at String >> #format: ok, got that fixed. how do I remove the log4s dependency on Bindings-Core-tbn.1? I don't seen anything in the Monticello browser that lets me unload/unlink/remove etc. Thanks > > On 2013-06-29, at 22:26, Donald <dmacq(a)instantiations.com> wrote: > >> Logs uses a package called Bindings-Core-tbn.1 that has this description: >> /Name: Bindings-Core-tbn.1// >> //Author: tbn// >> //Time: 11 July 2012, 9:46:06.521 am// >> //UUID: 2c28d2f3-610f-a54d-82b1-f421a40394ce// >> //Ancestors: // >> // >> //Initial version from Benoit, see http://lists.gforge.inria.fr/pipermail/pharo-project/2012-July/067412.html/ >> >> It allows me to do things like this: >> >> Transcript show: 'Today is %1' bindWith: 'the first day of the rest of your life'. >> >> Is there a better way to do this in Pharo 2?. An hour of poking around and no joy. >> >> Thanks. >> >> -- >> Donald [|] >> >> A bad day in [] is better than a good day in {} >> > -- Donald [|] A bad day in [] is better than a good day in {}

June 29, 2013

Re: [Pharo-users] trait question

by Igor Stasenko

yes, i don't know if it good or bad, but i'd rather prefer that traits applied to Behavior, but not to Class (which has two entangled behaviors). But maybe for human comprehension it is better.. but not for implementing, because it certainly makes model more complex. On 29 June 2013 22:52, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-06-29, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 29 June 2013 21:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> On Jun 29, 2013, at 8:19 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>>> On 29 June 2013 20:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>> Working on the new class builder I have a hard time figuring out the full trait >>>>> semantics. >>>>> >>>>> If I use a trait on instance side, does that imply that its classTrait on the >>>>> metaclass? >>> >>> No. I do not think so (I will have to think). >>> Normally Trait and ClassTrait are two different classes. NOw I do not remember if a trait is composed >>> of a classTrait too. >>> >> Trait has 'classTrait' > > yes, but the strange part is, that if you use a Trait on the instance-side it > will automatically install the class trait as well. > > ClassDescription subclass: #Class > uses: TClass > ... > > and the users > > TClass users => an IdentitySet(Class) > TClass classTrait users => an IdentitySet(Class class) > > so in this case it implies that when you use a Trait on the instance side it will > apply also it's classTrait to the class side. So is it ok then to enforce that in > the new class builder? > > Currently you can do the following in the new class builder: > > PharoClassInstaller make: [:builder| > builder > superclass: Object; > name: 'Foo'; > traitComposition: TClass ] > > which will explicitely NOT install `TClass classTrait` in `Foo class`. > Does this behavior make sense? -- Best regards, Igor Stasenko.

June 29, 2013

Re: [Pharo-users] trait question

by Camillo Bruni

On 2013-06-29, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 29 June 2013 21:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> On Jun 29, 2013, at 8:19 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 29 June 2013 20:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> Working on the new class builder I have a hard time figuring out the full trait >>>> semantics. >>>> >>>> If I use a trait on instance side, does that imply that its classTrait on the >>>> metaclass? >> >> No. I do not think so (I will have to think). >> Normally Trait and ClassTrait are two different classes. NOw I do not remember if a trait is composed >> of a classTrait too. >> > Trait has 'classTrait' yes, but the strange part is, that if you use a Trait on the instance-side it will automatically install the class trait as well. ClassDescription subclass: #Class uses: TClass ... and the users TClass users => an IdentitySet(Class) TClass classTrait users => an IdentitySet(Class class) so in this case it implies that when you use a Trait on the instance side it will apply also it's classTrait to the class side. So is it ok then to enforce that in the new class builder? Currently you can do the following in the new class builder: PharoClassInstaller make: [:builder| builder superclass: Object; name: 'Foo'; traitComposition: TClass ] which will explicitely NOT install `TClass classTrait` in `Foo class`. Does this behavior make sense?

June 29, 2013

Re: [Pharo-users] How to do this in Pharo 2?

by Camillo Bruni

look at String >> #format: On 2013-06-29, at 22:26, Donald <dmacq(a)instantiations.com> wrote: > Logs uses a package called Bindings-Core-tbn.1 that has this description: > /Name: Bindings-Core-tbn.1// > //Author: tbn// > //Time: 11 July 2012, 9:46:06.521 am// > //UUID: 2c28d2f3-610f-a54d-82b1-f421a40394ce// > //Ancestors: // > // > //Initial version from Benoit, see http://lists.gforge.inria.fr/pipermail/pharo-project/2012-July/067412.html/ > > It allows me to do things like this: > > Transcript show: 'Today is %1' bindWith: 'the first day of the rest of your life'. > > Is there a better way to do this in Pharo 2?. An hour of poking around and no joy. > > Thanks. > > -- > Donald [|] > > A bad day in [] is better than a good day in {} >

June 29, 2013