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

playground size

by Christophe Demarey

Hi, First I need to say, I love the new GT tools. It really goes a step further. I just wanted to say that I find the Playground window quite big (at least 1/4 of the whole Pharo window). I understand that the size is bigger than a simple workspace to be able to display panes after clicking play but if you just need to evaluate ()do-it, print-it) some code, it is over-sized. Would it be possible to have a default window size smaller and resize automatically if you need to display an inspector pane? Regards, Christophe.

Oct. 3, 2014

Re: [Pharo-dev] First additions to GT-Inspector

by Andrei Chis

I'll make a new version to integrate. Cheers, Andrei On Fri, Oct 3, 2014 at 3:52 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Done! > > Doru > > On Fri, Oct 3, 2014 at 3:25 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> >> On 03 Oct 2014, at 15:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> > Great. I checked it quickly and it looks great. I added you to the >> Moose team. Could you please commit directly in the repo? >> >> Done, you'll have to merge my version since it is two commits behind. >> >> > Doru >> > >> > On Fri, Oct 3, 2014 at 3:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > I made my first additions/changes to GT-Inspector: >> > >> > === >> > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.54 >> > Author: SvenVanCaekenberghe >> > Time: 3 October 2014, 3:03:17.252107 pm >> > UUID: 853cfe8d-314c-4eac-ad67-8c6eff2b4f83 >> > Ancestors: GT-InspectorExtensions-Core-TudorGirba.53 >> > >> > Customized GT-Inspector for Integer, Float and Character >> > === >> > >> > MCZ attached: >> > >> > >> > >> > >> > I made it so that 'State' shows slots only (if any) and takes >> precedence. >> > >> > I added an 'Integer' tab to Integer with decimal, hex, octal, binary >> and optional character aspects. >> > >> > I added a 'Float' tab to Float with (binary, base 2) significant and >> exponent (self = significant * (2 ** exponent)) [the old sign field was not >> needed since significant is signed already), while making the 'State' show >> the 2 indexed slots (which is more correct IMHO). >> > >> > I added a 'Character' tab with self, codepoint and unicode aspects. >> > >> > Obviously this has to be iterated upon. I am already very happy that I >> could figure out how to do this. Much more from the old Eye inspectors will >> follow. >> > >> > Sven >> > >> > PS1: Implementing this, I sense that we might need an option so that a >> field can show some label for its value, while clicking further on it would >> continue on something else (obviously related), differently field by field. >> > >> > PS2: Is is necessary/useful for the States fields in >> #gtInspectorVariableValuePairs to be a Set instead of something that >> preserves the order ? >> > >> > >> > >> > -- >> > www.tudorgirba.com >> > >> > "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 3, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 3, 2014

[pharo-project/pharo-core] 3ad5e4: 40280

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3ad5e446a607564ae9c5a653681812e861b32240 https://github.com/pharo-project/pharo-core/commit/3ad5e446a607564ae9c5a653… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-03 (Fri, 03 Oct 2014) Changed paths: A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version104_.st A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version104_.st A ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version273_.st R GT-InspectorExtensions-Core.package/extension/CollectionValueHolder/instance/announcer.st R GT-InspectorExtensions-Core.package/extension/CompiledMethod/instance/gtDisplayOn_.st R Glamour-Helpers.package/extension/Boolean/instance/glamourValueWithArgs_.st M Glamour-Morphic-Theme.package/GLMWhitespaceTheme.class/instance/private/glamorousThickBorderFor_.st A Glamour-Tests-Rubric.package/GLMRubricTextMorphicTest.class/instance/as yet unclassified/expectedFailures.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script280.st M ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40279.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40280.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40280 14145 GTools version 1.0.4 https://pharo.fogbugz.com/f/cases/14145 http://files.pharo.org/image/40/40280.zip

Oct. 3, 2014

Re: [Pharo-dev] First additions to GT-Inspector

by Tudor Girba

