On Fri, May 25, 2012 at 8:01 PM, tfer <[email protected]> wrote: > Here is what I've got for the abstract of the talk:
Hi Tom, Imo, the abstract should attempt to convey why you think Leo is a paradigm shift. Stress what is unique in Leo, and essentially nothing else. > Leo is an outliner, each node in a leo outline has two parts, a headline - a > single line topic, and its body text, either of which can be blank. > Headlines are displayed in the "outline pane" their position and indent > level give a visual representation of the outlines hierarchical tree > structure. Whenever a headline is selected in the outline pane, its body > text will be visible in the body pane. So far, Leo sounds utterly unremarkable. You might consider deleting, or drastically shortening it. Something like, "Leo looks like a typical outlining program. However, ..." > The files in your project head up > their own subtree in the outline, the root of each has a special headline > that names the file to create/update from the body text of its descendants. > A template, usually in the body text of that special headline, determines > how the body text in each descendent will be gathered up to generate the > named file on each save. I like your use of the term "template". It's evocative, and allows you to avoid details about @others and sections. In fact, any node can contain a template, in the sense you mean it. I also like that you didn't discuss @file nodes explicitly. You might shorten the description still further by saying something like: "designated parts of Leo outlines can correspond to external text files." > Using this system allows you to lay out and > organize your different areas of functionality your code will implement, > then write code, or write code and then organize, or mix this up however you > are drawn to do. Rearranging code is easy, just move the headlines around > and the code in the associated body text is moved too. Not bad. I might be shorter. > Commenting code in body text is cheap and easy, by default text entered into > a body starts a free form, wrapped comment, when you want to start your > code, just put the "code-start", (@c -- short for @code) directive on a new > line, then write your code below it. However, there is another, implicit > type of commenting available through the headlines, just give the headline a > short sentence about what your up to in that nodes descendents. You can use > this to quickly capture what you intend you code to do, and then come back > later and write the code. I would delete this from the abstract, and probably from the talk. It is a relatively unimportant. > The ability of outlines to capture, but then hide details to allow you to > shift your focus to another area of the system is one of Leo great > strengths. Yes. There are at least four unique aspects of Leo you haven't mentioned: 1. The two-way correspondence between external files and Leo outlines. 2. uA's extend what each node may contain. 3. Leo's dead-simple Python DOM: iterators, p.b, p.h, p.v and p.v.u. 4. @button and plugins. HTH. 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.
