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. > Like I said, at that level of complexity I should have implemented a > plugin, which I still plan to do. > > One more thing, Jon, if you do implement a plugin then you would be able > to share code in all the usual Python ways, ie, functions, classes, and > modules. >
Yes, thanks Terry, that was useful as a summary of that approach, even if it's not what I will do (yet)... Also thanks to John for the plugin summary. I have some functionality that I may do as a plugin, but this work is very specific to one .leo file which is why I want it to live as an @command node(s) Oh (Jacob/Edward) ... I assume your use of '@common' is a convention within your code, ie. '@common' has no code-based meaning within Leo otherwise? I see reference to it here: http://leoeditor.com/unitTesting.html#using-mark-for-unit-tests but nowhere else. Regards Jon N -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.