Done! Doru On Fri, Oct 3, 2014 at 3:25 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 03 Oct 2014, at 15:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Great. I checked it quickly and it looks great. I added you to the Moose > team. Could you please commit directly in the repo? > > Done, you'll have to merge my version since it is two commits behind. > > > Doru > > > > On Fri, Oct 3, 2014 at 3:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > I made my first additions/changes to GT-Inspector: > > > > === > > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.54 > > Author: SvenVanCaekenberghe > > Time: 3 October 2014, 3:03:17.252107 pm > > UUID: 853cfe8d-314c-4eac-ad67-8c6eff2b4f83 > > Ancestors: GT-InspectorExtensions-Core-TudorGirba.53 > > > > Customized GT-Inspector for Integer, Float and Character > > === > > > > MCZ attached: > > > > > > > > > > I made it so that 'State' shows slots only (if any) and takes precedence. > > > > I added an 'Integer' tab to Integer with decimal, hex, octal, binary and > optional character aspects. > > > > I added a 'Float' tab to Float with (binary, base 2) significant and > exponent (self = significant * (2 ** exponent)) [the old sign field was not > needed since significant is signed already), while making the 'State' show > the 2 indexed slots (which is more correct IMHO). > > > > I added a 'Character' tab with self, codepoint and unicode aspects. > > > > Obviously this has to be iterated upon. I am already very happy that I > could figure out how to do this. Much more from the old Eye inspectors will > follow. > > > > Sven > > > > PS1: Implementing this, I sense that we might need an option so that a > field can show some label for its value, while clicking further on it would > continue on something else (obviously related), differently field by field. > > > > PS2: Is is necessary/useful for the States fields in > #gtInspectorVariableValuePairs to be a Set instead of something that > preserves the order ? > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 3, 2014

Re: [Pharo-dev] About ways to participate in community and general negativity

by phil＠highoctane.be

On Fri, Oct 3, 2014 at 3:23 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2014-10-03 8:44 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > Please people, we (the pharo âcoreâ team) cannot do everything. > > We do not have the manpower or the resources to hire manpower. > > We would like, but we just do not have the resources > > (is already a blessing that we can work on this, for now: INRIA is > paying, > > but what it pays is *research*, not âpharo the languageâ, so this is a > collateral advantageâ¦.) > > > So, having an OPEN SOURCE project, with limited resources means that > there is a lot of things that depend on the community. > > It depends on the community not just to fix, but to enlarge the > ecosystem in general too. > > It is a matter of tolerance and patience. > > You keep doing your great job, but accept that we, outside of the > internal, core, revolutionary research being made, might have mundane > necessities. That on the daily basis have more importance than a > futuristic 128bit manycore vm that kicks JVM's ass :D > Same boat here. > > > So, I refuse to believe that we cannot be a cool and helpful community. > > We are. > We are indeed. > Email sometimes is counterproductive to the health of the > communication. It's like a fence between us. > And as the saying, transliterated, goes: "We're like dogs barking at > both sides of the fence that when together they smell at each other > and waggle their tails." :) > We should Hangout more. > > > In conclusion: not helping does not help :) > > Please consider than USING Pharo is a way to contribute to it. > Even if you had infinite manpower but no one uses it, it would be > worthless. > +1 > > > Esteban, still grateful of belonging to this community > ditto :) > ditto :) > > Regards! > > Peace, Phil

Oct. 3, 2014

Re: [Pharo-dev] ZnEasy and post:data:

by Benjamin Pollack

On Thu, Oct 2, 2014, at 01:28 AM, Sven Van Caekenberghe wrote: > ZnClient is your friend (it is a builder) : > > ZnClient new > url: 'http://some/thing'; > formAt: #foo put: #bar; > formAt: 'baz' put: 'quux'; > post. > Ah, that's indeed perfect. I think I discounted ZnClient initially because I was thinking of it being primarily useful for pipelined operations, but your proposal is *way* cleaner, even if I throw beOneShot in there. Thanks for the pointer. --Benjamin

Oct. 3, 2014

Re: [Pharo-dev] First additions to GT-Inspector

by Sven Van Caekenberghe

