September 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Esteban Lorenzano

Hi, when fixing with configuration, this is the procedure: 1) you have to copy the configuration into the Inbox (so we keep history). 2) You complete the fields: âConfigurationOfâ and âConfigurationVersionâ. In your case, is: ConfigurationOf = GTPlayground ConfigurationVersion = 1.0.1 3) *If* you have some preload or postload scripts to execute, you can fill the corresponding fields. cheers, Esteban On 30 Sep 2014, at 17:39, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Thanks. > > First bugfix: https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… > > Is there a way to get a diff of the changes introduced by this configuration? (something like when working with slices) > > > Andrei > > On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > new project GTools created in fogbugz :) > Esteban > > > On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> I guess a new category would make sense. >> It would at least make it easy to find and keep track of those bugs related to the GTools >> >> On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> â¦ that :) >> Which means that now we have a long way to polish them until Pharo4 release. >> >> Please test and provide feedback :) >> >> Esteban >> >> Great! >> >> How about a new Project category in fogbugz for GTools >> or should we use just "Tools"? >> >> Nicolai >> > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

Thanks. First bugfix: https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… Is there a way to get a diff of the changes introduced by this configuration? (something like when working with slices) Andrei On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > new project GTools created in fogbugz :) > > Esteban > > > On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > I guess a new category would make sense. > It would at least make it easy to find and keep track of those bugs > related to the GTools > > On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> â¦ that :) >>> Which means that now we have a long way to polish them until Pharo4 >>> release. >>> >>> Please test and provide feedback :) >>> >>> Esteban >>> >> >> Great! >> >> How about a new Project category in fogbugz for GTools >> or should we use just "Tools"? >> >> Nicolai >> > > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Esteban Lorenzano

new project GTools created in fogbugz :) Esteban On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > I guess a new category would make sense. > It would at least make it easy to find and keep track of those bugs related to the GTools > > On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > â¦ that :) > Which means that now we have a long way to polish them until Pharo4 release. > > Please test and provide feedback :) > > Esteban > > Great! > > How about a new Project category in fogbugz for GTools > or should we use just "Tools"? > > Nicolai >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

I guess a new category would make sense. It would at least make it easy to find and keep track of those bugs related to the GTools On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> â¦ that :) >> Which means that now we have a long way to polish them until Pharo4 >> release. >> >> Please test and provide feedback :) >> >> Esteban >> > > Great! > > How about a new Project category in fogbugz for GTools > or should we use just "Tools"? > > Nicolai >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Nicolai Hess

2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > â¦ that :) > Which means that now we have a long way to polish them until Pharo4 > release. > > Please test and provide feedback :) > > Esteban > Great! How about a new Project category in fogbugz for GTools or should we use just "Tools"? Nicolai

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

