Great - and I recall you mentioning the inspector trick in a blog post (I just didn’t have the context when I read it).

Small question: Cmd+O isn’t quite the same as the little “Execute and Open” triangle, as it just evaluates the current line/selection. Am I right in thinking you have to do Cmd+a, Cmd+o to get the same effect? I thought I saw people doing something else (but I might have misunderstood). I really like the idea of the “Execute and Open” in one step - as it really embodies the idea of a playground - which is really cool. Would it be hard to add a keystroke for that?

Tim

On 3 Sep 2014, at 15:57, Tudor Girba <tudor@tudorgirba.com> wrote:

Hi,

On Wed, Sep 3, 2014 at 4:49 PM, Tim Mackinnon <tim@testit.works> wrote:
Thanks Uko - I’m happy to use Tab (is that the same in the editor as well?).

On a similar note - is there anything that documents the keystrokes available in Moose? I recall people mentioning things for Opening an inspector in the same window vs. new window (or something like that in GT-Inspector)?

You can find the keystrokes by inspecting the morph you want to investigate. For example:
- open a Playground
- Ctrl+Shift click to bring the halos on the text editor
- Inspect
- In the inspector, get to the RubEditingArea (use the Submorphs tab)
- Select it, and in the right pane choose the Keys tab
 
I also haven’t figured out how you execute code in a playground via a keystroke vs. pressing the little triangle in the top bar (again I saw people at ESUG press something when doing Roassal demos).

Cmd+d = do it
Cmd+i = inspect it
Cmd+o=open it (it's like inspect, only it spawns to the right)

Cheers,
Doru
 

Tim

On 3 Sep 2014, at 15:37, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:

> So the latest version is indeed unreleased 5.0 which is available from CI. 4.9 is 1 year old. Autocomplete settings are changed in Moose because default ones annoy some people. To get suggestions you have to press tab. You can change your setting to match default Pharo ones automatically by putting first file fromhttps://gist.github.com/Uko/7672537#file-completion-st into your ~/Library/Preferences/pharo/
>
> Cheers.
> Uko
>
>
> On 03 Sep 2014, at 16:29, Tim Mackinnon <tim@testit.works> wrote:
>
>> Hi guys - I was really amazed by the advances I saw being made in Moose at ESUG and so I’ve downloaded the latest 2292 image (using Pharo Launcher) to give things a spin.
>>
>> Can I first check that this is the image I should use? I checked out the stable 4.9 version - but it doesn’t seem to have the playground that I observed people using at ESUG and seemed slicker? I should also say that I don’t mind if its a bit wobbly, as I figure I might as well help test the latest version.
>>
>> Assuming this is the right version - I notice that on OSX when I press Shift-Enter (to spotlight search code), it doesn’t give me any auto-completed items like it does in Pharo (e.g. Typing “Order” doesn’t start showing any classes). I noticed this was broken in a version I downloaded at ESUG as well, so I took the latest just to check.
>>
>> Tim
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev@iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev@iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



-- 

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev