On Tue, Aug 5, 2014 at 12:45 PM, 'Terry Brown' via leo-editor <[email protected]> wrote:
> Interesting and not that complex after all: Thanks for this. There are many ast-oriented classes in leoSTC.py which may or may not be of interest to you. As for the lisp music demo, I think there is a large element of showmanship going on. It looks all very mysterious and magic, largely because the lisp code is entirely undocumented ;-) I have watched the demo multiple times. Each time I do so the technology seems less impressive. The *only* interesting part of the demo from a technical perspective are the "yellow flashes". Unless I am mistaken, these indicate that the code is being evaluated and sent to the background processor. Any kind of data could be sent to the background. It might be convenient to send lisp code, but but Python or yaml might be clearer. However, clearer has the disadvantage (during performances) of not being so geeky ;-) Put another way, all that matters is that a) the background process can drive the pianos, and b) there is a way, asynchronously, to send data (including programs) to the background. For all the reasons you mention it would be good to have a way of interacting asynchronously with free-running scripts in other threads. So much the easier if those scripts never try to change data within Leo. Edward ------------------------------------------------------------------------------------------ Edward K. Ream: [email protected] Leo: http://leoeditor.com/ Speak the truth, but not to punish--Thich Nhat Hanh ------------------------------------------------------------------------------------------ -- 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.
