Re: My last lecture. Part 1: Why Leo is noteworthy

On Tuesday, October 20, 2015 at 11:08:56 AM UTC-5, Edward K. Ream wrote: > > This post discusses what I think matters most about Leo. > I have reposted this on my blog here . I've left it almost completely unchanged, except for

Re: My last lecture. Part 1: Why Leo is noteworthy

On Thu, 5 Nov 2015 09:50:32 -0800 Don Dwiggins wrote: > Well, I wouldn't go as far as Marcel, but there is a tension here > between brevity and general comprehensibility. Ed, you've lived and > breathed Leo for years, so those particular single letter names are > probably etched in your neura

Re: My last lecture. Part 1: Why Leo is noteworthy

Well, I wouldn't go as far as Marcel, but there is a tension here between brevity and general comprehensibility. Ed, you've lived and breathed Leo for years, so those particular single letter names are probably etched in your neural circuitry. Others, however, might have more difficulty learn

Re: My last lecture. Part 1: Why Leo is noteworthy

Aha! It's good to hear this praise from a fellow Ecco user. It gives me some confidence that the investment will be well repaid. Rob, do you have any advice for someone following in your footsteps? (If this isn't appropriate for this group, write me offline: don, of the domain dondwiggins d

Re: My last lecture. Part 1: Why Leo is noteworthy

Synchronicity is funny. I had just read about this in one of my course readings. *Shu (obey)*. In this beginning stage, the student follows the teachings of one master precisely. He concentrates on how to do the task, without worrying too much about the underlying theory. If there are multiple

Re: My last lecture. Part 1: Why Leo is noteworthy

On Tue, Oct 27, 2015 at 10:39 AM, Jacob Peck wrote: > On 10/27/2015 11:34 AM, Edward K. Ream wrote: > > Imo, nobody could grok these advantages by reading documentation or > reviews. I just had to immerse myself in the new language. Probably the > same is true about Leo programming. > > I just

Re: My last lecture. Part 1: Why Leo is noteworthy

On 10/27/2015 11:34 AM, Edward K. Ream wrote: Imo, nobody could grok these advantages by reading documentation or reviews. I just had to immerse myself in the new language. Probably the same is true about Leo programming. I just have to say that this is perhaps the single most salient line in

Re: My last lecture. Part 1: Why Leo is noteworthy

On Tue, Oct 27, 2015 at 7:59 AM, john lunzer wrote: > This is a good summary of Leo's history and capabilities. Because this > thread has been met with some... criticism I will provide my reaction and > some guidance for further posting. > ​Thanks for your comments. ​ They are spot on.​ ​> ​ T

Re: My last lecture. Part 1: Why Leo is noteworthy

This is a good summary of Leo's history and capabilities. Because this thread has been met with some... criticism I will provide my reaction and some guidance for further posting. Firstly, this is likely not the thread for criticism of Leo's design decisions. Edward and friends are capable pro

Re: My last lecture. Part 1: Why Leo is noteworthy

On 22/10/15 13:35, Offray Vladimir Luna Cárdenas wrote: As I said, Leo is a source of inspiration. I have differences with it, and the play to deploy them is my own outliner, but also I recognize powerful ideas it brings. I mean: "and the plan to deploy them is my own outliner". Cheers

Re: My last lecture. Part 1: Why Leo is noteworthy

Hi, On 22/10/15 09:12, Marcel Franke wrote: Offray Vladimir Luna Cárdenas wrote: This idea of an always present outline has been key to me for organizing writings. Some coworkers have found in the past that this helps them when we're correcting their text. On a sightly off-topi

Re: My last lecture. Part 1: Why Leo is noteworthy

Some ideas, like more readable code of Leo with non single letter are easier to implement in other places. That doesn't diminish the utility/worth of Leo, is just that is not the proper medium for some ideas. Cheers, Offray On 22/10/15 11:57, Ville M. Vainio wrote: On single-letter names: .h

Re: My last lecture. Part 1: Why Leo is noteworthy

On single-letter names: .h and .b are "archetypal" properties of a position. Think i,j and k in for-loops. There are only a couple of properties like that. Longer names, while helping in the first few minutes of investigating the API, would soon become tedious "nagging". On Wed, Oct 21, 2015 at 5:

Re: My last lecture. Part 1: Why Leo is noteworthy

Edward K. Ream wrote: ​Unconvincing.​ > > >> > What surprise... ​The naming principle I use is this: the more important the name, the > shorter it should be. > That is obvious, and it is still wrong. If you want your comments to be taken seriously, you should refrain from > nit

