[Pharo-dev] Cmd-o is not opening a new pane?

[Alexandre Bergel]

It does in the moose image. Pity, this is so useful...

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

you have to pay attention to other lists other than moose, Alex :)
nah, seriously: we have been discussing on a remap, because it is conflicting 
with other keybindings we have in pharo (cmd+o+[others]). 

For now, we have three proposals:

cmd+e “execute”
cmd+g “go”
cmd+i, and remap gtinspector to cmd+I

personally I prefer the second one. 
the third one looks like a good idea, but it will introduce an incoherence in 
the system (unless we remap everything, everywhere), so I prefer to stick with 
“cmd+g”

Esteban

> On 02 Oct 2014, at 23:28, Alexandre Bergel  wrote:
> 
> It does in the moose image. Pity, this is so useful...
> 
> Cheers,
> Alexandre
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
> 

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Alexandre Bergel]

> you have to pay attention to other lists other than moose, Alex :)

Sorry for making some question redundant :-)

> nah, seriously: we have been discussing on a remap, because it is conflicting 
> with other keybindings we have in pharo (cmd+o+[others]). 

I was not aware of keybindings starting with cmd+o

Alexandre

> 
> For now, we have three proposals:
> 
> cmd+e “execute”
> cmd+g “go”
> cmd+i, and remap gtinspector to cmd+I
> 
> personally I prefer the second one. 
> the third one looks like a good idea, but it will introduce an incoherence in 
> the system (unless we remap everything, everywhere), so I prefer to stick 
> with “cmd+g”
> 
> Esteban
> 
>> On 02 Oct 2014, at 23:28, Alexandre Bergel  wrote:
>> 
>> It does in the moose image. Pity, this is so useful...
>> 
>> Cheers,
>> Alexandre
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>> 
> 
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Why do you think that the "Cmd+i" option introduces incoherence?

Doru

On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano 
wrote:

> you have to pay attention to other lists other than moose, Alex :)
> nah, seriously: we have been discussing on a remap, because it is
> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>
> For now, we have three proposals:
>
> cmd+e “execute”
> cmd+g “go”
> cmd+i, and remap gtinspector to cmd+I
>
> personally I prefer the second one.
> the third one looks like a good idea, but it will introduce an incoherence
> in the system (unless we remap everything, everywhere), so I prefer to
> stick with “cmd+g”
>
> Esteban
>
> > On 02 Oct 2014, at 23:28, Alexandre Bergel 
> wrote:
> >
> > It does in the moose image. Pity, this is so useful...
> >
> > Cheers,
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

yes, because it will be "open panel" in playground and "popup an inspector"
everyplace else.

On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba  wrote:

> Why do you think that the "Cmd+i" option introduces incoherence?
>
> Doru
>
> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano 
> wrote:
>
>> you have to pay attention to other lists other than moose, Alex :)
>> nah, seriously: we have been discussing on a remap, because it is
>> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>>
>> For now, we have three proposals:
>>
>> cmd+e “execute”
>> cmd+g “go”
>> cmd+i, and remap gtinspector to cmd+I
>>
>> personally I prefer the second one.
>> the third one looks like a good idea, but it will introduce an
>> incoherence in the system (unless we remap everything, everywhere), so I
>> prefer to stick with “cmd+g”
>>
>> Esteban
>>
>> > On 02 Oct 2014, at 23:28, Alexandre Bergel 
>> wrote:
>> >
>> > It does in the moose image. Pity, this is so useful...
>> >
>> > Cheers,
>> > Alexandre
>> > --
>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> > Alexandre Bergel  http://www.bergel.eu
>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >
>> >
>> >
>> >
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Marcus Denker]

On 03 Oct 2014, at 07:47, Tudor Girba  wrote:

> Why do you think that the "Cmd+i" option introduces incoherence?
> 

I like the idea of cmd-i for opening in the playground and cmd-I (big I) for 
spawning a new one.

(and the nice popper the we get when “print it” should have a play button… the 
“i” is already great, but
I sometimes "print it” and would like to play it instead…

> Doru
> 
> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano  
> wrote:
> you have to pay attention to other lists other than moose, Alex :)
> nah, seriously: we have been discussing on a remap, because it is conflicting 
> with other keybindings we have in pharo (cmd+o+[others]).
> 
> For now, we have three proposals:
> 
> cmd+e “execute”
> cmd+g “go”
> cmd+i, and remap gtinspector to cmd+I
> 
> personally I prefer the second one.
> the third one looks like a good idea, but it will introduce an incoherence in 
> the system (unless we remap everything, everywhere), so I prefer to stick 
> with “cmd+g”
> 
> Esteban
> 
> > On 02 Oct 2014, at 23:28, Alexandre Bergel  wrote:
> >
> > It does in the moose image. Pity, this is so useful...
> >
> > Cheers,
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> 
> 
> 
> 
> 
> -- 
> www.tudorgirba.com
> 
> "Every thing has its own flow"



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Hi,

What if you see it like this: Cmd+i inspects. If you can inspect in place,
you do it, otherwise, you inspect in a new window. I know it would require
a bit of getting used to, but imagine what will happen when the class
browser will allow you to inspect in place ... oops, perhaps I should have
not say it loud :)

Cheers,
Doru



On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano 
wrote:

> yes, because it will be "open panel" in playground and "popup an
> inspector" everyplace else.
>
> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba  wrote:
>
>> Why do you think that the "Cmd+i" option introduces incoherence?
>>
>> Doru
>>
>> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano 
>> wrote:
>>
>>> you have to pay attention to other lists other than moose, Alex :)
>>> nah, seriously: we have been discussing on a remap, because it is
>>> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>>>
>>> For now, we have three proposals:
>>>
>>> cmd+e “execute”
>>> cmd+g “go”
>>> cmd+i, and remap gtinspector to cmd+I
>>>
>>> personally I prefer the second one.
>>> the third one looks like a good idea, but it will introduce an
>>> incoherence in the system (unless we remap everything, everywhere), so I
>>> prefer to stick with “cmd+g”
>>>
>>> Esteban
>>>
>>> > On 02 Oct 2014, at 23:28, Alexandre Bergel 
>>> wrote:
>>> >
>>> > It does in the moose image. Pity, this is so useful...
>>> >
>>> > Cheers,
>>> > Alexandre
>>> > --
>>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> > Alexandre Bergel  http://www.bergel.eu
>>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Hi,

