Re: how to share @command functionality between nodes?

On Tue, Feb 16, 2016 at 3:07 PM, jkn wrote: For some reason your posting above made a lot more sense after looking at > leo/scripts/scripts.leo > > There are aspects I don't get grok about this but I have enough to play > with... > ​It's important to understand that Leo

Re: how to share @command functionality between nodes?

Thanks Edward On Monday, February 15, 2016 at 3:55:26 PM UTC, Edward K. Ream wrote: > > On Fri, Feb 5, 2016 at 3:20 PM, jkn > wrote: > >> >> does the whole body of an @command script have to live within a single >> node? >> > > ​Not at all. @button and @command nodes

Re: how to share @command functionality between nodes?

On Fri, Feb 5, 2016 at 3:20 PM, jkn wrote: > > does the whole body of an @command script have to live within a single > node? > ​Not at all. @button and @command nodes can use sections and @others. Indeed, for complex scripts my pattern is: << imports >> @others x =

Re: how to share @command functionality between nodes?

On Tuesday, February 9, 2016 at 11:55:40 AM UTC, john lunzer wrote: > > Thanks for clearing/summing everything up Terry. It wasn't 70 nodes on the > first level, it was 70 children and subchildren. I set up several > subclasses of QFrame and handle a whole host of QShortcut key sequences. >

Re: how to share @command functionality between nodes?

Thanks for clearing/summing everything up Terry. It wasn't 70 nodes on the first level, it was 70 children and subchildren. I set up several subclasses of QFrame and handle a whole host of QShortcut key sequences. Like I said, at that level of complexity I should have implemented a plugin,

Re: how to share @command functionality between nodes?

On Mon, 8 Feb 2016 06:07:33 -0800 (PST) john lunzer wrote: > I'm a little confused by your request and perhaps Jacob answered it > but I feel like I heard a much simpler question. > > You can use the @others directive in the body of you @command node. > This is the same as

Re: how to share @command functionality between nodes?

I'm a little confused by your request and perhaps Jacob answered it but I feel like I heard a much simpler question. You can use the @others directive in the body of you @command node. This is the same as what you would do in an @ node. I have abused this horribly to my own ends to write a

Re: how to share @command functionality between nodes?

You are correct, the @others is just a node body directive and doesn't dictate where or how a file will be stored, only the structure of the file. If you're just personal commands which you don't intend on sharing then you'll likely just want to keep them in your myLeoSettings.leo file and

Re: how to share @command functionality between nodes?

Hi John On Monday, February 8, 2016 at 2:07:33 PM UTC, john lunzer wrote: > > I'm a little confused by your request and perhaps Jacob answered it but I > feel like I heard a much simpler question. > > You can use the @others directive in the body of you @command node. This > is the same as what

Re: how to share @command functionality between nodes?

At the top of your @command node, you can do something like: eval(g.findTestScript(c,'@common code')) Where '@common code' is the name of a node somewhere in your outline. (Thanks to Edward for that one, 3 years ago now! Wow, hard to believe I've been using Leo that long...)