In the past, many or most of the development on Leo has centered on making 
Leo more usable, such as having more features for editing, or viewing what 
you have edited, or operating with scripts on content in Leo.  Leo is so 
powerful that it should be be a very suitable platform for other kinds of 
applications, ones that aren't centered on Leo itself.

IMHO Leo's potential for host a range of useful applications is nearly 
untapped.  When someone with a good idea tries to develop it in Leo, there 
may turn out to be a need for some new capability of feature.  But without 
tasks like that it's hard to know what would be needed.  Maybe some means 
for debugging programs in other languages would be helpful, making Leo more 
like a conventional IDE.  But that would take a lot of work absent a clear 
need.

Some readers  might remember me writing about the bookmark manager I wrote 
years ago to run inside a browser.  It's really nice, but the internals are 
complicated javascript code, making it hard to modify, and saving and 
restoring data is really clumsy and annoying. It would be very hard to get 
it working for someone else.  Leo turns out to have the abilities of the 
usual bookmark managers that are built into browsers except it's way 
better.  I have a couple of scripts: one lets you insert a bookmark node 
using a URL in the clipboard.  The other takes the standard HTML bookmark 
file that most browsers can generate and produces an entire Leo tree with 
organizer and URL nodes.

I'm already using this, and I like it a lot.  I'm prototyping some of the 
other features of my old inbrowser manager.  When that's all working  I'll 
have something very useful to me, and one much easier to modify and extend 
than my old one.  All in Leo.

So that's one application, one feature that isn't focused on making Leo 
easier to use.  The recent photo slideshow script is one of these.  There 
must be an unlimited number of others, if only people can think of them.

On Friday, February 18, 2022 at 11:41:36 AM UTC-5 Edward K. Ream wrote:

> Leo 6.6 may be the last substantial release in Leo's history. At present, 
> the 6.6 to-do list 
> <https://github.com/leo-editor/leo-editor/issues?q=is%3Aissue+is%3Aopen+milestone%3A6.6>
>  
> contains five items. There are no items at present on the 6.7 to-do list 
> <https://github.com/leo-editor/leo-editor/issues?q=is%3Aissue+is%3Aopen+milestone%3A6.7>.
>  
> Many open items remain 
> <https://github.com/leo-editor/leo-editor/issues?q=is%3Aissue+is%3Aopen+no%3Amilestone+-label%3Ainfo+-label%3Adelegated+-label%3ALeoU+-label%3Acan%27tfix>,
>  
> but I have little desire to do any of them.  Expect 6.6 final in a month or 
> so.
>
> The leojs <https://github.com/boltex/leojs> project now seems like the 
> future of Leo. Indeed, it melds Leo with vs code, an unbeatable combination 
> imo.
>
> I have no clear idea about what I'll do after Leo 6.6. I've been thinking 
> about that question quite a bit lately :-) I have no desire to retire, but 
> I have less desire for make-work.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/93426af0-05b3-4730-bf8f-9d1eae47ad91n%40googlegroups.com.

Reply via email to