Overall I like the blog post. Leo is such a generic tool (in my mind)
that that's what makes it difficult to define.

>Outlines and organization: Leo's outlines are far more flexible and
>powerful than any other outline you have ever used, for at least three
>reasons:

I think you meant, "any other outliner" (missing the "r")"?

>1. Unlike other browsers, you, not the browser,

A browser to me is Firefox, IE, Safari, Opera, etc. Do you mean an
"outline browser"?

>2. Leo outlines may look like other outlines, but in fact Leo outlines are
>views of a more general underlying graph structure.

The jargon here I don't understand is "graph structure." The word
"graph" to me conjures up images of charts and plotting points on x-y
axes. I've yet to see anything like this in Leo, so I'm obviously not
"getting" the "graph structure" concept. If "graph structure" is akin
to "graph databases" as in the presentation described at
http://preview.tinyurl.com/25zmhdd or the discussion at
http://preview.tinyurl.com/29zfnep, then can you "dumb down" the use
of "graph structure" above? (I did watch the entire Problem Solving
using Graph Traversals presentation and found it fascinating... but
WAY over my head in hopes of my ever grasping it, let alone applying
its concepts.) I'd never even heard of a graph database before August
1. :D

>3.... External files
>2. just as in typical class browsers.

The jargon I don't know here is "class browser" -- is this the same
kind of browser you refer to under "1. Unlike other browsers, you, not
the browser," ? Is a class browser something common in Python
programming? Object-oriented programming? What about those of us who
use neither on a regular basis, if at all? It might be helpful to know
who the intended audience for Leo is, what kind of background is
needed to understand its concepts and use it effectively.

>Here are some of the implications of of this new world:

The word "of" is repeated twice. I wish I had $1000 for every time I
did this myself. I'd have paid off my mortgage years ago. :D

>Design.... There is no need for separate design tools because creating
>a Leo outlines

I think you mean "outline" (singular) here?

>Programming.... Nodes also provide unlimited room to save as many
>details an notes as you like,

I think you mean "and notes" (missing "d")?

>Testing.... 1. You can make node a unit test simply by putting @test at
>the start of its headline.

I think you mean, "make a node" (missing "a")?

Question: Are unit tests confined to Leo itself and Python? Or can it
be used for other programming languages?

>Organization everywhere: Have you noticed that Leo's organizational
>prowess applies to everything?

I =really= like this paragraph. As I said above, Leo is a generic
tool. :D

On Aug 8, 1:18 pm, "Edward K. Ream" <[email protected]> wrote:
> The first draft of a new page of Leo's docs is on my blog:
>
> http://edreamleo.blogspot.com/2010/08/leo-in-nutshell.html
>
> It should be syndicated to Planet Python soon.
>
> I am happy.  "Leo in a nutshell" uses no jargon, yet it does much more
> than just hint at the large array of possibilities in the Leonine
> world.
>
> All comments and suggestions welcome.  These are early days for this
> page.
>
> Edward

-- 
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.

Reply via email to