Exactly, that is the idea behind the "i", but the problem is that we still
have to find a nice way of implementing it :).

Cheers,
Doru



On Fri, Oct 3, 2014 at 8:14 AM, Marcus Denker 
wrote:

>
> On 03 Oct 2014, at 07:47, Tudor Girba  wrote:
>
> Why do you think that the "Cmd+i" option introduces incoherence?
>
>
> I like the idea of cmd-i for opening in the playground and cmd-I (big I)
> for spawning a new one.
>
> (and the nice popper the we get when “print it” should have a play button…
> the “i” is already great, but
> I sometimes "print it” and would like to play it instead…
>
> Doru
>
> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano 
> wrote:
>
>> you have to pay attention to other lists other than moose, Alex :)
>> nah, seriously: we have been discussing on a remap, because it is
>> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>>
>> For now, we have three proposals:
>>
>> cmd+e “execute”
>> cmd+g “go”
>> cmd+i, and remap gtinspector to cmd+I
>>
>> personally I prefer the second one.
>> the third one looks like a good idea, but it will introduce an
>> incoherence in the system (unless we remap everything, everywhere), so I
>> prefer to stick with “cmd+g”
>>
>> Esteban
>>
>> > On 02 Oct 2014, at 23:28, Alexandre Bergel 
>> wrote:
>> >
>> > It does in the moose image. Pity, this is so useful...
>> >
>> > Cheers,
>> > Alexandre
>> > --
>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> > Alexandre Bergel  http://www.bergel.eu
>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >
>> >
>> >
>> >
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

well, but that’s something that *now* you cannot do. 
what people will see now is “cmd+i does one thing in playground, and other 
thing in other parts of the system". 
For me, that’s not coherent, and introduces a level of pain. 
We are still trying to fix the annoying introduced by nautilus because commands 
are different on it than the rest of the system… I would like to avoid that. 

Esteban

> On 03 Oct 2014, at 08:17, Tudor Girba  wrote:
> 
> Hi,
> 
> What if you see it like this: Cmd+i inspects. If you can inspect in place, 
> you do it, otherwise, you inspect in a new window. I know it would require a 
> bit of getting used to, but imagine what will happen when the class browser 
> will allow you to inspect in place ... oops, perhaps I should have not say it 
> loud :)
> 
> Cheers,
> Doru
> 
> 
> 
> On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano  > wrote:
> yes, because it will be "open panel" in playground and "popup an inspector" 
> everyplace else. 
> 
> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba  > wrote:
> Why do you think that the "Cmd+i" option introduces incoherence?
> 
> Doru
> 
> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano  > wrote:
> you have to pay attention to other lists other than moose, Alex :)
> nah, seriously: we have been discussing on a remap, because it is conflicting 
> with other keybindings we have in pharo (cmd+o+[others]).
> 
> For now, we have three proposals:
> 
> cmd+e “execute”
> cmd+g “go”
> cmd+i, and remap gtinspector to cmd+I
> 
> personally I prefer the second one.
> the third one looks like a good idea, but it will introduce an incoherence in 
> the system (unless we remap everything, everywhere), so I prefer to stick 
> with “cmd+g”
> 
> Esteban
> 
> > On 02 Oct 2014, at 23:28, Alexandre Bergel  > > wrote:
> >
> > It does in the moose image. Pity, this is so useful...
> >
> > Cheers,
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu 
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> 
> 
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"
> 
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

I understand. But, even now, you associated Cmd+i as a window action. Is it
a stretch to see it as a logical action that materializes in different ways?

Doru

On Fri, Oct 3, 2014 at 8:26 AM, Esteban Lorenzano 
wrote:

> well, but that’s something that *now* you cannot do.
> what people will see now is “cmd+i does one thing in playground, and other
> thing in other parts of the system".
> For me, that’s not coherent, and introduces a level of pain.
> We are still trying to fix the annoying introduced by nautilus because
> commands are different on it than the rest of the system… I would like to
> avoid that.
>
> Esteban
>
> On 03 Oct 2014, at 08:17, Tudor Girba  wrote:
>
> Hi,
>
> What if you see it like this: Cmd+i inspects. If you can inspect in place,
> you do it, otherwise, you inspect in a new window. I know it would require
> a bit of getting used to, but imagine what will happen when the class
> browser will allow you to inspect in place ... oops, perhaps I should have
> not say it loud :)
>
> Cheers,
> Doru
>
>
>
> On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano 
> wrote:
>
>> yes, because it will be "open panel" in playground and "popup an
>> inspector" everyplace else.
>>
>> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba  wrote:
>>
>>> Why do you think that the "Cmd+i" option introduces incoherence?
>>>
>>> Doru
>>>
>>> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano 
>>> wrote:
>>>
 you have to pay attention to other lists other than moose, Alex :)
 nah, seriously: we have been discussing on a remap, because it is
 conflicting with other keybindings we have in pharo (cmd+o+[others]).

 For now, we have three proposals:

 cmd+e “execute”
 cmd+g “go”
 cmd+i, and remap gtinspector to cmd+I

 personally I prefer the second one.
 the third one looks like a good idea, but it will introduce an
 incoherence in the system (unless we remap everything, everywhere), so I
 prefer to stick with “cmd+g”

 Esteban

 > On 02 Oct 2014, at 23:28, Alexandre Bergel 
 wrote:
 >
 > It does in the moose image. Pity, this is so useful...
 >
 > Cheers,
 > Alexandre
 > --
 > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
 > Alexandre Bergel  http://www.bergel.eu
 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
 >
 >
 >
 >



>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

On a separate note, I played with another variation of a go icon that would
be more specific to Pharo. Would you like this better?

[image: Inline image 1]

Cheers,
Doru



On Fri, Oct 3, 2014 at 8:35 AM, Tudor Girba  wrote:

