Re: Discusss: use Discourse instead of mailing list

On Sat, Aug 31, 2019 at 5:44 PM Chris George wrote: > So I broke my leg this morning. > Ouch! So sorry to hear that. Since I will have a fair bit of downtime coming up I would be happy to > work on the import/backup to see what can be done. > > Edward, would you like me to apply and get starte

Active settings outline: status report

In another thread I said, "I'm going to do #852 : (active settings outline) first. I think I can do this in a few hours [sic] to a few days. It's a frequently requested feature." I spent about 15 hours on yesterday, from 2 am to 7pm, with j

Re: Active settings outline: status report

> > Given the complexities of the code, I simply do not understand how anyone > can be confident that proposed changes would work *exactly* as before. > After 15 hours of intense study, I don't understand the code well enough to > have any confidence in *any* real changes to the code. > > If

Re: Active settings outline: status report

On Sun, Sep 1, 2019 at 5:13 AM vitalije wrote: If you, a rather clever, smart, experienced developer and also the author > of this code, after 15 hours of intense study do not fully understand the > code, shouldn't that tell you something about the quality of the code? If > you cant fully underst

Re: Active settings outline: status report

On Sunday, September 1, 2019 at 3:53:51 AM UTC-5, Edward K. Ream wrote: The aso.start method, and its helpers, now appears to recreate the required > initing of settings *exactly* as is done in Leo's startup code. *Subtle > bugs will abound if it doesn't*. > Oh joy. There is a simple way arou

Re: Active settings outline: status report

> > Insulting comments about the code's quality shows engineering immaturity. > Yes, the code is difficult. That in no way proves that it could be > simplified safely. > I am truly sorry if you read my comments as insulting. That was never my intent. Do you really think I would try to get you

Re: Active settings outline: status report

On Sunday, September 1, 2019 at 7:29:59 AM UTC-5, Edward K. Ream wrote: I would be happy to make the code simpler if I knew how to do this without > damaging Leo. > Aha! I see a way forward. To gain my approval, you would have to convince me of the following: > > Requirement 1. That users pre

Re: Active settings outline: status report

On Sunday, September 1, 2019 at 8:20:31 AM UTC-5, vitalije wrote: Insulting comments about the code's quality shows engineering immaturity. >> Yes, the code is difficult. That in no way proves that it could be >> simplified safely. >> > > I am truly sorry if you read my comments as insulting.

Re: Active settings outline: status report

On Sun, Sep 1, 2019 at 6:13 AM vitalije wrote: > I am tempted to put aside all my current tasks and write my own > launchLeo.py which will monkey patch completely cofiguration code and just > read settings from the database table. I guess it would greatly reduce > number of code lines that has to

Re: Active settings outline: status report

On Sun, Sep 1, 2019 at 8:32 AM Brian Theado wrote: > I...discovered leo can be started without reading any .leo files at all. Just delete config/leoSettings.leo and then run it like this: HOME=$HOME/tmp/blank python launchLeo.py ~/tmp/new.leo Clever and creative. The prototyping unit test f

Re: Active settings outline: status report

On Sunday, September 1, 2019 at 8:27:09 AM UTC-5, Edward K. Ream wrote: This is a breakthrough, in two, no three ways: > And there is a fourth breakthrough. The faux unit test allows for *controlled, limited* changes to how Leo's long-suffering users actually perceive settings. For example, a

Re: Discusss: use Discourse instead of mailing list

On Saturday, August 31, 2019 at 7:44:34 PM UTC-3, Chris George wrote: > > So I broke my leg this morning. > > Ups! I hope it's not serious and you get well soon! > Since I will have a fair bit of downtime coming up I would be happy to > work on the import/backup to see what can be done. > T

Re: Active settings outline: status report

On Sunday, September 1, 2019 at 8:48:15 AM UTC-5, Edward K. Ream wrote: > Vitalije, should you choose to accept it, I would like to name you as lead engineer for the prototyping unit test. I have just created #1314 for this. Edward -- Yo

Re: Discusss: use Discourse instead of mailing list

On Sun, Sep 1, 2019 at 9:00 AM Xavier G. Domingo (xgid) wrote: I think we should not ask just Edward, but the whole community. 😃 > I agree. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receivin

Re: Discusss: use Discourse instead of mailing list

> > Actually, I am thinking that we should just stick with Leo's existing > forum and issue tracker. I don't see any major benefits to changing how we > communicate. > > Edward > Jeje, it's weird to hear that from the author of a piece of software that *is* changing the way we work with code

Re: Discusss: use Discourse instead of mailing list

> Discourse and similar tools are doing the same for communication and > community building. > I have just read https://www.discourse.org/testimonials and here are some of the quotes that resonated the most with my own feelings about Discourse: *“It’s really oriented towards community* and c

Re: Active settings outline: status report

On Sun, Sep 1, 2019 at 9:37 AM vitalije wrote: I gladly accept the challenge. > Thank you! > I am not sure what you mean by unit test, but here is how I see it. > In this context, a unit test is simply a script that verifies, in some unspecified way, that exiting code works. It can also be ap

Re: Active settings outline: status report

On Sunday, September 1, 2019 at 12:46:51 PM UTC-5, Edward K. Ream wrote: Some second thoughts. We have drastically changed mind sets. In my previous thinking, everything was dangerous. In the context of the new testing script, everything is allowed. The overall goal is to know where we have b