thanks :) On Tue, Sep 30, 2014 at 4:56 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > done > > On 30 Sep 2014, at 16:06, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > ok. I just need access to PharoExtras :) > > > Andrei > > On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Better put it in PharoExtras. The projects under the Moose team are all >> project repositories. >> >> Doru >> >> On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis <chisvasileandrei(a)gmail.com> >> wrote: >> >>> Simple enough :) >>> I'll create then a project Pharo4Integration in the Moose team and >>> commit everything there. >>> >>> On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba <tudor(a)tudorgirba.com> >>> wrote: >>> >>>> Sure. You just specify a repository. >>>> >>>> Doru >>>> >>>> On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis < >>>> chisvasileandrei(a)gmail.com> wrote: >>>> >>>>> I also like configurations much more but now I need to find a way to >>>>> keep Moose running on both Pharo 3 and 4 :) >>>>> >>>>> Can I say in a version that I want a particular package to be loaded >>>>> form a certain repository? >>>>> >>>>> On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano < >>>>> estebanlm(a)gmail.com> wrote: >>>>> >>>>>> we are moving to configurationsâ¦ conceptually, you *could* give us an >>>>>> SLICE, but a config would be a lot better. >>>>>> >>>>>> Esteban >>>>>> >>>>>> On 30 Sep 2014, at 15:14, Andrei Chis <chisvasileandrei(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> Could I also just provide you with a slice? >>>>>> Right now Moose is still on Pharo 3 and baselines (not versions) are >>>>>> used to load more or less everything. >>>>>> So as soon as I'll commit something incompatible with Pharo 3 it will >>>>>> break Moose. >>>>>> >>>>>> I can also provide a version but then I'll have to commit the changed >>>>>> mcz elsewhere. >>>>>> Not sure which is the best option. >>>>>> >>>>>> @Doru how far are we from moving Moose to Pharo 4? >>>>>> >>>>>> On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano < >>>>>> estebanlm(a)gmail.com> wrote: >>>>>> >>>>>>> remember you will have to give me a 1.0.1 config version :P >>>>>>> >>>>>>> On 30 Sep 2014, at 15:00, Andrei Chis <chisvasileandrei(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> Cool. >>>>>>> >>>>>>> Now I found the first bug :) >>>>>>> Seems that there is a problem with declaring variables in a >>>>>>> playground. Fixing it now >>>>>>> >>>>>>> On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <maxleske(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Oh yeah!! >>>>>>>> >>>>>>>> On 30.09.2014, at 14:51, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>> > â¦ that :) >>>>>>>> > Which means that now we have a long way to polish them until >>>>>>>> Pharo4 release. >>>>>>>> > >>>>>>>> > Please test and provide feedback :) >>>>>>>> > >>>>>>>> > Esteban >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Esteban Lorenzano

done On 30 Sep 2014, at 16:06, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > ok. I just need access to PharoExtras :) > > > Andrei > > On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Better put it in PharoExtras. The projects under the Moose team are all project repositories. > > Doru > > On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Simple enough :) > I'll create then a project Pharo4Integration in the Moose team and commit everything there. > > On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Sure. You just specify a repository. > > Doru > > On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > I also like configurations much more but now I need to find a way to keep Moose running on both Pharo 3 and 4 :) > > Can I say in a version that I want a particular package to be loaded form a certain repository? > > On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > we are moving to configurationsâ¦ conceptually, you *could* give us an SLICE, but a config would be a lot better. > > Esteban > > On 30 Sep 2014, at 15:14, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> Could I also just provide you with a slice? >> Right now Moose is still on Pharo 3 and baselines (not versions) are used to load more or less everything. >> So as soon as I'll commit something incompatible with Pharo 3 it will break Moose. >> >> I can also provide a version but then I'll have to commit the changed mcz elsewhere. >> Not sure which is the best option. >> >> @Doru how far are we from moving Moose to Pharo 4? >> >> On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> remember you will have to give me a 1.0.1 config version :P >> >> On 30 Sep 2014, at 15:00, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >>> Cool. >>> >>> Now I found the first bug :) >>> Seems that there is a problem with declaring variables in a playground. Fixing it now >>> >>> On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <maxleske(a)gmail.com> wrote: >>> Oh yeah!! >>> >>> On 30.09.2014, at 14:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> > â¦ that :) >>> > Which means that now we have a long way to polish them until Pharo4 release. >>> > >>> > Please test and provide feedback :) >>> > >>> > Esteban >>> >>> >>> >> >> > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 30, 2014

need access to PharoExtras :)

by Andrei Chis

username: AndreiChis

Sept. 30, 2014

Re: [Pharo-dev] Nautilus roadmap / icons

by Marcus Denker