> I understand. But, even now, you associated Cmd+i as a window action. Is
> it a stretch to see it as a logical action that materializes in different
> ways?
>
> Doru
>
> On Fri, Oct 3, 2014 at 8:26 AM, Esteban Lorenzano 
> wrote:
>
>> well, but that’s something that *now* you cannot do.
>> what people will see now is “cmd+i does one thing in playground, and
>> other thing in other parts of the system".
>> For me, that’s not coherent, and introduces a level of pain.
>> We are still trying to fix the annoying introduced by nautilus because
>> commands are different on it than the rest of the system… I would like to
>> avoid that.
>>
>> Esteban
>>
>> On 03 Oct 2014, at 08:17, Tudor Girba  wrote:
>>
>> Hi,
>>
>> What if you see it like this: Cmd+i inspects. If you can inspect in
>> place, you do it, otherwise, you inspect in a new window. I know it would
>> require a bit of getting used to, but imagine what will happen when the
>> class browser will allow you to inspect in place ... oops, perhaps I should
>> have not say it loud :)
>>
>> Cheers,
>> Doru
>>
>>
>>
>> On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano 
>> wrote:
>>
>>> yes, because it will be "open panel" in playground and "popup an
>>> inspector" everyplace else.
>>>
>>> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba 
>>> wrote:
>>>
 Why do you think that the "Cmd+i" option introduces incoherence?

 Doru

 On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano >>> > wrote:

> you have to pay attention to other lists other than moose, Alex :)
> nah, seriously: we have been discussing on a remap, because it is
> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>
> For now, we have three proposals:
>
> cmd+e “execute”
> cmd+g “go”
> cmd+i, and remap gtinspector to cmd+I
>
> personally I prefer the second one.
> the third one looks like a good idea, but it will introduce an
> incoherence in the system (unless we remap everything, everywhere), so I
> prefer to stick with “cmd+g”
>
> Esteban
>
> > On 02 Oct 2014, at 23:28, Alexandre Bergel 
> wrote:
> >
> > It does in the moose image. Pity, this is so useful...
> >
> > Cheers,
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
>
>
>


 --
 www.tudorgirba.com

 "Every thing has its own flow"

>>>
>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>



-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[p...@highoctane.be]

Question about those icons, are they DarkTheme ready? I have had to invert
them all by hand to have something looking nice (and do all kinds of
changes to be able to read the contents).

Also, as GT is using Rubric, the default black/dark text has to be turned
into white as well as the cursor color in order to see something.

Phil

On Fri, Oct 3, 2014 at 8:44 AM, Tudor Girba  wrote:

> On a separate note, I played with another variation of a go icon that
> would be more specific to Pharo. Would you like this better?
>
> [image: Inline image 1]
>
> Cheers,
> Doru
>
>
>
> On Fri, Oct 3, 2014 at 8:35 AM, Tudor Girba  wrote:
>
>> I understand. But, even now, you associated Cmd+i as a window action. Is
>> it a stretch to see it as a logical action that materializes in different
>> ways?
>>
>> Doru
>>
>> On Fri, Oct 3, 2014 at 8:26 AM, Esteban Lorenzano 
>> wrote:
>>
>>> well, but that’s something that *now* you cannot do.
>>> what people will see now is “cmd+i does one thing in playground, and
>>> other thing in other parts of the system".
>>> For me, that’s not coherent, and introduces a level of pain.
>>> We are still trying to fix the annoying introduced by nautilus because
>>> commands are different on it than the rest of the system… I would like to
>>> avoid that.
>>>
>>> Esteban
>>>
>>> On 03 Oct 2014, at 08:17, Tudor Girba  wrote:
>>>
>>> Hi,
>>>
>>> What if you see it like this: Cmd+i inspects. If you can inspect in
>>> place, you do it, otherwise, you inspect in a new window. I know it would
>>> require a bit of getting used to, but imagine what will happen when the
>>> class browser will allow you to inspect in place ... oops, perhaps I should
>>> have not say it loud :)
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>>
>>> On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano 
>>> wrote:
>>>
 yes, because it will be "open panel" in playground and "popup an
 inspector" everyplace else.

 On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba 
 wrote:

> Why do you think that the "Cmd+i" option introduces incoherence?
>
> Doru
>
> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano <
> esteba...@gmail.com> wrote:
>
>> you have to pay attention to other lists other than moose, Alex :)
>> nah, seriously: we have been discussing on a remap, because it is
>> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>>
>> For now, we have three proposals:
>>
>> cmd+e “execute”
>> cmd+g “go”
>> cmd+i, and remap gtinspector to cmd+I
>>
>> personally I prefer the second one.
>> the third one looks like a good idea, but it will introduce an
>> incoherence in the system (unless we remap everything, everywhere), so I
>> prefer to stick with “cmd+g”
>>
>> Esteban
>>
>> > On 02 Oct 2014, at 23:28, Alexandre Bergel 
>> wrote:
>> >
>> > It does in the moose image. Pity, this is so useful...
>> >
>> > Cheers,
>> > Alexandre
>> > --
>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> > Alexandre Bergel  http://www.bergel.eu
>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >
>> >
>> >
>> >
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>


>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>>
>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Marcus Denker]

On 03 Oct 2014, at 09:30, p...@highoctane.be wrote:

> Question about those icons, are they DarkTheme ready? I have had to invert 
> them all by hand to have something looking nice (and do all kinds of changes 
> to be able to read the contents).
> 
> Also, as GT is using Rubric, the default black/dark text has to be turned 
> into white as well as the cursor color in order to see something.
> 

As far as I know: no, this is work on progress.

Marcus



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

No, they are not "Pharo ready" in general. I'm working in a change proposal...



