Posting to an old thread just to keep in context, also relates to this
https://groups.google.com/d/msg/leo-editor/qSA-E9-hj4Q/aSX0E-PeyLsJand
(tangentially) to
thishttps://groups.google.com/d/msg/leo-editor/7ikGpR_J8bM/JeNJqzJdDC8J
.
Chris Granger: Connecting to your
This is a long post. It deals with tangential topics that may
interest some greatly, and others not at all. Feel free to ignore.
After watching the video, I said that I would have to learn
JavaScript. I got a lot of excellent suggestions for study, including
various well-known videos.
On Feb 22, 7:16 am, Edward K. Ream edream...@gmail.com 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
On Wed, Feb 22, 2012 at 7:39 AM, Edward K. Ream edream...@gmail.com wrote:
On Feb 22, 7:16 am, Edward K. Ream edream...@gmail.com 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.
I'd guess
I've been thinking about how to intersperse code and tests generally,
(not just for python).
I'm considering just doing it under a, say:
@codetest codeFile testFile
The subtree would have code nodes with say:
@testF
nodes to hold tests.
A script would collect the code nodes under an '@file
This *might* work, but I have concerns. One one hand, we want
interactive unit tests to be close (in the outline) to the code being
tested, so that we can work on the unit test in tandem with the code
being testing. Otoh, we *don't* want interactive unit tests to be
close to the code being
