Re: [Pharo-dev] GTPlayground/Inspector print it

Hi, The main goal of the "print it” action is to expose printString (not asString). It certainly can be conceivable to show different representations in the popup window, but right now, there is no mechanism for this. As Clement says, printString can have all sorts of usages, so until we have s

Re: [Pharo-dev] GTPlayground/Inspector print it

Hi, The result of DoIts can be executed as another DoIt to get the same result. I use this all the time. Some tools also use this. With your change it is not possible to execute the DoIt result anymore. Regards On Wed, Aug 17, 2016 at 10:01 AM, Peter Uhnák wrote: > Hi, > > does the print-it o

[Pharo-dev] GTPlayground/Inspector print it

Hi, does the print-it option always use only asString (or whatever it actually uses), or can it be modified in some way? I would like to modify it a bit, because for big numbers the default one is not easy to read, e.g. ​instead, I would like to see this ​It gives much better idea of the scal

Re: [Pharo-dev] GTPlayground cache

Done. It will be available in the next GT release. Doru On Thu, Dec 4, 2014 at 4:02 PM, Marcus Denker wrote: > > On 04 Dec 2014, at 15:46, Marcus Denker wrote: > > > On 04 Dec 2014, at 15:42, Tudor Girba wrote: > > Aha. So, that's a bug, right? > > > I think Playground needs to be resetted on

Re: [Pharo-dev] GTPlayground cache

> On 04 Dec 2014, at 15:46, Marcus Denker wrote: > > >> On 04 Dec 2014, at 15:42, Tudor Girba > > wrote: >> >> Aha. So, that's a bug, right? >> > > I think Playground needs to be resetted on #cleanUpForRelease. > > Else the image on the server thinks that it alr

Re: [Pharo-dev] GTPlayground cache

> On 04 Dec 2014, at 15:42, Tudor Girba wrote: > > Aha. So, that's a bug, right? > I think Playground needs to be resetted on #cleanUpForRelease. Else the image on the server thinks that it already has a playground file. > Doru > > On Thu, Dec 4, 2014 at 3:32 PM, Nicolai Hess

Re: [Pharo-dev] GTPlayground cache

Aha. So, that's a bug, right? Doru On Thu, Dec 4, 2014 at 3:32 PM, Nicolai Hess wrote: > No code change, but prior to that version, a fresh image would read all > the play-cache files. > And the current image (40395 for example) just shows what already in its > history, not the > contents writt

Re: [Pharo-dev] GTPlayground cache

> On 04 Dec 2014, at 15:32, Nicolai Hess wrote: > > No code change, but prior to that version, a fresh image would read all the > play-cache files. > And the current image (40395 for example) just shows what already in its > history, not the > contents written into play-cache from the prior us

Re: [Pharo-dev] GTPlayground cache

No code change, but prior to that version, a fresh image would read all the play-cache files. And the current image (40395 for example) just shows what already in its history, not the contents written into play-cache from the prior used images. nicolai 2014-12-04 9:45 GMT+01:00 Tudor Girba : > W

Re: [Pharo-dev] GTPlayground cache

Why not? Was there a change in the Pharo image? (I do not have access to the code right now) Doru On Thu, Dec 4, 2014 at 8:57 AM, Nicolai Hess wrote: > Since 40393 the play-cache is not read when you open the first > GTPlayground in a fresh image. > > > -- www.tudorgirba.com "Every thing ha

[Pharo-dev] GTPlayground cache

Since 40393 the play-cache is not read when you open the first GTPlayground in a fresh image.

Re: [Pharo-dev] GTPlayground wrong cursor position

> Thank you. > It looks like the cursor positioning and syntax highlighing happens in > different processes, right? > yes, and the cursor bounds are not updated correctly after the highlighting process has finished. I’ve found the fix :) Thanks for reporting. Cheers Alain > > On 3 oct. 2014,

Re: [Pharo-dev] GTPlayground wrong cursor position

