2009 was an excellent year for Leo. Here are a few highlights: - The one-node world. Gone is the horrid distinction between tnodes and vnodes. For the first time ever, Leo's fundamental data model is intuitive. Moreover, it's obviously the best that can be imagined: nothing remains to be simplified.
- Caching external files greatly speeds up loading .leo files. - Leo now works reliably with Python 3000. - This year the Qt gui became stable, and I suspect became the default for most people. The Tk gui will die unless it gets ported to Python 3000. - @edit nodes - @auto-rst nodes debuted, and early this year became solid. - The new executable Windows installer uses the bzr manifest. - Better documentation, especially Leo's tutorial. Looking ahead to 2010, I foresee progress in the following areas: - The reduction of Leo's bug list to zero, except for wish-list items. - Better support for vim bindings. - A breakthrough (details unclear) on autocompletion. - The conversion of more plugins to work with the Qt gui. - And maybe even some way to make sentinels appear to disappear. As the result of all this actual and anticipated progress, Leo can begin to reach out to other projects. Just for example, Mathematica would benefit greatly from Leo's outlines and DOM. Your comments, please. Anything else you would put on these lists? Edward -- 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.
