On Mon, Jan 21, 2019 at 3:41 PM Steve Litt <[email protected]> wrote:
> I am going to de-emphasize enhancements. > > Leo is XML. Therefore, then any enhancement on the output end or input > end or both can be done by a separate program using an XML library. Using > separate programs insulates Leo from the debugging hassles and bug > hideouts that would be caused by an enhancement within Leo itself. > Whoa. This is very far from how I think of Leo and its code. True, programs could manipulate the contents of .leo files, but this factoid never enters my mind when I think of enhancing Leo's *python* code base. I've always been a big fan of adding an enhancement to a program I like by > writing an auxiliary program, that demands from the original program no > behavior or definition change or recognition of the auxiliary program. > That's the purpose of Leo's plugins. So if you never again put an enhancement in Leo itself, that doesn't prevent > all sorts of enhancements being made separately. Leo remains encapsulated. > True, but again far removed from how I think about enhancements. Enhancements are typically made to Leo's core, although some do get done in "official" plugins like mod_scripting.py and the qt_* plugins. I spend a lot of time evaluating whether each particular enhancement is worth doing. Many are not. What's new is that I am not going to be chasing after the features of other editors, nor am I going to consider embedding Leonine features into other editors. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