Am 03.10.2014 07:37 schrieb "Alain Plantec" : > > a Rubric issue I guess. > I will have a look. > Cheers > Alain > Thank you. It looks like the cursor positioning and syntax highlighing happens in different processes, right? > On 3 oct. 2014, at 07:25, Tudor Girba wrote: > > > I do not know :( >

Re: [Pharo-dev] GTPlayground wrong cursor position

a Rubric issue I guess. I will have a look. Cheers Alain On 3 oct. 2014, at 07:25, Tudor Girba wrote: > I do not know :( > > Doru > > On Thu, Oct 2, 2014 at 11:46 PM, Nicolai Hess wrote: > Someone knows why this happens ? > Sometimes the cursor is at the wrong textposition. At least > it loo

Re: [Pharo-dev] GTPlayground wrong cursor position

I do not know :( Doru On Thu, Oct 2, 2014 at 11:46 PM, Nicolai Hess wrote: > Someone knows why this happens ? > Sometimes the cursor is at the wrong textposition. At least > it looks like that. Newly entered characters are on the right position. > (see screenshot ) > > -- www.tudorgirba.com

[Pharo-dev] GTPlayground wrong cursor position

Someone knows why this happens ? Sometimes the cursor is at the wrong textposition. At least it looks like that. Newly entered characters are on the right position. (see screenshot )

Re: [Pharo-dev] GTPlayground Play Button Semantics

I know what it was :). I was asking what would the goal be of an explorer now. Doru On Wed, Oct 1, 2014 at 10:39 PM, Esteban Lorenzano wrote: > it was the tree-shaped inspector, it does not have sense anymore with the > new inspector (since everything is rolled into one). > > > On 01 Oct 2014,

Re: [Pharo-dev] GTPlayground Play Button Semantics

it was the tree-shaped inspector, it does not have sense anymore with the new inspector (since everything is rolled into one). > On 01 Oct 2014, at 22:33, Tudor Girba wrote: > > What is explorer? > > Doru > > On Wed, Oct 1, 2014 at 10:12 PM, stepharo > wrote: > Alex

Re: [Pharo-dev] GTPlayground Play Button Semantics

The play symbol is also used for run. That is why we used that icon. But, we can change it. Ideas? Btw, all the icons used in GT and Moose are drawn by me and licensed under CC Attribution: https://github.com/girba/mooseart Cheers, Doru On Wed, Oct 1, 2014 at 10:12 PM, stepharo wrote: > Alex

Re: [Pharo-dev] GTPlayground Play Button Semantics

What is explorer? Doru On Wed, Oct 1, 2014 at 10:12 PM, stepharo wrote: > Alex > > play looks like flash or music not like executing. > > We all complain that smalltalk is weak and that people can make silly > statements like > Java is compiled and Smalltalk intepreted (I read that in the >

Re: [Pharo-dev] GTPlayground Play Button Semantics

Ok, I will try to explain again: Cmd+i means inspect. When I am in a class browser, it means that the inspector windows opens up. But, when I am in the inspector, it can simply mean open a new pane to the right. Then if you explicitly want to open a window you use an imperative Inspect that we ca

Re: [Pharo-dev] GTPlayground Play Button Semantics

Alex play looks like flash or music not like executing. We all complain that smalltalk is weak and that people can make silly statements like Java is compiled and Smalltalk intepreted (I read that in the lecture)!!! But this is our fault. In my book you will not see evaluating an express

Re: [Pharo-dev] GTPlayground Play Button Semantics

On 1/10/14 16:55, Tudor Girba wrote: Cmd+g sounds like fun :). The other thing could be to have cmd+i as a replacement for cmd+o when you are in the inspector. When outside, Cmd+i would spawn an inspector window if the surrounding browser does not support in-place inspection (like the playgr

Re: [Pharo-dev] GTPlayground Play Button Semantics

On 1/10/14 16:06, Esteban Lorenzano wrote: and btw, what about remap cmd+o to cmd+e (like “execute”) ? + 1 and rename open to execute! Esteban On 01 Oct 2014, at 16:05, Sven Van Caekenberghe > wrote: On 01 Oct 2014, at 16:00, Andrei Chis

Re: [Pharo-dev] GTPlayground Play Button Semantics

Open is not a good name. I want to execute something not opening it. I would never think that open is executing an expression and inspecting the result. Stef On 1/10/14 16:05, Sven Van Caekenberghe wrote: On 01 Oct 2014, at 16:00, Andrei Chis wrote: On Wed, Oct 1, 2014 at 3:14 PM, Sven Va

Re: [Pharo-dev] GTPlayground Play Button Semantics

Process can always be enhanced, of course. But in fact what we did now was just to formalise what was already happening (with Zinc, for example). so we can continue enhancing it from here. about your fears: - all sub-projects will be (we still need to move some there) under “Pharo” umbrella,

Re: [Pharo-dev] GTPlayground Play Button Semantics

cmd+e does not look like to be more explicit to me. Something that I find a little bit confusing, is “play” vs “open”. The button is a play button. But in the menu, it says “open”. Why not being consistent with “play”? Alexandre On Oct 1, 2014, at 7:06 AM, Esteban Lorenzano wrote: > and btw,

Re: [Pharo-dev] GTPlayground Play Button Semantics

Le 1 oct. 2014 à 16:55, Tudor Girba a écrit : > Cmd+g sounds like fun :). > > The other thing could be to have cmd+i as a replacement for cmd+o when you > are in the inspector. When outside, Cmd+i would spawn an inspector window if > the surrounding browser does not support in-place inspection

Re: [Pharo-dev] GTPlayground Play Button Semantics

Hi Sven, Thanks a lot for these questions. Please keep them coming. These first impressions are really important because we have the opportunity to evolve. @Everyone: if you see me or Andrei providing arguments is not to say that we want to be right, but simply to show what we took into considera

Re: [Pharo-dev] GTPlayground Play Button Semantics

Cmd+g sounds like fun :). The other thing could be to have cmd+i as a replacement for cmd+o when you are in the inspector. When outside, Cmd+i would spawn an inspector window if the surrounding browser does not support in-place inspection (like the playground). To force inspect in a new window we

Re: [Pharo-dev] GTPlayground Play Button Semantics

so far, we want to keep cmd+o to open tools. then what about cmd+g for “cmd+go” (and as Guille says, an internal joke for “cmd+gDoit”) :P Esteban > On 01 Oct 2014, at 16:15, Andrei Chis wrote: > > If we want to keep cmd+o for opening the tools then it make sense to use > cmd+e. > Just it c

Re: [Pharo-dev] GTPlayground Play Button Semantics

If we want to keep cmd+o for opening the tools then it make sense to use cmd+e. Just it could be a little confusing because cmd+e was already user before to open the explorer. We wanted a new shortcut to avoid this confusion. But I am not against using cmd+e On Wed, Oct 1, 2014 at 4:06 PM, Esteba

Re: [Pharo-dev] GTPlayground Play Button Semantics

and btw, what about remap cmd+o to cmd+e (like “execute”) ? Esteban > On 01 Oct 2014, at 16:05, Sven Van Caekenberghe wrote: > > > On 01 Oct 2014, at 16:00, Andrei Chis > wrote: > >> >> >> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe wrote: >> W

Re: [Pharo-dev] GTPlayground Play Button Semantics

On 01 Oct 2014, at 16:00, Andrei Chis wrote: > > > On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe wrote: > Was it a conscious decision to make the GTPlayground Play button act as 'play > all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting tha

Re: [Pharo-dev] GTPlayground Play Button Semantics

On Wed, Oct 1, 2014 at 4:00 PM, Andrei Chis wrote: > Does this seem ok to you? makes perfect sense to me. Toolbar is for global stuff, context menu for contextual stuff. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without lo

Re: [Pharo-dev] GTPlayground Play Button Semantics

On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe wrote: > Was it a conscious decision to make the GTPlayground Play button act as > 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play > it'. A works

Re: [Pharo-dev] GTPlayground Play Button Semantics

+1 On Wed, Oct 1, 2014 at 10:14 AM, Sven Van Caekenberghe wrote: > Was it a conscious decision to make the GTPlayground Play button act as > 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play > it'. A

[Pharo-dev] GTPlayground Play Button Semantics

Was it a conscious decision to make the GTPlayground Play button act as 'play all' (evaluate the whole workspace contents) ? If so, why ? I find it quite limiting that I cannot select some expression and 'play it'. A workspace/playground is like a notebook containing lots of different things.

Re: [Pharo-dev] GTPlayground

Thanks. Indeed, we had two mistakes. I just solved the first one. Please, just ignore the second one for now. We will solve it in a week time when we will have the Moose Dojo in Bern. Cheers, Doru On Mon, Feb 24, 2014 at 10:51 PM, Alejandro Infante < alejandroinfant...@gmail.com> wrote: > Jus

Re: [Pharo-dev] GTPlayground

Grrr…. Syndrome of having tools not adequate to package application. Pity. Alexandre On Feb 24, 2014, at 6:51 PM, Alejandro Infante wrote: > Just tried to copy and paste the script to load the GTPlayground on a clean > Pharo 3.0 image and got this warning: > > -

Re: [Pharo-dev] GTPlayground

Just tried to copy and paste the script to load the GTPlayground on a clean Pharo 3.0 image and got this warning: - This package depends on the following classes: EyeContextInspector RTView You must resolve these dependenc

Re: [Pharo-dev] GTPlayground

> Can this be tested on a vanilla Pharo 3.0 image? Yes. http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed The following script should work: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; configuration; load. (Smalltalk globals at:

Re: [Pharo-dev] GTPlayground

Can this be tested on a vanilla Pharo 3.0 image? I still don't get the "moose image" vs "pharo image" separation. I thought Moose was installable, as any other package is :) Regards! Esteban A. Maringolo 2014-02-24 17:59 GMT-03:00 Alexandre Bergel : > Hi! > > Now I am back from holidays, I am c

[Pharo-dev] GTPlayground

Hi! Now I am back from holidays, I am catching up with what happens during that February. My first surprise is GTPlayground, packaged with the Moose image. This is really cool stuff. I have never thought that the workspace could be such a primitive tool. GTPlayground greatly enhances my workfl