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 can map on Cmd+Shift+i (like we did for the explorer before). I think this would fit, but it would be a bit difficult to implement. Is it clearer? What do you think? Cheers, Doru On Wed, Oct 1, 2014 at 10:09 PM, stepharo <steph...@free.fr> wrote: > > 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 playground). > > To force inspect in a new window we could use Cmd+Shift+i and this would > be uniformly applied everywhere. > > What do you think? > > I'm lost. > > > > Cheers, > Doru > > On Wed, Oct 1, 2014 at 4:20 PM, Esteban Lorenzano <esteba...@gmail.com> > wrote: > >> 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 <chisvasileand...@gmail.com> >> wrote: >> >> 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, Esteban Lorenzano <esteba...@gmail.com> >> wrote: >> >>> and btw, what about remap cmd+o to cmd+e (like “execute”) ? >>> >>> Esteban >>> >>> >>> On 01 Oct 2014, at 16:05, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> >>> >>> On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileand...@gmail.com> >>> wrote: >>> >>> >>> >>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <s...@stfx.eu> >>> 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 workspace/playground is like a notebook containing lots of different >>> things. >>> >>> >>> Yes, it is like this by design. The Play button at the top evaluates >>> the entire content of the workspace. >>> >>> To evaluate just an expression you can select it and choose 'Open' from >>> the context menu, or use CMD+o. >>> Just right now CMD+o is still broken due to the global shortcuts from >>> opening tools. >>> >>> The Play button at the top works like that as we tried to have in the >>> toolbar only global actions that apply on the entire presentations and not >>> only on the selection. >>> Those that apply on the selection go in the context menu and should have >>> keybindings >>> >>> Does this seem ok to you? >>> >>> >>> Ah, I thought the open menu action worked like the inspect it menu >>> action. >>> OK, that works for me. >>> >>> Thanks. >>> >>> Cheers, >>> Andrei >>> >>> >>> Sven >>> >>> >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"
