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.
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess. On 03 Oct 2014, at 17:05, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
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.
I am using GT in 3.0 and the inspector is indeed supercool. Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on Cmd-g. Depending on the task, one or the other is better. I am using Workspaces as a kind of command prompt in Pharo to set some state of the system, reinitializing etc. There is zero need to inspect the result there nor have a large window. Also, the ability to save/load such workspaces is very useful (as well as making them unclosable). All of these abilities are lost with the Playground and the size of the Playground there would be too large. There is a use case for both facilities. Phil On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess.
On 03 Oct 2014, at 17:05, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
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.
Yes your use case make a lot of sense.
I am using GT in 3.0 and the inspector is indeed supercool.
Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on Cmd-g. Depending on the task, one or the other is better.
I am using Workspaces as a kind of command prompt in Pharo to set some state of the system, reinitializing etc. There is zero need to inspect the result there nor have a large window. Also, the ability to save/load such workspaces is very useful (as well as making them unclosable). All of these abilities are lost with the Playground and the size of the Playground there would be too large.
There is a use case for both facilities.
Phil
On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess.
On 03 Oct 2014, at 17:05, Christophe Demarey <Christophe.Demarey@inria.fr <mailto:Christophe.Demarey@inria.fr>> wrote:
> 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.
This is indeed a relevant use case, and we are already thinking about this issue for quite a while. The playground or even the workspace are not appropriate for things that need to live for a short time only. I would like to have an interface that comes, let's me enter my command and then vanishes. Similar to the spotlight interface. And once we will be on this, we will also make it a search interface... remember that Pharo4 is about tooling so now is the time to dream and do :). Doru On Fri, Oct 3, 2014 at 10:38 PM, stepharo <stepharo@free.fr> wrote:
Yes your use case make a lot of sense.
I am using GT in 3.0 and the inspector is indeed supercool.
Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on Cmd-g. Depending on the task, one or the other is better.
I am using Workspaces as a kind of command prompt in Pharo to set some state of the system, reinitializing etc. There is zero need to inspect the result there nor have a large window. Also, the ability to save/load such workspaces is very useful (as well as making them unclosable). All of these abilities are lost with the Playground and the size of the Playground there would be too large.
There is a use case for both facilities.
Phil
On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess.
On 03 Oct 2014, at 17:05, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
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.
-- www.tudorgirba.com "Every thing has its own flow"
Well, my Spotlight looks like this: [image: Inline image 1] You'll notice the $<expr> to execute commands. Works well. Code is here: http://www.smalltalkhub.com/#!/~philippeback/HOExtras/packages/Tools Tools is an hefty package. Always interesting to dig in there. Looks like there is SourceWebBrowser subclassing Workspace and a UserManager. Never heard of those. It feels like an open world game. It is really nice to be able to dig as deep as one wants in those areas. Phil On Fri, Oct 3, 2014 at 10:57 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
This is indeed a relevant use case, and we are already thinking about this issue for quite a while. The playground or even the workspace are not appropriate for things that need to live for a short time only.
I would like to have an interface that comes, let's me enter my command and then vanishes. Similar to the spotlight interface. And once we will be on this, we will also make it a search interface... remember that Pharo4 is about tooling so now is the time to dream and do :).
Doru
On Fri, Oct 3, 2014 at 10:38 PM, stepharo <stepharo@free.fr> wrote:
Yes your use case make a lot of sense.
I am using GT in 3.0 and the inspector is indeed supercool.
Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on Cmd-g. Depending on the task, one or the other is better.
I am using Workspaces as a kind of command prompt in Pharo to set some state of the system, reinitializing etc. There is zero need to inspect the result there nor have a large window. Also, the ability to save/load such workspaces is very useful (as well as making them unclosable). All of these abilities are lost with the Playground and the size of the Playground there would be too large.
There is a use case for both facilities.
Phil
On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess.
On 03 Oct 2014, at 17:05, Christophe Demarey < Christophe.Demarey@inria.fr> wrote:
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.
-- www.tudorgirba.com
"Every thing has its own flow"
phil@highoctane.be wrote:
Well, my Spotlight looks like this:
Inline image 1
You'll notice the $<expr> to execute commands.
Works well. Code is here:
http://www.smalltalkhub.com/#!/~philippeback/HOExtras/packages/Tools
Tools is an hefty package. Always interesting to dig in there. Looks like there is SourceWebBrowser subclassing Workspace and a UserManager. Never heard of those. It feels like an open world game. It is really nice to be able to dig as deep as one wants in those areas.
Phil
I like that idea of having a start character to determine the function of Spotlight. Its a highly extensible concept. -ben
On Fri, Oct 3, 2014 at 10:57 PM, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote:
This is indeed a relevant use case, and we are already thinking about this issue for quite a while. The playground or even the workspace are not appropriate for things that need to live for a short time only.
I would like to have an interface that comes, let's me enter my command and then vanishes. Similar to the spotlight interface. And once we will be on this, we will also make it a search interface... remember that Pharo4 is about tooling so now is the time to dream and do :).
Doru
On Fri, Oct 3, 2014 at 10:38 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Yes your use case make a lot of sense.
I am using GT in 3.0 and the inspector is indeed supercool.
Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on Cmd-g. Depending on the task, one or the other is better.
I am using Workspaces as a kind of command prompt in Pharo to set some state of the system, reinitializing etc. There is zero need to inspect the result there nor have a large window. Also, the ability to save/load such workspaces is very useful (as well as making them unclosable). All of these abilities are lost with the Playground and the size of the Playground there would be too large.
There is a use case for both facilities.
Phil
On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess.
On 03 Oct 2014, at 17:05, Christophe Demarey <Christophe.Demarey@inria.fr <mailto:Christophe.Demarey@inria.fr>> wrote:
> 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.
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
Tudor Girba wrote:
This is indeed a relevant use case, and we are already thinking about this issue for quite a while. The playground or even the workspace are not appropriate for things that need to live for a short time only.
I would like to have an interface that comes, let's me enter my command and then vanishes. Similar to the spotlight interface. And once we will be on this, we will also make it a search interface... remember that Pharo4 is about tooling so now is the time to dream and do :).
Doru
Why not use spotlight, allowing Cmd-d to work. Or would you want a bit more space? Maybe if you need a second line you could use Alt-<Enter> ? -ben
On Fri, Oct 3, 2014 at 10:38 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Yes your use case make a lot of sense.
I am using GT in 3.0 and the inspector is indeed supercool.
Now, I've the standard Workspace on Cmd-o Cmd-w and the Playground on Cmd-g. Depending on the task, one or the other is better.
I am using Workspaces as a kind of command prompt in Pharo to set some state of the system, reinitializing etc. There is zero need to inspect the result there nor have a large window. Also, the ability to save/load such workspaces is very useful (as well as making them unclosable). All of these abilities are lost with the Playground and the size of the Playground there would be too large.
There is a use case for both facilities.
Phil
On Fri, Oct 3, 2014 at 5:07 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
I too feel that GT-Tools in general use up too much screen real estate. It is as if they were designed for big screens and/or small fonts. But I am concentrating on functionality (views) first, the look can change later on I guess.
On 03 Oct 2014, at 17:05, Christophe Demarey <Christophe.Demarey@inria.fr <mailto:Christophe.Demarey@inria.fr>> wrote:
> 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.
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
participants (6)
-
Ben Coman -
Christophe Demarey -
phil＠highoctane.be -
stepharo -
Sven Van Caekenberghe -
Tudor Girba