On 03 Oct 2014, at 15:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Great. I checked it quickly and it looks great. I added you to the Moose team. Could you please commit directly in the repo? Done, you'll have to merge my version since it is two commits behind. > Doru > > On Fri, Oct 3, 2014 at 3:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I made my first additions/changes to GT-Inspector: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.54 > Author: SvenVanCaekenberghe > Time: 3 October 2014, 3:03:17.252107 pm > UUID: 853cfe8d-314c-4eac-ad67-8c6eff2b4f83 > Ancestors: GT-InspectorExtensions-Core-TudorGirba.53 > > Customized GT-Inspector for Integer, Float and Character > === > > MCZ attached: > > > > > I made it so that 'State' shows slots only (if any) and takes precedence. > > I added an 'Integer' tab to Integer with decimal, hex, octal, binary and optional character aspects. > > I added a 'Float' tab to Float with (binary, base 2) significant and exponent (self = significant * (2 ** exponent)) [the old sign field was not needed since significant is signed already), while making the 'State' show the 2 indexed slots (which is more correct IMHO). > > I added a 'Character' tab with self, codepoint and unicode aspects. > > Obviously this has to be iterated upon. I am already very happy that I could figure out how to do this. Much more from the old Eye inspectors will follow. > > Sven > > PS1: Implementing this, I sense that we might need an option so that a field can show some label for its value, while clicking further on it would continue on something else (obviously related), differently field by field. > > PS2: Is is necessary/useful for the States fields in #gtInspectorVariableValuePairs to be a Set instead of something that preserves the order ? > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 3, 2014

Re: [Pharo-dev] About ways to participate in community and general negativity

by Esteban A. Maringolo

2014-10-03 8:44 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Please people, we (the pharo âcoreâ team) cannot do everything. > We do not have the manpower or the resources to hire manpower. > We would like, but we just do not have the resources > (is already a blessing that we can work on this, for now: INRIA is paying, > but what it pays is *research*, not âpharo the languageâ, so this is a collateral advantageâ¦.) > So, having an OPEN SOURCE project, with limited resources means that there is a lot of things that depend on the community. > It depends on the community not just to fix, but to enlarge the ecosystem in general too. It is a matter of tolerance and patience. You keep doing your great job, but accept that we, outside of the internal, core, revolutionary research being made, might have mundane necessities. That on the daily basis have more importance than a futuristic 128bit manycore vm that kicks JVM's ass :D > So, I refuse to believe that we cannot be a cool and helpful community. We are. Email sometimes is counterproductive to the health of the communication. It's like a fence between us. And as the saying, transliterated, goes: "We're like dogs barking at both sides of the fence that when together they smell at each other and waggle their tails." :) > In conclusion: not helping does not help :) Please consider than USING Pharo is a way to contribute to it. Even if you had infinite manpower but no one uses it, it would be worthless. > Esteban, still grateful of belonging to this community ditto :) Regards!

Oct. 3, 2014

Re: [Pharo-dev] First additions to GT-Inspector

by Tudor Girba

Great. I checked it quickly and it looks great. I added you to the Moose team. Could you please commit directly in the repo? Doru On Fri, Oct 3, 2014 at 3:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I made my first additions/changes to GT-Inspector: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.54 > Author: SvenVanCaekenberghe > Time: 3 October 2014, 3:03:17.252107 pm > UUID: 853cfe8d-314c-4eac-ad67-8c6eff2b4f83 > Ancestors: GT-InspectorExtensions-Core-TudorGirba.53 > > Customized GT-Inspector for Integer, Float and Character > === > > MCZ attached: > > > > > I made it so that 'State' shows slots only (if any) and takes precedence. > > I added an 'Integer' tab to Integer with decimal, hex, octal, binary and > optional character aspects. > > I added a 'Float' tab to Float with (binary, base 2) significant and > exponent (self = significant * (2 ** exponent)) [the old sign field was not > needed since significant is signed already), while making the 'State' show > the 2 indexed slots (which is more correct IMHO). > > I added a 'Character' tab with self, codepoint and unicode aspects. > > Obviously this has to be iterated upon. I am already very happy that I > could figure out how to do this. Much more from the old Eye inspectors will > follow. > > Sven > > PS1: Implementing this, I sense that we might need an option so that a > field can show some label for its value, while clicking further on it would > continue on something else (obviously related), differently field by field. > > PS2: Is is necessary/useful for the States fields in > #gtInspectorVariableValuePairs to be a Set instead of something that > preserves the order ? > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 3, 2014