Re: My last lecture. Part 1: Why Leo is noteworthy

Offray Vladimir Luna Cárdenas wrote: This idea of an always present outline has been key to me for organizing > writings. Some coworkers have found in the past that this helps them when > we're correcting their text. On a sightly off-topic, most of them are > school teachers making their maste

Re: My last lecture. Part 1: Why Leo is noteworthy

On Wed, Oct 21, 2015 at 9:37 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > Leo is a superb tool for understanding, studying and organizing any kind > of complex data, including computer programs. > > That's why I think that Leo should be easy to install by "anyone". The > potenti

Re: My last lecture. Part 1: Why Leo is noteworthy

On Wed, Oct 21, 2015 at 9:29 AM, Marcel Franke < kugelfischtemp...@googlemail.com> wrote: > > Edward K. Ream wrote: > >> >> ​How would you improve, say: >> >> for p in c.all_positions(): >> print(p.h) >> > > > > for position in commander.find(all=True): > > print(position.headline) > >

Re: My last lecture. Part 1: Why Leo is noteworthy

On Tue, Oct 20, 2015 at 11:08 AM, Edward K. Ream wrote: > This post discusses what I think matters most about Leo. This post assumes > you are an experienced Leo user. It does not try to duplicate Leo's > Tutorial . > ​Here are my brother Speed's comments: Q

Re: My last lecture. Part 1: Why Leo is noteworthy

Hi, Some typos: On 21/10/15 09:37, Offray Vladimir Luna Cárdenas wrote: Thanks Edward for this pre-writing. Hopefully we can contribute in a constructive way. Some comments below. On 20/10/15 11:08, Edward K. Ream wrote: This post discusses what I think matters most about Leo. This post assu

Re: My last lecture. Part 1: Why Leo is noteworthy

On 21/10/15 09:02, Offray Vladimir Luna Cárdenas wrote: Hi, On 21/10/15 08:22, Edward K. Ream wrote: On Wed, Oct 21, 2015 at 1:40 AM, Marcel Franke > wrote: Edward K. Ream wrote: Leo's API consists primarily of *generators*, such as

Re: My last lecture. Part 1: Why Leo is noteworthy

Thanks Edward for this pre-writing. Hopefully we can contribute in a constructive way. Some comments below. On 20/10/15 11:08, Edward K. Ream wrote: This post discusses what I think matters most about Leo. This post assumes you are an experienced Leo user. It does not try to duplicate Leo's T

Re: My last lecture. Part 1: Why Leo is noteworthy

Edward K. Ream wrote: Leo's API consists primarily of *generators*, such as c.all_positions(), >>> p.self_and_subtree(), etc. and *properties*, such as p.b, p.h, p.gnx >>> and p.v.u. >>> >> >> One thing I always wondered about...is there a reason why Leos API is so >> unpythonic? >> > > ​How

Re: My last lecture. Part 1: Why Leo is noteworthy

Hi, On 21/10/15 08:22, Edward K. Ream wrote: On Wed, Oct 21, 2015 at 1:40 AM, Marcel Franke > wrote: Edward K. Ream wrote: Leo's API consists primarily of *generators*, such as c.all_positions(), p.self_and_subtree(), etc. and

Re: My last lecture. Part 1: Why Leo is noteworthy

On Wed, Oct 21, 2015 at 1:40 AM, Marcel Franke < kugelfischtemp...@googlemail.com> wrote: > > Edward K. Ream wrote: > > Leo's API consists primarily of *generators*, such as c.all_positions(), >> p.self_and_subtree(), etc. and *properties*, such as p.b, p.h, p.gnx and >> p.v.u. >> > > One thing I

Re: My last lecture. Part 1: Why Leo is noteworthy

Edward K. Ream wrote: Leo's API consists primarily of *generators*, such as c.all_positions(), > p.self_and_subtree(), etc. and *properties*, such as p.b, p.h, p.gnx and > p.v.u. > One thing I always wondered about...is there a reason why Leos API is so unpythonic? > AFAIK, these capabil

Re: My last lecture. Part 1: Why Leo is noteworthy

This post makes me realize (again) how much of Leo I don't understand or use. I use Leo just about every day for work and personal writing (mostly LaTex and some HTML). I didn't think I would find a tool to replace ECCO, but Leo proved up to the task (I never use ECCO anymore except to print ca

My last lecture. Part 1: Why Leo is noteworthy

This post discusses what I think matters most about Leo. This post assumes you are an experienced Leo user. It does not try to duplicate Leo's Tutorial . This post will be pre-writing for a version that will be posted to Leo's web site. All comments are welc