Re: Leo in 5 minutes

[john lunzer]

I think what you said about the "over the shoulder" concept of learning is 
potentially the most powerful way to bring people up to speed. Some people 
will still prefer traditional "read the docs" style documentation but many 
will prefer narrated "demo.py" style demos showing them *exactly* what Leo 
is capable of.

I believe YouTube is the best place host these demos as it offers the 
"playback speed" setting which in my experience has been critical to me 
watching any technical/instructive videos.  

On Saturday, February 11, 2017 at 5:44:59 PM UTC-5, Edward K. Ream wrote:
>
> Here is the first draft for a new intro to Leo's tutorials, Leo in 5 
> minutes.  Let me know what you think.
>
> *Outlines*
>
> Leo is a full-featured outliner and IDE, with features borrowed from emacs 
> and vim. When Leo reloads an outline, it remembers where you left off.
>
> Outlines consists of *nodes *with *headlines* and *bodies*. The *outline 
> pane* shows nodes. The *body pane* contains the body of the selected node.
>
> *External files*
>
> - @file trees in the outline represent *external files* on your file 
> system. Leo *updates @file nodes* when you change external files outside 
> of Leo.
>
> - When saving an outline, Leo writes all changed @file trees to their 
> external files.
>
> *Scripting and markup*
>
> - Leo's *markup language* consists of`@others` and `<< sections >>`. 
> Markup controls how Leo writes @file trees to external files.
>
> - Any outline node can contain a python script. Three *predefined symbols* 
> give Leo scripts *easy *access to all the structure and data in the 
> outline.
>
> - The same markup applies to scripts as well as external files. Before 
> executing a script node, Leo *composes *the script from the script node 
> and (depending on markup) some or all of its descendants.
>
> - @button nodes contain scripts that *can be applied to other nodes*.
>
> *Clones*
>
> - Outline nodes can be *cloned*. Cloned nodes are actually the *same *node, 
> but they appear in different places in the outline. *Changes to any clone 
> affect all other clones of that node, including their descendants*. 
> Clones are a powerful organizing tool.
>
> - Leo's *clone-find* commands create clones of all found nodes. The 
> clone-find commands move the newly-created clones so they are all children 
> of an organizer node describing the search.
>
> *Summary*
>
> @file nodes create external files. Guided by markup, Leo writes @file 
> trees to external files. Leo updates @file trees when external files change 
> outside Leo. Leo's importers create outlines from external files.
>
> Leo composes complex scripts from a node and (depending on markup) some or 
> all of its descendants. Leo scripts have access to all data in the outline, 
> including its structure.
>
> Clones are nodes that appear in multiples places within the outline. Leo's 
> clone-find commands gather found nodes together in one place.
>
> *Ironic Comments*
>
> The "less said the better" principle has allowed me, *for the first time 
> ever*, to summarize Leo's essential an unique features in just a few 
> words. This summary probably seems pretty clear to Leonistas. However, I 
> wonder how much newbies will understand.
>
> There are two ways forward.
>
> 1. Explain the pithy summary above using *text* examples, including text 
> representations of Leo's outline structure. We must do this for the written 
> docs, but text only hints at Leo's dynamic nature.
>
> 2. Use this post as a preliminary script for a demo, eventually to appear 
> on YouTube. I'll attempt this soon.
>
> Your comments and suggestions, please.
>
> Edward
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Leo in 5 minutes

[Edward K. Ream]

Here is the first draft for a new intro to Leo's tutorials, Leo in 5 
minutes.  Let me know what you think.

*Outlines*

Leo is a full-featured outliner and IDE, with features borrowed from emacs 
and vim. When Leo reloads an outline, it remembers where you left off.

Outlines consists of *nodes *with *headlines* and *bodies*. The *outline 
pane* shows nodes. The *body pane* contains the body of the selected node.

*External files*

- @file trees in the outline represent *external files* on your file 
system. Leo *updates @file nodes* when you change external files outside of 
Leo.

- When saving an outline, Leo writes all changed @file trees to their 
external files.

*Scripting and markup*

- Leo's *markup language* consists of`@others` and `<< sections >>`. Markup 
controls how Leo writes @file trees to external files.

- Any outline node can contain a python script. Three *predefined symbols* 
give Leo scripts *easy *access to all the structure and data in the outline.

- The same markup applies to scripts as well as external files. Before 
executing a script node, Leo *composes *the script from the script node and 
(depending on markup) some or all of its descendants.

- @button nodes contain scripts that *can be applied to other nodes*.

*Clones*

- Outline nodes can be *cloned*. Cloned nodes are actually the *same *node, 
but they appear in different places in the outline. *Changes to any clone 
affect all other clones of that node, including their descendants*. Clones 
are a powerful organizing tool.