On 27 Sep 2014, at 09:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 26 Sep 2014, at 20:44, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> Hi Marcus, >> >> On Thu, Sep 25, 2014 at 11:29 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On 25 Sep 2014, at 23:02, phil(a)highoctane.be wrote: >> >> > Well, the full story is that the decompiler is now gone with Opal. >> > >> There is a decompiler again in Pharo4 >> >> > So, there were 3 in the beginning. So, of course with 2, this becomes a switch. >> > >> > Why no decompiler anymore, for the layman I am? >> > >> The *option* of showing decompiled code in the browser: Honestly, I do not get >> why this was useful, ever. >> >> I can think of three reasons. >> >> 1. mutable literals. using the decompiler is a quick way to check if a literal has been corrupted/modified >> >> 2. if you're working on the decompiler this is convenient >> > > Yes, but all this does not mean that there need to be a button always visible for itâ¦ > (and maybe GTInspector already provides the perfect tool for it? I guess it does: Decompiler > can define a view for CompiledMethod, it is added as a tab, the tabs let you switch easily between code, AST, IR, CM Header and everyone > else who defines an inspector view for the method) In 4.0 #272: -> add gtInspectorDecompilerIn: composite <gtInspectorPresentationOrder: 40> ^ composite smalltalkCode title: 'Decompiled'; smalltalkClass: [ self methodClass ]; display: [ self codeForNoSource ]. to CompiledMethod. Result: instant browser for comparing source vs. decompiled vs. AST vs Bytecode. (I inspect âObject methodsâ).

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

ok. I just need access to PharoExtras :) Andrei On Tue, Sep 30, 2014 at 4:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Better put it in PharoExtras. The projects under the Moose team are all > project repositories. > > Doru > > On Tue, Sep 30, 2014 at 3:39 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> Simple enough :) >> I'll create then a project Pharo4Integration in the Moose team and commit >> everything there. >> >> On Tue, Sep 30, 2014 at 3:34 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Sure. You just specify a repository. >>> >>> Doru >>> >>> On Tue, Sep 30, 2014 at 3:33 PM, Andrei Chis <chisvasileandrei(a)gmail.com >>> > wrote: >>> >>>> I also like configurations much more but now I need to find a way to >>>> keep Moose running on both Pharo 3 and 4 :) >>>> >>>> Can I say in a version that I want a particular package to be loaded >>>> form a certain repository? >>>> >>>> On Tue, Sep 30, 2014 at 3:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com >>>> > wrote: >>>> >>>>> we are moving to configurationsâ¦ conceptually, you *could* give us an >>>>> SLICE, but a config would be a lot better. >>>>> >>>>> Esteban >>>>> >>>>> On 30 Sep 2014, at 15:14, Andrei Chis <chisvasileandrei(a)gmail.com> >>>>> wrote: >>>>> >>>>> Could I also just provide you with a slice? >>>>> Right now Moose is still on Pharo 3 and baselines (not versions) are >>>>> used to load more or less everything. >>>>> So as soon as I'll commit something incompatible with Pharo 3 it will >>>>> break Moose. >>>>> >>>>> I can also provide a version but then I'll have to commit the changed >>>>> mcz elsewhere. >>>>> Not sure which is the best option. >>>>> >>>>> @Doru how far are we from moving Moose to Pharo 4? >>>>> >>>>> On Tue, Sep 30, 2014 at 3:04 PM, Esteban Lorenzano < >>>>> estebanlm(a)gmail.com> wrote: >>>>> >>>>>> remember you will have to give me a 1.0.1 config version :P >>>>>> >>>>>> On 30 Sep 2014, at 15:00, Andrei Chis <chisvasileandrei(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> Cool. >>>>>> >>>>>> Now I found the first bug :) >>>>>> Seems that there is a problem with declaring variables in a >>>>>> playground. Fixing it now >>>>>> >>>>>> On Tue, Sep 30, 2014 at 2:53 PM, Max Leske <maxleske(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Oh yeah!! >>>>>>> >>>>>>> On 30.09.2014, at 14:51, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> > â¦ that :) >>>>>>> > Which means that now we have a long way to polish them until >>>>>>> Pharo4 release. >>>>>>> > >>>>>>> > Please test and provide feedback :) >>>>>>> > >>>>>>> > Esteban >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 30, 2014