> On 3 Oct 2014, at 09:30, "p...@highoctane.be"  wrote:
> 
> Question about those icons, are they DarkTheme ready? I have had to invert 
> them all by hand to have something looking nice (and do all kinds of changes 
> to be able to read the contents).
> 
> Also, as GT is using Rubric, the default black/dark text has to be turned 
> into white as well as the cursor color in order to see something.
> 
> Phil
> 
>> On Fri, Oct 3, 2014 at 8:44 AM, Tudor Girba  wrote:
>> On a separate note, I played with another variation of a go icon that would 
>> be more specific to Pharo. Would you like this better?
>> 
>> 
>> 
>> Cheers,
>> Doru
>> 
>> 
>> 
>>> On Fri, Oct 3, 2014 at 8:35 AM, Tudor Girba  wrote:
>>> I understand. But, even now, you associated Cmd+i as a window action. Is it 
>>> a stretch to see it as a logical action that materializes in different ways?
>>> 
>>> Doru
>>> 
 On Fri, Oct 3, 2014 at 8:26 AM, Esteban Lorenzano  
 wrote:
 well, but that’s something that *now* you cannot do. 
 what people will see now is “cmd+i does one thing in playground, and other 
 thing in other parts of the system". 
 For me, that’s not coherent, and introduces a level of pain. 
 We are still trying to fix the annoying introduced by nautilus because 
 commands are different on it than the rest of the system… I would like to 
 avoid that. 
 
 Esteban
 
> On 03 Oct 2014, at 08:17, Tudor Girba  wrote:
> 
> Hi,
> 
> What if you see it like this: Cmd+i inspects. If you can inspect in 
> place, you do it, otherwise, you inspect in a new window. I know it would 
> require a bit of getting used to, but imagine what will happen when the 
> class browser will allow you to inspect in place ... oops, perhaps I 
> should have not say it loud :)
> 
> Cheers,
> Doru
> 
> 
> 
>> On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano  
>> wrote:
>> yes, because it will be "open panel" in playground and "popup an 
>> inspector" everyplace else. 
>> 
>>> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba  
>>> wrote:
>>> Why do you think that the "Cmd+i" option introduces incoherence?
>>> 
>>> Doru
>>> 
 On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano 
  wrote:
 you have to pay attention to other lists other than moose, Alex :)
 nah, seriously: we have been discussing on a remap, because it is 
 conflicting with other keybindings we have in pharo (cmd+o+[others]).
 
 For now, we have three proposals:
 
 cmd+e “execute”
 cmd+g “go”
 cmd+i, and remap gtinspector to cmd+I
 
 personally I prefer the second one.
 the third one looks like a good idea, but it will introduce an 
 incoherence in the system (unless we remap everything, everywhere), so 
 I prefer to stick with “cmd+g”
 
 Esteban
 
 > On 02 Oct 2014, at 23:28, Alexandre Bergel  
 > wrote:
 >
 > It does in the moose image. Pity, this is so useful...
 >
 > Cheers,
 > Alexandre
 > --
 > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
 > Alexandre Bergel  http://www.bergel.eu
 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
 >
 >
 >
 >
>>> 
>>> 
>>> 
>>> -- 
>>> www.tudorgirba.com
>>> 
>>> "Every thing has its own flow"
> 
> 
> 
> -- 
> www.tudorgirba.com
> 
> "Every thing has its own flow"
>>> 
>>> 
>>> 
>>> -- 
>>> www.tudorgirba.com
>>> 
>>> "Every thing has its own flow"
>> 
>> 
>> 
>> -- 
>> www.tudorgirba.com
>> 
>> "Every thing has its own flow"
> 

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Christophe Demarey]

Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :

> well, but that’s something that *now* you cannot do. 
> what people will see now is “cmd+i does one thing in playground, and other 
> thing in other parts of the system". 

Maybe it is me but what I see is cmd+i => inspect.
I will be more confused to use cmd+o in GT and cmd+i everywhere else.

My 2 cents,
Christophe.



smime.p7s
Description: S/MIME cryptographic signature

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Marcus Denker]

On 03 Oct 2014, at 10:08, Christophe Demarey  
wrote:

> 
> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
> 
>> well, but that’s something that *now* you cannot do. 
>> what people will see now is “cmd+i does one thing in playground, and other 
>> thing in other parts of the system". 
> 
> Maybe it is me but what I see is cmd+i => inspect.
> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
> 

another argument: everyone agrees that we open too many windows (*far* too many 
windows) and that we
need to change the IDE to do that less.

Now if we declare “every keystroke that used to open a window needs to open a 
window forever and in all
contexts”, then it will be hard to solve the window-plague…

Marcus



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[p...@highoctane.be]

Window plague maybe, but Ctrl-w is closing them quite fast too.

As well as the Windows > Delete Unchanged windows menu entry.

Tiling Windows Manager kind of helps too.

It is important to have all of those windows when drilling down into a
complicated feature with senders and implementors. That is  a
differentiating factor vs other IDEs. (Ok, Vim can :sp and :vsp a lot but
this is not the same feeling).

Phil

On Fri, Oct 3, 2014 at 10:13 AM, Marcus Denker 
wrote:

>
> On 03 Oct 2014, at 10:08, Christophe Demarey 
> wrote:
>
> >
> > Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
> >
> >> well, but that’s something that *now* you cannot do.
> >> what people will see now is “cmd+i does one thing in playground, and
> other thing in other parts of the system".
> >
> > Maybe it is me but what I see is cmd+i => inspect.
> > I will be more confused to use cmd+o in GT and cmd+i everywhere else.
> >
>
> another argument: everyone agrees that we open too many windows (*far* too
> many windows) and that we
> need to change the IDE to do that less.
>
> Now if we declare “every keystroke that used to open a window needs to
> open a window forever and in all
> contexts”, then it will be hard to solve the window-plague…
>
> Marcus
>
>

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Hi,

Indeed, they are not ready for the dark theme.

As for Pharo-ready, I would rather take the opportunity to create a set of
icons that are Pharo specific. I can try to play with that.

@Esteban: could you point me to where I should look for the currently used
icons?

Cheers,
Doru

On Fri, Oct 3, 2014 at 9:52 AM, Esteban Lorenzano 
wrote:

