Re: Understanding Leo Code

2017-01-13 Thread Edward K. Ream
On Tuesday, January 10, 2017 at 5:46:51 PM UTC-5, rengel wrote: Beyond that, there are many other small annoyances: > - In __doc__ strings, Leo code often states the obvious. Every Python > programmer knows, that __init__ is the constructor. > Leo's cff command often finds matches in multiple

Re: Understanding Leo Code

2017-01-10 Thread Edward K. Ream
​​ On Tue, Jan 10, 2017 at 5:46 PM, rengel wrote: > Leo is not a big ball of mud. >> > > Isn't that in the eyes of the beholder? > ​Sure. But Leo's problems emphatically do not arise from the structure of Leo's classes. They are clean an ​d​ neat. Kinda like an

Re: Understanding Leo Code

2017-01-10 Thread rengel
> > Leo is not a big ball of mud. > Isn't that in the eyes of the beholder? Leo's problems attracting users stem from other sources. Probably the most > important is the need for .leo files. In other words, people are unwilling > to pay even small prices for better tools. > For years, I've

Re: Understanding Leo Code

2017-01-09 Thread Offray Vladimir Luna Cárdenas
Hi, On 09/01/17 15:36, Edward K. Ream wrote: On Mon, Jan 9, 2017 at 7:36 AM, rengel > wrote: This might be of interest to anyone who tries to understand and program Leo code. http://www.laputan.org/mud/mud.html

Re: Understanding Leo Code

2017-01-09 Thread Edward K. Ream
On Mon, Jan 9, 2017 at 7:36 AM, rengel wrote: > This might be of interest to anyone who tries to understand and program > Leo code. > > http://www.laputan.org/mud/mud.html > > It also might help to understand why it seems so difficult to find more > Leo adopters. >