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 <[email protected]> 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 <[email protected]> > 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. > > >