> No, they are not "Pharo ready" in general. I'm working in a change
> proposal...
>
>
>
> On 3 Oct 2014, at 09:30, "p...@highoctane.be"  wrote:
>
> Question about those icons, are they DarkTheme ready? I have had to invert
> them all by hand to have something looking nice (and do all kinds of
> changes to be able to read the contents).
>
> Also, as GT is using Rubric, the default black/dark text has to be turned
> into white as well as the cursor color in order to see something.
>
> Phil
>
> On Fri, Oct 3, 2014 at 8:44 AM, Tudor Girba  wrote:
>
>> On a separate note, I played with another variation of a go icon that
>> would be more specific to Pharo. Would you like this better?
>>
>> 
>>
>> Cheers,
>> Doru
>>
>>
>>
>> On Fri, Oct 3, 2014 at 8:35 AM, Tudor Girba  wrote:
>>
>>> I understand. But, even now, you associated Cmd+i as a window action. Is
>>> it a stretch to see it as a logical action that materializes in different
>>> ways?
>>>
>>> Doru
>>>
>>> On Fri, Oct 3, 2014 at 8:26 AM, Esteban Lorenzano 
>>> wrote:
>>>
 well, but that’s something that *now* you cannot do.
 what people will see now is “cmd+i does one thing in playground, and
 other thing in other parts of the system".
 For me, that’s not coherent, and introduces a level of pain.
 We are still trying to fix the annoying introduced by nautilus because
 commands are different on it than the rest of the system… I would like to
 avoid that.

 Esteban

 On 03 Oct 2014, at 08:17, Tudor Girba  wrote:

 Hi,

 What if you see it like this: Cmd+i inspects. If you can inspect in
 place, you do it, otherwise, you inspect in a new window. I know it would
 require a bit of getting used to, but imagine what will happen when the
 class browser will allow you to inspect in place ... oops, perhaps I should
 have not say it loud :)

 Cheers,
 Doru



 On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano 
 wrote:

> yes, because it will be "open panel" in playground and "popup an
> inspector" everyplace else.
>
> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba 
> wrote:
>
>> Why do you think that the "Cmd+i" option introduces incoherence?
>>
>> Doru
>>
>> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano <
>> esteba...@gmail.com> wrote:
>>
>>> you have to pay attention to other lists other than moose, Alex :)
>>> nah, seriously: we have been discussing on a remap, because it is
>>> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>>>
>>> For now, we have three proposals:
>>>
>>> cmd+e “execute”
>>> cmd+g “go”
>>> cmd+i, and remap gtinspector to cmd+I
>>>
>>> personally I prefer the second one.
>>> the third one looks like a good idea, but it will introduce an
>>> incoherence in the system (unless we remap everything, everywhere), so I
>>> prefer to stick with “cmd+g”
>>>
>>> Esteban
>>>
>>> > On 02 Oct 2014, at 23:28, Alexandre Bergel <
>>> alexandre.ber...@me.com> wrote:
>>> >
>>> > It does in the moose image. Pity, this is so useful...
>>> >
>>> > Cheers,
>>> > Alexandre
>>> > --
>>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> > Alexandre Bergel  http://www.bergel.eu
>>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>


 --
 www.tudorgirba.com

 "Every thing has its own flow"



>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Hi,

Well, the same argument was used for inspectors before the GTInspector. And
now, the amount of inspector windows reduces significantly and you actually
gain value in the process (because you keep track of the session).

Having windows popping up everywhere is a technical solution, but it does
not mean we cannot find a better cognitive solution. I think that the
overhead imposed by those windows is quite high and reducing the amount is
a worthy goal.

Cheers,
Doru

On Fri, Oct 3, 2014 at 10:30 AM, p...@highoctane.be 
wrote:

> Window plague maybe, but Ctrl-w is closing them quite fast too.
>
> As well as the Windows > Delete Unchanged windows menu entry.
>
> Tiling Windows Manager kind of helps too.
>
> It is important to have all of those windows when drilling down into a
> complicated feature with senders and implementors. That is  a
> differentiating factor vs other IDEs. (Ok, Vim can :sp and :vsp a lot but
> this is not the same feeling).
>
> Phil
>
> On Fri, Oct 3, 2014 at 10:13 AM, Marcus Denker 
> wrote:
>
>>
>> On 03 Oct 2014, at 10:08, Christophe Demarey 
>> wrote:
>>
>> >
>> > Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
>> >
>> >> well, but that’s something that *now* you cannot do.
>> >> what people will see now is “cmd+i does one thing in playground, and
>> other thing in other parts of the system".
>> >
>> > Maybe it is me but what I see is cmd+i => inspect.
>> > I will be more confused to use cmd+o in GT and cmd+i everywhere else.
>> >
>>
>> another argument: everyone agrees that we open too many windows (*far*
>> too many windows) and that we
>> need to change the IDE to do that less.
>>
>> Now if we declare “every keystroke that used to open a window needs to
>> open a window forever and in all
>> contexts”, then it will be hard to solve the window-plague…
>>
>> Marcus
>>
>>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

> On 03 Oct 2014, at 11:40, Tudor Girba  wrote:
> 
> Hi,
> 
> Indeed, they are not ready for the dark theme.
> 
> As for Pharo-ready, I would rather take the opportunity to create a set of 
> icons that are Pharo specific. I can try to play with that.
> 
> @Esteban: could you point me to where I should look for the currently used 
> icons?

current icons are in: EclipseUIThemeIcons and around. 
but I’m starting to refactorise all that monolithic crap we have now. 
I was just now discussing an idea (more or less same we discussed before around 
themes) to solve this (still not completely done…)

Esteban 

