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

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

by Yuriy Tymchuk

> On 01 Oct 2014, at 07:37, stepharo <stepharo(a)free.fr> wrote: > > is Kommiter working for you in 40 latest? > Because I get an error tellling to me that it cannot find Applications / Pharo? I was also getting this some time ago. Didnât check since then Uko >

Oct. 1, 2014

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

by Christophe Demarey

Le 1 oct. 2014 Ã 07:37, stepharo a Ã©crit : > is Kommiter working for you in 40 latest? yes, works fine for me

Oct. 1, 2014

Re: [Pharo-dev] GTInspector + Fuel

by Mariano Martinez Peck

On Wed, Oct 1, 2014 at 2:25 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Mariano, > > I am not sure I understand the implication of using addPostMaterializationAction: > in combination with the inspector materialization extension. Where do you > see the opportunity? > > What I thought is the following..... if you are at the inspector level, and you are watching a .fuel it is nice that it materializes the file and then let you inspect the materialized object. However, if the graph was serialized with postMaterializationActions, those would be executed after you click in the inspector. This trick of the postMaterializationActions was used, for example, for when you serialize test failures or debuggers, in order to directly open a new debugger with the materialized stack upon materialization. So.... you are in the inspector, you see a fueled out stack or test failure, you click on it, and you have the debugger opened :) > Cheers, > Doru > > On Tue, Sep 30, 2014 at 10:52 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> That's very nice!!! >> >> >> And that ... together with the ability to define >> #addPostMaterializationAction: is a super awesome combination :) >> >> On Tue, Sep 30, 2014 at 5:17 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> >>> On 30.09.2014, at 22:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> :) >>> >>> Doru >>> >>> >>> On Tue, Sep 30, 2014 at 10:11 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>> wrote: >>> >>>> Hi, >>>> >>>> sorry if this is a known thing, but Iâve just notices this and it made >>>> my day. >>>> >>>> So in GTInspector you can browse filesystem, but when you select a fuel >>>> file, you can press a "plusâ button in top right corner, and it >>>> materialises the object. Amazing. >>>> >>> >>> Hehe ;) Took me 10 minutes on MooseDay (including showing meta info) :D >>> >>> GT rocks! >>> >>> >>>> Uko >>>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- Mariano http://marianopeck.wordpress.com

Oct. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40273 Home: https://github.com/pharo-project/pharo-core

Oct. 1, 2014

[pharo-project/pharo-core] 11e333: 40273

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 11e333080d87e57dd8d889e4088b73ad3b1440bd https://github.com/pharo-project/pharo-core/commit/11e333080d87e57dd8d889e4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-01 (Wed, 01 Oct 2014) Changed paths: A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version101_.st A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version102_.st A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version101_.st A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version102_.st A ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version271_.st A GT-InspectorExtensions-Core.package/extension/CollectionValueHolder/instance/announcer.st M GT-InspectorExtensions-Core.package/extension/Dictionary/instance/gtInspectorItemsIn_.st R GT-InspectorExtensions-Core.package/extension/GLMSystemWindow/instance/gtInspectorOpenTreeIn_.st M GT-InspectorExtensions-Core.package/extension/String/instance/gtInspectorTextIn_.st M GT-Playground.package/GTPlayground.class/instance/accessing/acceptContents_.st M GT-Playground.package/GTPlaygroundPage.class/instance/compatibility-tools/acceptContents_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoPlaygroundRenderer.class/instance/as yet unclassified/workspaceBindingsStrategy.st M Glamour-Morphic-Renderer.package/GLMMorphicSmalltalkCodeRenderer.class/instance/private/workspaceBindingsStrategy.st M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/initialization/initializeInspectButton.st M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/initialization/initializeTextMorph.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script273.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40273.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40273 14123 removed backgroundColor, fixed playgroundpage>>contents https://pharo.fogbugz.com/f/cases/14123 http://files.pharo.org/image/40/40273.zip

Oct. 1, 2014

Re: [Pharo-dev] GTTool bug:

by Marcus Denker

On 01 Oct 2014, at 10:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I think this is the wrong thing to do. We should reimplement the method in the UIManager. > Yes! > Doru > > On Wed, Oct 1, 2014 at 10:30 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > There is an acceptsContents: on GLMSystemWindow that delegates to the model, which in this case is the playground. > > On Wed, Oct 1, 2014 at 10:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > How did you fix it? > > Doru > > On Wed, Oct 1, 2014 at 10:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > I fixed for now the part with acceptsContents: > This should work when the issue is integrated > > UIManager default > edit: 'jlklkjk' > label: 'lkjlkjjkl'. > > On Wed, Oct 1, 2014 at 9:50 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Exactly. > > I created an entry for this: > https://pharo.fogbugz.com/f/cases/14133/UIManager-should-not-overuse-the-wo… > > Cheers, > Doru > > > On Wed, Oct 1, 2014 at 9:20 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 30 Sep 2014, at 20:41, stepharo <stepharo(a)free.fr> wrote: > > > edit: aText label: labelString accept: anAction > > "Open an editor on the given string/text" > > > > ^(Smalltalk tools workspace openLabel: labelString) > > acceptContents: aText; > > acceptAction: anAction; > > yourself. > > > > > > > Yes, we are abusing the workspace for an editor, this is not good. > > We should have an editor that is an editor, not a workspace. > > > -> DNU > > > > UIManager default > > edit: 'jlklkjk' > > label: 'lkjlkjjkl' > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTool bug:

by Tudor Girba

