I really like the clarity that comes after tempest in Leo community and how it reinforces Leo core proposals and unique values.
Nice to have Edward in a more playful explorative mode again, putting stuff like Lua or Pharo in his radar. Despite I would like to see live coding coming to Leo, I have already found a path to explore this in an outlining environment and for sure it will not be implemented if is not a joy/pain suffered first hand by Leo users/devs so may this playful attitude bring a lot of interesting paths to follow. Cheers, Offray On 17/1/19 12:59, Edward K. Ream wrote: > For the first time since Terry's announcement I am at peace regarding > Leo and its future. > > *Aha 1*: Leo's legacy is its /existing/ code. No foreseeable > enhancement will change this legacy. > > *Aha 2*: My main task will be to fix significant or annoying bugs. > > *Bugs* > > This page > <https://github.com/leo-editor/leo-editor/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Abug+-label%3Alvl%3Aminor+-label%3Awaiting> > lists all of Leo's significant bugs, minus bugs awaiting action from > others. There are 19 in all. > > This page > <https://github.com/leo-editor/leo-editor/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A5.8.1+-label%3Awaiting+is%3Aopen+> > lists the 12 bugs scheduled for Leo 5.8.1. The most serious bug is > #1021 <https://github.com/leo-editor/leo-editor/issues/1021> re > add-editor. Several of these bugs are duplicates. I expect to fix > them all in the near future. > > *Aha 3*: There is no great rush to release 5.8.1. The "devel" branch > will suffice for most people. > > *Code quality* > > Imo, Leo's code base does not need major revisions, especially after > the latest refactoring. YMMV, but that does not concern me greatly. > > *Aha 4*: Simplifying Leo's code must be weighed against the > probability that the code will ever actually need to be changed. > > For example, the mod_scripting plugin contains difficult code, but it > hasn't changed significantly in years. The conclusion: "improving" > this code has little payoff. > > *The future* > > I am going to de-emphasize enhancements. Some issues are on the > border between enhancement and bug, particularly the viewrendered2 > plugin. It would be best to merge the VR and VR2 plugins, but that is > much harder than you might think. So even this is not a high priority. > > Just for fun, I may play around with transliterating Leo's data mode > (leoNodes.py, and other code) into other languages. Coffeescript and > Lua are natural candidates: coffeescript may be useful for Joe Orr; > Lua is vim's new scripting language. Languages such as rust might also > be interesting. Vitalije has already expressed some interest in this. > > *Summary* > > Leo and its code are good enough as they are. > > Fixing significant or annoying bugs in Leo will always be an important > part of what I do. > > De-emphasizing enhancements frees me from the tyranny of to-do lists > and suggests playful projects. > > Your comments please, Amigos. > > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. -- 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.