> 
> Cheers,
> Doru
> 
> On Fri, Oct 3, 2014 at 9:52 AM, Esteban Lorenzano  > wrote:
> No, they are not "Pharo ready" in general. I'm working in a change proposal...
> 
> 
> 
> On 3 Oct 2014, at 09:30, "p...@highoctane.be " 
> mailto:p...@highoctane.be>> wrote:
> 
>> Question about those icons, are they DarkTheme ready? I have had to invert 
>> them all by hand to have something looking nice (and do all kinds of changes 
>> to be able to read the contents).
>> 
>> Also, as GT is using Rubric, the default black/dark text has to be turned 
>> into white as well as the cursor color in order to see something.
>> 
>> Phil
>> 
>> On Fri, Oct 3, 2014 at 8:44 AM, Tudor Girba > > wrote:
>> On a separate note, I played with another variation of a go icon that would 
>> be more specific to Pharo. Would you like this better?
>> 
>> 
>> 
>> Cheers,
>> Doru
>> 
>> 
>> 
>> On Fri, Oct 3, 2014 at 8:35 AM, Tudor Girba > > wrote:
>> I understand. But, even now, you associated Cmd+i as a window action. Is it 
>> a stretch to see it as a logical action that materializes in different ways?
>> 
>> Doru
>> 
>> On Fri, Oct 3, 2014 at 8:26 AM, Esteban Lorenzano > > wrote:
>> well, but that’s something that *now* you cannot do. 
>> what people will see now is “cmd+i does one thing in playground, and other 
>> thing in other parts of the system". 
>> For me, that’s not coherent, and introduces a level of pain. 
>> We are still trying to fix the annoying introduced by nautilus because 
>> commands are different on it than the rest of the system… I would like to 
>> avoid that. 
>> 
>> Esteban
>> 
>>> On 03 Oct 2014, at 08:17, Tudor Girba >> > wrote:
>>> 
>>> Hi,
>>> 
>>> What if you see it like this: Cmd+i inspects. If you can inspect in place, 
>>> you do it, otherwise, you inspect in a new window. I know it would require 
>>> a bit of getting used to, but imagine what will happen when the class 
>>> browser will allow you to inspect in place ... oops, perhaps I should have 
>>> not say it loud :)
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> 
>>> 
>>> On Fri, Oct 3, 2014 at 8:11 AM, Esteban Lorenzano >> > wrote:
>>> yes, because it will be "open panel" in playground and "popup an inspector" 
>>> everyplace else. 
>>> 
>>> On Fri, Oct 3, 2014 at 7:47 AM, Tudor Girba >> > wrote:
>>> Why do you think that the "Cmd+i" option introduces incoherence?
>>> 
>>> Doru
>>> 
>>> On Thu, Oct 2, 2014 at 11:45 PM, Esteban Lorenzano >> > wrote:
>>> you have to pay attention to other lists other than moose, Alex :)
>>> nah, seriously: we have been discussing on a remap, because it is 
>>> conflicting with other keybindings we have in pharo (cmd+o+[others]).
>>> 
>>> For now, we have three proposals:
>>> 
>>> cmd+e “execute”
>>> cmd+g “go”
>>> cmd+i, and remap gtinspector to cmd+I
>>> 
>>> personally I prefer the second one.
>>> the third one looks like a good idea, but it will introduce an incoherence 
>>> in the system (unless we remap everything, everywhere), so I prefer to 
>>> stick with “cmd+g”
>>> 
>>> Esteban
>>> 
>>> > On 02 Oct 2014, at 23:28, Alexandre Bergel >> > > wrote:
>>> >
>>> > It does in the moose image. Pity, this is so useful...
>>> >
>>> > Cheers,
>>> > Alexandre
>>> > --
>>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> > Alexandre Bergel  http://www.bergel.eu 
>>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >
>>> >
>>> >
>>> >
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> www.tudorgirba.com 
>>> 
>>> "Every thing has its own flow"
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> www.tudorgirba.com 
>>> 
>>> "Every thing has its own flow"
>> 
>> 
>> 
>> 
>> -- 
>> www.tudorgirba.com 
>> 
>> "Every thing has its own flow"
>> 
>> 
>> 
>> -- 
>> www.tudorgirba.com 
>> 
>> "Every thing has its own flow"
>> 
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

well… but I still keep my argument: current cmd+i semantics is “popup a new 
inspector”, if we change that *just in the playground”, it will be annoying. 
anyway, looks like opinions are divided: I believe that using cmd+i is bad, 
while the rest of the world believe is the best way to go. 
but since I’m not sure, I’m making a poll  to see the general opinion :)

Esteban

> On 03 Oct 2014, at 10:13, Marcus Denker  wrote:
> 
> 
> On 03 Oct 2014, at 10:08, Christophe Demarey  
> wrote:
> 
>> 
>> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
>> 
>>> well, but that’s something that *now* you cannot do. 
>>> what people will see now is “cmd+i does one thing in playground, and other 
>>> thing in other parts of the system". 
>> 
>> Maybe it is me but what I see is cmd+i => inspect.
>> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
>> 
> 
> another argument: everyone agrees that we open too many windows (*far* too 
> many windows) and that we
> need to change the IDE to do that less.
> 
> Now if we declare “every keystroke that used to open a window needs to open a 
> window forever and in all
> contexts”, then it will be hard to solve the window-plague…
> 
>   Marcus
> 

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

I suggest another thing.

We keep Cmd+g as the "ginspect". And when we will work on the next tools
will add this command when possible.

So, in essence, Cmd+i will become the Cmd+Shift+i from my proposal, and
Cmd+g will become the Cmd+i from my proposal.

What do you think?

Cheers,
Doru



On Fri, Oct 3, 2014 at 12:21 PM, Esteban Lorenzano 
wrote:

> well… but I still keep my argument: current cmd+i semantics is “popup a
> new inspector”, if we change that *just in the playground”, it will be
> annoying.
> anyway, looks like opinions are divided: I believe that using cmd+i is
> bad, while the rest of the world believe is the best way to go.
> but since I’m not sure, I’m making a poll  to see the general opinion :)
>
> Esteban
>
> > On 03 Oct 2014, at 10:13, Marcus Denker  wrote:
> >
> >
> > On 03 Oct 2014, at 10:08, Christophe Demarey <
> christophe.dema...@inria.fr> wrote:
> >
> >>
> >> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
> >>
> >>> well, but that’s something that *now* you cannot do.
> >>> what people will see now is “cmd+i does one thing in playground, and
> other thing in other parts of the system".
> >>
> >> Maybe it is me but what I see is cmd+i => inspect.
> >> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
> >>
> >
> > another argument: everyone agrees that we open too many windows (*far*
> too many windows) and that we
> > need to change the IDE to do that less.
> >
> > Now if we declare “every keystroke that used to open a window needs to
> open a window forever and in all
> > contexts”, then it will be hard to solve the window-plague…
> >
> >   Marcus
> >
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

yeah, I can agree with that :)

