October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] RB Tests failing

by stepharo

Mark told me that he will publish them. Stef On 30/9/14 11:37, Nicolai Hess wrote: > 2014-09-30 11:02 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com > <mailto:yuriy.tymchuk@me.com>>: > > Hi, > > now when you download a new Pharo4 image there are 3 tests > failing/erroring: > Failures: > RBRenameInstanceVariableTest>>#testRenameInstVarAccessorsReferences > > Errors: > RBRemoveClassTest>>#testRemoveClass > RBExtractMethodTest>>#testExtractMethodThatMovesTemporaryVariable > > Is there an issue about that? Is anybody looking into it? > > > > Yes there are > 13718 > 13719 > 13588 > Mark Rizun worked on them, but the fix does not work resp. I can not > find a slice. > > > > > Uko > >

Oct. 2, 2014

Re: [Pharo-dev] ZnEasy and post:data:

by Sven Van Caekenberghe

ZnClient is your friend (it is a builder) : ZnClient new url: 'http://some/thing'; formAt: #foo put: #bar; formAt: 'baz' put: 'quux'; post. HTH, Sven PS: Check out the 'accessing request' protocol for more ways to construct your request. Also, the response is kept in the object: #post returns something called the contents, but you can add ; response or ; isSuccess at the end. Check out the class comment or unit tests. On 02 Oct 2014, at 02:17, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > Hey all, > > This is probably me missing something, but: for an upcoming > presentation, I wanted to find the tersest way to demonstrate making an > HTTP POST. Something equivalent to Python's > > requests.post('http://some/thing', data={'foo': 'bar', 'baz': > 'quux'}) > > The closest I could come up with for Pharo was > > ZnEasy post: 'http://some/thing' data: > (ZnApplicationFormUrlEncodedEntity withAll: { > 'foo' -> 'bar'. > 'baz' -> 'quux'. > } asDictionary) > > I just wanted to verify that is, in fact, the shortest way to do this. > I feel as if I'm almost certainly missing a utility method around the > ZnApplicationFormUrlEncodedEntity bit, and, especially for demos, > terseness matters. (It's obviously trivial to write a utility method if > this *is* the shortest way to do this, but then people in the audience > won't be able to execute the resulting code snippet without the utility > method.) > > Thanks, > > --Benjamin >

Oct. 2, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Tudor Girba

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(a)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(a)tudorgirba.com> wrote: > > What is explorer? > > Doru > > On Wed, Oct 1, 2014 at 10:12 PM, stepharo <stepharo(a)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(a)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(a)stfx.eu> wrote: >>>>> >>>>> >>>>> On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com> >>>>> wrote: >>>>> >>>>> >>>>>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)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"

Oct. 2, 2014

ZnEasy and post:data:

by Benjamin Pollack

Hey all, This is probably me missing something, but: for an upcoming presentation, I wanted to find the tersest way to demonstrate making an HTTP POST.Â Something equivalent to Python's requests.post('http://some/thing', data={'foo': 'bar', 'baz': 'quux'}) The closest I could come up with for Pharo was ZnEasy post: 'http://some/thing' data: (ZnApplicationFormUrlEncodedEntity withAll: { 'foo' -> 'bar'. 'baz' -> 'quux'. } asDictionary) I just wanted to verify that is, in fact, the shortest way to do this. I feel as if I'm almost certainly missing a utility method around the ZnApplicationFormUrlEncodedEntity bit, and, especially for demos, terseness matters. (It's obviously trivial to write a utility method if this *is* the shortest way to do this, but then people in the audience won't be able to execute the resulting code snippet without the utility method.) Thanks, --Benjamin

Oct. 2, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Esteban Lorenzano

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(a)tudorgirba.com> wrote: > > What is explorer? > > Doru > > On Wed, Oct 1, 2014 at 10:12 PM, stepharo <stepharo(a)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(a)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(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > > On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: > > > On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)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"

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Tudor Girba

What is explorer? Doru On Wed, Oct 1, 2014 at 10:12 PM, stepharo <stepharo(a)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(a)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(a)stfx.eu> wrote: >>>> >>>> >>>> On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com> >>>> wrote: >>>> >>>> >>>>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)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"

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Tudor Girba

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(a)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(a)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(a)stfx.eu> wrote: >>>> >>>> >>>> On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com> >>>> wrote: >>>> >>>> >>>>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)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"

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Tudor Girba

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(a)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(a)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(a)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(a)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(a)stfx.eu> wrote: >>> >>> >>> On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com> >>> wrote: >>> >>> >>> >>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)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"

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by stepharo

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(a)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(a)stfx.eu> wrote: >>> >>> >>> On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >>> >>>> >>>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)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

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by stepharo

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(a)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(a)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(a)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(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>> >>> >>> On 01 Oct 2014, at 16:00, Andrei Chis >>> <chisvasileandrei(a)gmail.com >>> <mailto:chisvasileandrei@gmail.com>> wrote: >>> >>>> >>>> >>>> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe >>>> <sven(a)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"

Oct. 1, 2014