On Sat, May 8, 2010 at 6:07 PM, Edward K. Ream <[email protected]> wrote:
> keep Leo up to date Leo will eventually die. As I have said many times > before, the only way to have Leo live on would be to build the essence > of Leo into one or more mainstream programming environments. Plugins to existing frameworks die much faster than individual programs. All it takes is a major api rehaul and you are out, unless you can muster the time and energy to port your stuff over. As an independent application Leo is much more resilient as the maintenance is about features and bugfixing, which can be done "as needed". One problem with Leo's continued life after you retire is the complexity of the code. The basic "essence" of Leo could be crystallized in much less code than what is around currently (e.g. by relying on text editor classes to do text editing, removing the ui plugin compatibility layers etc. etc.). Eventually we'll want code more people can understand inside-out so that you could consider retiring with good conscience (knowing that Leo will continue to evolve). -- Ville M. Vainio http://tinyurl.com/vainio -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