> On 03 Oct 2014, at 14:27, Tudor Girba  wrote:
> 
> I suggest another thing.
> 
> We keep Cmd+g as the "ginspect". And when we will work on the next tools will 
> add this command when possible.
> 
> So, in essence, Cmd+i will become the Cmd+Shift+i from my proposal, and Cmd+g 
> will become the Cmd+i from my proposal.
> 
> What do you think?
> 
> Cheers,
> Doru
> 
> 
> 
> On Fri, Oct 3, 2014 at 12:21 PM, Esteban Lorenzano  > wrote:
> well… but I still keep my argument: current cmd+i semantics is “popup a new 
> inspector”, if we change that *just in the playground”, it will be annoying.
> anyway, looks like opinions are divided: I believe that using cmd+i is bad, 
> while the rest of the world believe is the best way to go.
> but since I’m not sure, I’m making a poll  to see the general opinion :)
> 
> Esteban
> 
> > On 03 Oct 2014, at 10:13, Marcus Denker  > > wrote:
> >
> >
> > On 03 Oct 2014, at 10:08, Christophe Demarey  > > wrote:
> >
> >>
> >> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
> >>
> >>> well, but that’s something that *now* you cannot do.
> >>> what people will see now is “cmd+i does one thing in playground, and 
> >>> other thing in other parts of the system".
> >>
> >> Maybe it is me but what I see is cmd+i => inspect.
> >> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
> >>
> >
> > another argument: everyone agrees that we open too many windows (*far* too 
> > many windows) and that we
> > need to change the IDE to do that less.
> >
> > Now if we declare “every keystroke that used to open a window needs to open 
> > a window forever and in all
> > contexts”, then it will be hard to solve the window-plague…
> >
> >   Marcus
> >
> 
> 
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Ok. Then how do we call the action?

I like "gInspect", but that is not useful for
non-deeply-into-the-joke-people. Would "Go" be fine?

Cheers,
Doru

On Fri, Oct 3, 2014 at 2:37 PM, Esteban Lorenzano 
wrote:

> yeah, I can agree with that :)
>
> On 03 Oct 2014, at 14:27, Tudor Girba  wrote:
>
> I suggest another thing.
>
> We keep Cmd+g as the "ginspect". And when we will work on the next tools
> will add this command when possible.
>
> So, in essence, Cmd+i will become the Cmd+Shift+i from my proposal, and
> Cmd+g will become the Cmd+i from my proposal.
>
> What do you think?
>
> Cheers,
> Doru
>
>
>
> On Fri, Oct 3, 2014 at 12:21 PM, Esteban Lorenzano 
> wrote:
>
>> well… but I still keep my argument: current cmd+i semantics is “popup a
>> new inspector”, if we change that *just in the playground”, it will be
>> annoying.
>> anyway, looks like opinions are divided: I believe that using cmd+i is
>> bad, while the rest of the world believe is the best way to go.
>> but since I’m not sure, I’m making a poll  to see the general opinion :)
>>
>> Esteban
>>
>> > On 03 Oct 2014, at 10:13, Marcus Denker  wrote:
>> >
>> >
>> > On 03 Oct 2014, at 10:08, Christophe Demarey <
>> christophe.dema...@inria.fr> wrote:
>> >
>> >>
>> >> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
>> >>
>> >>> well, but that’s something that *now* you cannot do.
>> >>> what people will see now is “cmd+i does one thing in playground, and
>> other thing in other parts of the system".
>> >>
>> >> Maybe it is me but what I see is cmd+i => inspect.
>> >> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
>> >>
>> >
>> > another argument: everyone agrees that we open too many windows (*far*
>> too many windows) and that we
>> > need to change the IDE to do that less.
>> >
>> > Now if we declare “every keystroke that used to open a window needs to
>> open a window forever and in all
>> > contexts”, then it will be hard to solve the window-plague…
>> >
>> >   Marcus
>> >
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Tudor Girba]

Or it can be "Do it and go".

Doru

On Fri, Oct 3, 2014 at 2:41 PM, Tudor Girba  wrote:

> Ok. Then how do we call the action?
>
> I like "gInspect", but that is not useful for
> non-deeply-into-the-joke-people. Would "Go" be fine?
>
> Cheers,
> Doru
>
> On Fri, Oct 3, 2014 at 2:37 PM, Esteban Lorenzano 
> wrote:
>
>> yeah, I can agree with that :)
>>
>> On 03 Oct 2014, at 14:27, Tudor Girba  wrote:
>>
>> I suggest another thing.
>>
>> We keep Cmd+g as the "ginspect". And when we will work on the next tools
>> will add this command when possible.
>>
>> So, in essence, Cmd+i will become the Cmd+Shift+i from my proposal, and
>> Cmd+g will become the Cmd+i from my proposal.
>>
>> What do you think?
>>
>> Cheers,
>> Doru
>>
>>
>>
>> On Fri, Oct 3, 2014 at 12:21 PM, Esteban Lorenzano 
>> wrote:
>>
>>> well… but I still keep my argument: current cmd+i semantics is “popup a
>>> new inspector”, if we change that *just in the playground”, it will be
>>> annoying.
>>> anyway, looks like opinions are divided: I believe that using cmd+i is
>>> bad, while the rest of the world believe is the best way to go.
>>> but since I’m not sure, I’m making a poll  to see the general opinion :)
>>>
>>> Esteban
>>>
>>> > On 03 Oct 2014, at 10:13, Marcus Denker 
>>> wrote:
>>> >
>>> >
>>> > On 03 Oct 2014, at 10:08, Christophe Demarey <
>>> christophe.dema...@inria.fr> wrote:
>>> >
>>> >>
>>> >> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
>>> >>
>>> >>> well, but that’s something that *now* you cannot do.
>>> >>> what people will see now is “cmd+i does one thing in playground, and
>>> other thing in other parts of the system".
>>> >>
>>> >> Maybe it is me but what I see is cmd+i => inspect.
>>> >> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
>>> >>
>>> >
>>> > another argument: everyone agrees that we open too many windows (*far*
>>> too many windows) and that we
>>> > need to change the IDE to do that less.
>>> >
>>> > Now if we declare “every keystroke that used to open a window needs to
>>> open a window forever and in all
>>> > contexts”, then it will be hard to solve the window-plague…
>>> >
>>> >   Marcus
>>> >
>>>
>>>
>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>



-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Esteban Lorenzano]

> On 03 Oct 2014, at 14:53, Tudor Girba  wrote:
> 
> Or it can be "Do it and go”.

+1