- Leo's *clone-find* commands create clones of all found nodes. The 
clone-find commands move the newly-created clones so they are all children 
of an organizer node describing the search.

*Summary*

@file nodes create external files. Guided by markup, Leo writes @file trees 
to external files. Leo updates @file trees when external files change 
outside Leo. Leo's importers create outlines from external files.

Leo composes complex scripts from a node and (depending on markup) some or 
all of its descendants. Leo scripts have access to all data in the outline, 
including its structure.

Clones are nodes that appear in multiples places within the outline. Leo's 
clone-find commands gather found nodes together in one place.

*Ironic Comments*

The "less said the better" principle has allowed me, *for the first time 
ever*, to summarize Leo's essential an unique features in just a few words. 
This summary probably seems pretty clear to Leonistas. However, I wonder 
how much newbies will understand.

There are two ways forward.

1. Explain the pithy summary above using *text* examples, including text 
representations of Leo's outline structure. We must do this for the written 
docs, but text only hints at Leo's dynamic nature.

2. Use this post as a preliminary script for a demo, eventually to appear 
on YouTube. I'll attempt this soon.

Your comments and suggestions, please.

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: About org mode

[Israel Hands]

Hi EKR - I am a very lightweight user of both Leo and org-mode - for me the 
killer dimension of org-mode is the Agenda view with the integrated diary 
and the ability of org-mode to throw up reminder dialogues. For me at least 
todo lists tend to be dead letter unless they reach out to me.  The ability 
to hold todo items and diary items together is the gold and means EMACS is 
the first thing I run - just before Leo.  
While we are on the topic of what keeps us in different places Auctex is 
probably the other thing or was the other thing that kept me on Emacs 
however I now use Scrivener MMD compiled to Latex - I feel bad about this. 
Scrivener has lots of nice features but I know that Leo would be better 
it's just a matter of the set up learning curve.  A really easy Latex set 
up would be another winner. 


IH

On Friday, 10 February 2017 22:21:20 UTC, Edward K. Ream wrote:
>
> I finished watching this superb video about org-mode 
>  earlier today.  I took 
> copious notes.
>
> It has inspired many thoughts, and will continue to do so. I expect this 
> conversation to be long lasting and fruitful.  Some *brief* first 
> thoughts:
>
> 1. The demo looked off the cuff. Each topic had its own org-mode "page" 
> containing the script for that page. It looks like Camtasia did the post 
> production. This is a perfectly reasonable, perhaps superior, alternative 
> to totally controlled demos using demo-it.el or demo.py.
>
> 2. After the first few minutes, the presentation had almost nothing to do 
> with outlines!
>
> 3. The demo shows that Leo must have better rendering *in the body pane, 
> not* a separate rendering pane.
>
> 4. Imo, the real difference between Leo and Emacs lies differing 
> approaches to multiple buffers and screen real estate. Both ways have 
> pluses and minuses.  Discussing the nuances should be fascinating.
>
> 5. Leo can (and will) soon have *everything* that org-mode has. Otoh, 
> that will likely not be enough to cause an exodus from Emacs to Leo.  
> Still, Leo has features that org-mode will likely never have. It reminds me 
> of the song, Anything you can do, I can do better 
> .
>
> More to come later.
>
> Edward
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Turning to documentation

[Edward K. Ream]

On Friday, February 10, 2017 at 9:28:39 AM UTC-6, Edward K. Ream wrote:

I want to emphasize something.  Demo scripts can use *all *parts of Leo's 
> API to "run" Leo automatically. For example, this is one way to create a 
> new node:
>
> p = c.insertHeadline()
> p.h = 'a headline'
> p.b = 'some body text'
>

Recent revs make this work properly. See the change log 
.
 
There were some tricky issues with control and screen refresh.  The summary:

demo.start now takes an "auto_run=False" keyword arg. When True, demo.start 
runs each demo script one after the other. The demo.auto_run ivar is a copy 
of this arg. As shown in the example top-level script 
,
 
demo.teardown could insert inter-slide delays when self.auto_run is True.

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: About org mode

[Largo84]

I would love to be able to do most of what he demonstrated in that video 
with Leo and org-mode. Maybe I can now, but just haven't figured out how 
yet. Great stuff!

BTW, search the Leo web site documentation for `org-mode` and nothing comes 
up. However, search for `org mode' and several results come up. Very 
weird...

Rob..

On Friday, February 10, 2017 at 5:21:20 PM UTC-5, Edward K. Ream wrote:
>
> I finished watching this superb video about org-mode 
>  earlier today.  I took 
> copious notes.
>
>
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.