>
> Leo is almost tragic in how powerful it is, and how much its adoption is
>> held back by poor documentation. Good documentation will be a major
>> endeavour, but well worth it.
>>
> [...]
>
Newbies only need to know how to search outlines, and which outlines to
> search, especially
>
> Any node, but @test or @button nodes are easiest to use.
>
> Is that defined somewhere?
>>
>
> Yes, in the next sentence.
>
The sentence can be parsed in two ways:
"This node (in the Leo outline) defines your development environment. You
can use an @test node, an @button node, or an @command
>
> My conceptual solution to this was/is "What If Topics Were Folders?",
> topics being the twiki version of Nodes. Basically: every topic is a
> container, within the container if the default file exists, display that
> using the filetype's default rendering mechanism (think web servers and
Funny you should bring up a third dimension, I've been experimenting
with something along these lines, although not within Leo :-/ No
doubt inspired by various discussions on this list (sea of nodes,
colored threads, Kent's mysterious extra dimensions :-). Data model
is basically a set of nodes
On Friday, October 12, 2018 at 4:33:18 AM UTC-5, Edward K. Ream wrote:
*> Leo outlines could benefit from a third dimension.*
One way to "fake" a third dimension in an external .py file is with a
"compile-time" test:
<< define factorial >>
if g.unitTesting:
- << define @test nodes >>
In the "Dreaming Big Dreams" post I asked, Why can't we put unit tests near
the code being tested?
In the "Unit Testing Nodes" thread I suggested two ways to put unit tests
near code:
1. Use doctests. The node will end with something like:
doctest.run_docstring_examples(factorial, globals(),
On Thursday, October 11, 2018 at 4:17:07 PM UTC-5, MN wrote:
> What is a dev node?
Any node, but @test or @button nodes are easiest to use.
Is that defined somewhere?
>
Yes, in the next sentence.
Suppose I have a node whose contents are:
>
> from operator import mul
>
> def