> 
> Doru
> 
> On Fri, Oct 3, 2014 at 2:41 PM, Tudor Girba  > wrote:
> Ok. Then how do we call the action?
> 
> I like "gInspect", but that is not useful for 
> non-deeply-into-the-joke-people. Would "Go" be fine?
> 
> Cheers,
> Doru
> 
> On Fri, Oct 3, 2014 at 2:37 PM, Esteban Lorenzano  > wrote:
> yeah, I can agree with that :)
> 
>> On 03 Oct 2014, at 14:27, Tudor Girba > > wrote:
>> 
>> I suggest another thing.
>> 
>> We keep Cmd+g as the "ginspect". And when we will work on the next tools 
>> will add this command when possible.
>> 
>> So, in essence, Cmd+i will become the Cmd+Shift+i from my proposal, and 
>> Cmd+g will become the Cmd+i from my proposal.
>> 
>> What do you think?
>> 
>> Cheers,
>> Doru
>> 
>> 
>> 
>> On Fri, Oct 3, 2014 at 12:21 PM, Esteban Lorenzano > > wrote:
>> well… but I still keep my argument: current cmd+i semantics is “popup a new 
>> inspector”, if we change that *just in the playground”, it will be annoying.
>> anyway, looks like opinions are divided: I believe that using cmd+i is bad, 
>> while the rest of the world believe is the best way to go.
>> but since I’m not sure, I’m making a poll  to see the general opinion :)
>> 
>> Esteban
>> 
>> > On 03 Oct 2014, at 10:13, Marcus Denker > > > wrote:
>> >
>> >
>> > On 03 Oct 2014, at 10:08, Christophe Demarey > > > wrote:
>> >
>> >>
>> >> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
>> >>
>> >>> well, but that’s something that *now* you cannot do.
>> >>> what people will see now is “cmd+i does one thing in playground, and 
>> >>> other thing in other parts of the system".
>> >>
>> >> Maybe it is me but what I see is cmd+i => inspect.
>> >> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
>> >>
>> >
>> > another argument: everyone agrees that we open too many windows (*far* too 
>> > many windows) and that we
>> > need to change the IDE to do that less.
>> >
>> > Now if we declare “every keystroke that used to open a window needs to 
>> > open a window forever and in all
>> > contexts”, then it will be hard to solve the window-plague…
>> >
>> >   Marcus
>> >
>> 
>> 
>> 
>> 
>> 
>> -- 
>> www.tudorgirba.com 
>> 
>> "Every thing has its own flow"
> 
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Sven Van Caekenberghe]

+1

On 03 Oct 2014, at 14:53, Tudor Girba  wrote:

> Or it can be "Do it and go".
> 
> Doru
> 
> On Fri, Oct 3, 2014 at 2:41 PM, Tudor Girba  wrote:
> Ok. Then how do we call the action?
> 
> I like "gInspect", but that is not useful for 
> non-deeply-into-the-joke-people. Would "Go" be fine?
> 
> Cheers,
> Doru
> 
> On Fri, Oct 3, 2014 at 2:37 PM, Esteban Lorenzano  wrote:
> yeah, I can agree with that :)
> 
>> On 03 Oct 2014, at 14:27, Tudor Girba  wrote:
>> 
>> I suggest another thing.
>> 
>> We keep Cmd+g as the "ginspect". And when we will work on the next tools 
>> will add this command when possible.
>> 
>> So, in essence, Cmd+i will become the Cmd+Shift+i from my proposal, and 
>> Cmd+g will become the Cmd+i from my proposal.
>> 
>> What do you think?
>> 
>> Cheers,
>> Doru
>> 
>> 
>> 
>> On Fri, Oct 3, 2014 at 12:21 PM, Esteban Lorenzano  
>> wrote:
>> well… but I still keep my argument: current cmd+i semantics is “popup a new 
>> inspector”, if we change that *just in the playground”, it will be annoying.
>> anyway, looks like opinions are divided: I believe that using cmd+i is bad, 
>> while the rest of the world believe is the best way to go.
>> but since I’m not sure, I’m making a poll  to see the general opinion :)
>> 
>> Esteban
>> 
>> > On 03 Oct 2014, at 10:13, Marcus Denker  wrote:
>> >
>> >
>> > On 03 Oct 2014, at 10:08, Christophe Demarey  
>> > wrote:
>> >
>> >>
>> >> Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :
>> >>
>> >>> well, but that’s something that *now* you cannot do.
>> >>> what people will see now is “cmd+i does one thing in playground, and 
>> >>> other thing in other parts of the system".
>> >>
>> >> Maybe it is me but what I see is cmd+i => inspect.
>> >> I will be more confused to use cmd+o in GT and cmd+i everywhere else.
>> >>
>> >
>> > another argument: everyone agrees that we open too many windows (*far* too 
>> > many windows) and that we
>> > need to change the IDE to do that less.
>> >
>> > Now if we declare “every keystroke that used to open a window needs to 
>> > open a window forever and in all
>> > contexts”, then it will be hard to solve the window-plague…
>> >
>> >   Marcus
>> >
>> 
>> 
>> 
>> 
>> 
>> -- 
>> www.tudorgirba.com
>> 
>> "Every thing has its own flow"
> 
> 
> 
> 
> -- 
> www.tudorgirba.com
> 
> "Every thing has its own flow"
> 
> 
> 
> -- 
> www.tudorgirba.com
> 
> "Every thing has its own flow"

Re: [Pharo-dev] Cmd-o is not opening a new pane?

[Ben Coman]

Marcus Denker wrote:

On 03 Oct 2014, at 10:08, Christophe Demarey  
wrote:


Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit :

well, but that’s something that *now* you cannot do. 
what people will see now is “cmd+i does one thing in playground, and other thing in other parts of the system". 

Maybe it is me but what I see is cmd+i => inspect.
I will be more confused to use cmd+o in GT and cmd+i everywhere else.



another argument: everyone agrees that we open too many windows (*far* too many 
windows) and that we
need to change the IDE to do that less.

Now if we declare “every keystroke that used to open a window needs to open a 
window forever and in all
contexts”, then it will be hard to solve the window-plague…

Marcus



Maybe we should be opening tabs by default. Its a paradigm that worked 
for web browsers.

-ben