At 5 am this morning, I declared the last Leo issue to be complete. I do not foresee significant changes to Leo in the future. See below.
Today is an intensely happy/sad moment for me. Leo has been my life for well over 30 years. I have no idea what I shall do next. I have deliberately put off those considerations until now. *Why stability matters* Imo, Leo (the python app) is no longer the leading edge of the Leonine world. That honor belongs to leoInteg <https://github.com/boltex/leointeg>, a plugin for vs-code, written by Félix Malboeuf. leoInteg communicates with Leo using Leo's server, leoserver.py. *Leo's stability doesn't matter much for leoInteg*. Leo's server is flexible and could accommodate significant changes to Leo. However, Félix is now working on leoJS <https://github.com/boltex/leojs>, an all-Typescript plugin for vs-code. leoJS promises significant performance improvements over leoInteg. There is no need to wait for results from leoserver.py! *Leo's stability matters very much for leoJS*. Félix is transliterating (literally line by line) Leo's python code into Typescript. It's a big job, but he is already well along. Changing Leo's code base would make additional work for Félix. *Summary* Today is a milestone for Leo and for me. It's an intensely happy/sad moment. Imo, leoInteg and leoJS are now the leading edges of the Leonine world. These two vs-code plugins offer all the advantages of vs-code plus all of Leo's unique features. I want to keep Leo's code stable so that Félix will not have to revise his transliterated Typescript code. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c5c03d3f-97bb-4322-aed0-a05388e7dff0n%40googlegroups.com.