I think this is the wrong thing to do. We should reimplement the method in the UIManager. Doru On Wed, Oct 1, 2014 at 10:30 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > There is an acceptsContents: on GLMSystemWindow that delegates to the > model, which in this case is the playground. > > On Wed, Oct 1, 2014 at 10:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> How did you fix it? >> >> Doru >> >> On Wed, Oct 1, 2014 at 10:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> >> wrote: >> >>> I fixed for now the part with acceptsContents: >>> This should work when the issue is integrated >>> >>> UIManager default >>> edit: 'jlklkjk' >>> label: 'lkjlkjjkl'. >>> >>> On Wed, Oct 1, 2014 at 9:50 AM, Tudor Girba <tudor(a)tudorgirba.com> >>> wrote: >>> >>>> Exactly. >>>> >>>> I created an entry for this: >>>> >>>> https://pharo.fogbugz.com/f/cases/14133/UIManager-should-not-overuse-the-wo… >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On Wed, Oct 1, 2014 at 9:20 AM, Marcus Denker <marcus.denker(a)inria.fr> >>>> wrote: >>>> >>>>> >>>>> On 30 Sep 2014, at 20:41, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>> > edit: aText label: labelString accept: anAction >>>>> > "Open an editor on the given string/text" >>>>> > >>>>> > ^(Smalltalk tools workspace openLabel: labelString) >>>>> > acceptContents: aText; >>>>> > acceptAction: anAction; >>>>> > yourself. >>>>> > >>>>> > >>>>> >>>>> >>>>> Yes, we are abusing the workspace for an editor, this is not good. >>>>> >>>>> We should have an editor that is an editor, not a workspace. >>>>> >>>>> > -> DNU >>>>> > >>>>> > UIManager default >>>>> > edit: 'jlklkjk' >>>>> > label: 'lkjlkjjkl' >>>>> > >>>>> >>>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTool bug:

by Andrei Chis

There is an acceptsContents: on GLMSystemWindow that delegates to the model, which in this case is the playground. On Wed, Oct 1, 2014 at 10:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > How did you fix it? > > Doru > > On Wed, Oct 1, 2014 at 10:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> I fixed for now the part with acceptsContents: >> This should work when the issue is integrated >> >> UIManager default >> edit: 'jlklkjk' >> label: 'lkjlkjjkl'. >> >> On Wed, Oct 1, 2014 at 9:50 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Exactly. >>> >>> I created an entry for this: >>> >>> https://pharo.fogbugz.com/f/cases/14133/UIManager-should-not-overuse-the-wo… >>> >>> Cheers, >>> Doru >>> >>> >>> On Wed, Oct 1, 2014 at 9:20 AM, Marcus Denker <marcus.denker(a)inria.fr> >>> wrote: >>> >>>> >>>> On 30 Sep 2014, at 20:41, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> > edit: aText label: labelString accept: anAction >>>> > "Open an editor on the given string/text" >>>> > >>>> > ^(Smalltalk tools workspace openLabel: labelString) >>>> > acceptContents: aText; >>>> > acceptAction: anAction; >>>> > yourself. >>>> > >>>> > >>>> >>>> >>>> Yes, we are abusing the workspace for an editor, this is not good. >>>> >>>> We should have an editor that is an editor, not a workspace. >>>> >>>> > -> DNU >>>> > >>>> > UIManager default >>>> > edit: 'jlklkjk' >>>> > label: 'lkjlkjjkl' >>>> > >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 1, 2014

Re: [Pharo-dev] GTTool bug:

by Tudor Girba

How did you fix it? Doru On Wed, Oct 1, 2014 at 10:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > I fixed for now the part with acceptsContents: > This should work when the issue is integrated > > UIManager default > edit: 'jlklkjk' > label: 'lkjlkjjkl'. > > On Wed, Oct 1, 2014 at 9:50 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Exactly. >> >> I created an entry for this: >> >> https://pharo.fogbugz.com/f/cases/14133/UIManager-should-not-overuse-the-wo… >> >> Cheers, >> Doru >> >> >> On Wed, Oct 1, 2014 at 9:20 AM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >>> >>> On 30 Sep 2014, at 20:41, stepharo <stepharo(a)free.fr> wrote: >>> >>> > edit: aText label: labelString accept: anAction >>> > "Open an editor on the given string/text" >>> > >>> > ^(Smalltalk tools workspace openLabel: labelString) >>> > acceptContents: aText; >>> > acceptAction: anAction; >>> > yourself. >>> > >>> > >>> >>> >>> Yes, we are abusing the workspace for an editor, this is not good. >>> >>> We should have an editor that is an editor, not a workspace. >>> >>> > -> DNU >>> > >>> > UIManager default >>> > edit: 'jlklkjk' >>> > label: 'lkjlkjjkl' >>> > >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTool bug:

by Andrei Chis

I fixed for now the part with acceptsContents: This should work when the issue is integrated UIManager default edit: 'jlklkjk' label: 'lkjlkjjkl'. On Wed, Oct 1, 2014 at 9:50 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Exactly. > > I created an entry for this: > > https://pharo.fogbugz.com/f/cases/14133/UIManager-should-not-overuse-the-wo… > > Cheers, > Doru > > > On Wed, Oct 1, 2014 at 9:20 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> On 30 Sep 2014, at 20:41, stepharo <stepharo(a)free.fr> wrote: >> >> > edit: aText label: labelString accept: anAction >> > "Open an editor on the given string/text" >> > >> > ^(Smalltalk tools workspace openLabel: labelString) >> > acceptContents: aText; >> > acceptAction: anAction; >> > yourself. >> > >> > >> >> >> Yes, we are abusing the workspace for an editor, this is not good. >> >> We should have an editor that is an editor, not a workspace. >> >> > -> DNU >> > >> > UIManager default >> > edit: 'jlklkjk' >> > label: 'lkjlkjjkl' >> > >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 1, 2014