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. Sven
+1 On Wed, Oct 1, 2014 at 10:14 AM, Sven Van Caekenberghe <sven@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.
Sven
-- Bernardo E.C. Sent from a cheap desktop computer in South America.
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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? Cheers, Andrei
Sven
On Wed, Oct 1, 2014 at 4:00 PM, Andrei Chis <chisvasileandrei@gmail.com> 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 losing enthusiasm." Winston Churchill
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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
and btw, what about remap cmd+o to cmd+e (like âexecuteâ) ? Esteban
On 01 Oct 2014, at 16:05, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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
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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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
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 <chisvasileandrei@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 <estebanlm@gmail.com <mailto:estebanlm@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 <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@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
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? Cheers, Doru On Wed, Oct 1, 2014 at 4:20 PM, Esteban Lorenzano <estebanlm@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 <chisvasileandrei@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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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"
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 (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?
Yes, I like it. no need of a new shortcut. It was the first thing I tried in the Playground before seeing the arrow in the menu. Christophe.
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 <estebanlm@gmail.com <mailto:estebanlm@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 <chisvasileandrei@gmail.com <mailto:chisvasileandrei@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 <estebanlm@gmail.com <mailto:estebanlm@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 <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@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 <http://www.tudorgirba.com>
"Every thing has its own flow"
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 <stepharo@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 <estebanlm@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 <chisvasileandrei@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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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"
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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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 expresssion, I execute it. So please we should not use silly names and more important we should not think that is is ok because we should think about new people. so for me cmd-e is good that we can map cmd-i for inspector cmd-I for explorer. Simple and straightforward. Stef On 1/10/14 19:03, Alexandre Bergel wrote:
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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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
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 <stepharo@free.fr> 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 lecture)!!! But this is our fault.
In my book you will not see evaluating an expresssion, I execute it. So please we should not use silly names and more important we should not think that is is ok because we should think about new people.
so for me cmd-e is good that we can map cmd-i for inspector cmd-I for explorer.
Simple and straightforward.
Stef
On 1/10/14 19:03, Alexandre Bergel wrote:
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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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"
What is explorer? Doru On Wed, Oct 1, 2014 at 10:12 PM, stepharo <stepharo@free.fr> 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 lecture)!!! But this is our fault.
In my book you will not see evaluating an expresssion, I execute it. So please we should not use silly names and more important we should not think that is is ok because we should think about new people.
so for me cmd-e is good that we can map cmd-i for inspector cmd-I for explorer.
Simple and straightforward.
Stef
On 1/10/14 19:03, Alexandre Bergel wrote:
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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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"
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 <tudor@tudorgirba.com> wrote:
What is explorer?
Doru
On Wed, Oct 1, 2014 at 10:12 PM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> 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 lecture)!!! But this is our fault.
In my book you will not see evaluating an expresssion, I execute it. So please we should not use silly names and more important we should not think that is is ok because we should think about new people.
so for me cmd-e is good that we can map cmd-i for inspector cmd-I for explorer.
Simple and straightforward.
Stef
On 1/10/14 19:03, Alexandre Bergel wrote: 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 <estebanlm@gmail.com <mailto:estebanlm@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 <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@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 <http://www.tudorgirba.com/>
"Every thing has its own flow"
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 <estebanlm@gmail.com> 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, at 22:33, Tudor Girba <tudor@tudorgirba.com> wrote:
What is explorer?
Doru
On Wed, Oct 1, 2014 at 10:12 PM, stepharo <stepharo@free.fr> 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 lecture)!!! But this is our fault.
In my book you will not see evaluating an expresssion, I execute it. So please we should not use silly names and more important we should not think that is is ok because we should think about new people.
so for me cmd-e is good that we can map cmd-i for inspector cmd-I for explorer.
Simple and straightforward.
Stef
On 1/10/14 19:03, Alexandre Bergel wrote:
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 <estebanlm@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 <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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"
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 <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@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
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 consideration up to this point. Please keep challenging what you see. Cheers, Doru On Wed, Oct 1, 2014 at 4:05 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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"
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 <chisvasileandrei@gmail.com> wrote:
On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven@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
participants (9)
-
Alexandre Bergel -
Andrei Chis -
Bernardo Ezequiel Contreras -
Christophe Demarey -
Damien Cassou -
Esteban Lorenzano -
stepharo -
Sven Van Caekenberghe -
Tudor Girba