I think it's a good idea to focus on small things. Leo backend is already powerful enough for most users, probably more powerful than what average user will ever need. What Leo needs to "make it " big time is polish on ui level... well working autocompleter etc. Perhaps a more modern color theme.
"Edward K. Ream" <[email protected]> wrote: >A few weeks ago Kent dropped in on me, and we discussed what's next >for Leo. > >At that time I indicated that I thought Leo was essentially complete. >Despite my recent posting about re-visioning Leo, I think what I told >Kent is correct, namely that it would be good to declare a one-year >moratorium on "grand" improvements to Leo. In my mind, this is >analogous to GvR's one-year moratorium on major additions to Python. > >Rather than pretending that there is something wrong with Leo that >needs to be fixed, imo it would be more appropriate to shift focus to >finding new and innovative ways to use what we already have. > >Of course, this does not preclude incremental improvements and bug >fixes. It doesn't necessarily even preclude experimenting with @view >nodes. But I think it's time to abandon new schemes for doing without >sentinels, improving @auto with "just a few more" sentinels, etc. For >me, these kinds of thoughts quickly become an annoying dead end. > >Your comments please. > >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. > -- 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.
