What I often do is that I write a test and then I just execute the code. When it runs into the non-existent method, the debugger offers a button "create" method.
Alternatively I do open a second browser (clicking on "scoped" in the current one or like that (or doubleclicking on a method to get the same method opened in a new browser) Peter On Fri, Oct 6, 2017 at 12:15 PM, Dirk Olmes <d...@xanthippe.ping.de> wrote: > Hi, > > I may be asking an absolute noob question but I was unable to find any > useful hints on google ... > > I often find myself writing methods that do not yet exist when > implementing other methods, e.g. when I'm writing the implementation of > methodA I'm calling out to methodB. > > What's the easiest way to create the new method? I know I can jump > aroung through hoops with a separate browser but that feels cumbersome. > > I understand that the editor/runtime/whatever cannot know 100% of the > time where to put the new method but at least for messages to self it > should be smart enough to offer some kind of help. > > -dirk > >
