[Moose-dev] Re: Moose-5.0 #2292 and Search Spotlight?

Ok. I think the problem comes from the fact that the shortcuts are defined only for the stack view. @Andrei: we discussed before that it would be ideal for the debugging actions to be defined for the whole debugger. As it seems, users might get confused with the current solution :)

Doru On Thu, Sep 4, 2014 at 3:33 PM, Tim Mackinnon <tim(a)testit.works> wrote: > I thought i was going to say I couldn’t repro it - but I just noticed > what I did. > > I did a “debug it” in a workspace (don’t think this is important) > (e.g. Date today + 5) > In the debugger I wanted to use a keyboard shortcut for Step Into (its > says Alt-E on the tool tip). None of the shortcuts for the debugger seem to > work on OSX? I’ve tried different combinations - but Alt-E produces a red ‘ > in the source. If you then press Cmd-z to undo it, you will get another ‘ > (not an undo - so its like its in some strange mode). > > I’ve noticed a variation of that - where I had some text selected and > wiped it out with a ‘ - and then undo wouldn’t work either. > > Tim > > On 4 Sep 2014, at 14:24, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Could you tell us how to reproduce the Cmd+z problem? > > Doru > > > > On Thu, Sep 4, 2014 at 3:15 PM, Tim Mackinnon <tim(a)testit.works> > wrote: > >> I was just observing that I love the playground idea - and that >> little triangle is awesome. I just wish I could also make a change in the >> playground and with 1-key press invoke it too ( e.g. cmd-shift-O vs. cmd-a, >> cmd-o). >> >> It’s a minor thing but seems in line with there you seem to be going. >> >> As an aside - are there issues with key-handling in Moose-5. A few >> times now (I think in the debugger), I’ve tried pressing keys like undo >> (cmd-z) and its not undone - but instead put a ` in the text pane? >> >> Tim >> >> On 4 Sep 2014, at 13:59, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I am not sure I understand. >> >> The triangle at the top right is indeed equivalent with Cmd+a, Cmd+o. >> We originally did have a Cmd+O, but we took it out because I could not >> figure out how to make keybindings happy with distinguishing between the >> two properly :( >> >> Cheers, >> Doru >> >> >> >> >> On Thu, Sep 4, 2014 at 2:35 PM, Tim Mackinnon <tim(a)testit.works> >> wrote: >> >>> 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(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> On Wed, Sep 3, 2014 at 4:49 PM, Tim Mackinnon <tim(a)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(a)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 from >>>> https://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(a)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(a)iam.unibe.ch >>>> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> > >>>> > >>>> > _______________________________________________ >>>> > Moose-dev mailing list >>>> > Moose-dev(a)iam.unibe.ch >>>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev