On Feb 22, 7:16 am, "Edward K. Ream" <[email protected]> wrote:
I forgot to ask for your comments about the entire post. I would welcome any ideas you might have for how to build more interactivity into Leo. > At the bare minimum, it would be good to have Leo run unit tests any time the > associated code changes. Leo can do this, given a smallish amount of new > infrastructure. We don't want to run unit tests on every keystroke because most of the time the text will not be syntactically correct. It would, however, be possible to run the test when the body pane *is* syntactically correct, but I have my doubts about whether this would be desirable. Another idea is to extend the run-selected-unit-tests- locally command so that it looks for a clone of the selected node that is a direct child of an @itest node. Experiments would show which approach is most convenient in practice. Edward P.S. Running unit tests locally might work *better* in the @itest world because the *present* body text of the code under test is available to the unit test. We had best be careful: we don't want to hot-change Leo by running unit tests locally! I'll have to give this puzzle some more thought... EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
