On Tue, Apr 7, 2015 at 10:02 AM, 'Terry Brown' via leo-editor < [email protected]> wrote:
One particularly powerful / cool Leo behavior I've been noticing > recently is how @button / @rclick / @command code is dynamic, i.e. > change the code in the node and the behavior of the created button, > menu item, or command changes immediately. I know @button has been like > that for long time, but I think @rlick only recently became that way > with some of Edward's recent work, and I'm not sure how long @command > has been that way. > Probably forever. BTW, the recent work uses the *static* text of all such nodes in leoSettings.leo and myLeoSettings.leo. That should not be a problem, imo. In any case, it's unbearable for Leo to open a settings file (briefly, with a screen flash) in order to execute a common script. This is one of those important details! > Anyway, this kind of dynamic environment is a big deal, and you're > right, details matter, but shouldn't obscure or overwhelm the big > picture, the question "how can the Leo system be used?". I think there > are a lot of different answers. > Exactly right. This kind of answer is why you are my chief deputy and my designated successor. Edward -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
