On Wed, Dec 16, 2020 at 1:17 PM vitalije <[email protected]> wrote:
Here are some ideas which you are free to ignore if you find them > uninteresting or useless. > Thanks for checking in, Vitalije. I'm glad you are well and busy :-) The goals of Leo in rust makes a lot of sense in the long term. To second Félix's comments to your post, for the leojs project we have no choice but to transpile Leo's core to JS. Happily, Transcrypt <http://www.transcrypt.org/docs/html/index.html>seems just about perfect. It transliterates Leo's python sources to JS without much fuss. The ekr-imports branch contains just a few tweaks: - Transcrypt doesn't support Python's copy module. I added transcrypt pragmas to disable the python code. Other pragmas could be used to insert corresponding JS code. - Transcrypt doesn't support Leo's legacy imports. It is straightforward (and a welcome simplification) to change, for example, import leo.core.leoGlobals as g import leo.commands.leoEditCommands as leoEditCommands to: from leo.core import leoGlobals as g from leo.commands import leoEditCommands *Summary* Leo in rust is worth exploring. Tools such as vs-code might eventually use rust for added speed. When that happens, it would likely be straightforward to port leoInteg and leojs to rust :-) 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/CAMF8tS3Z0btXztmMOy2DXAdOeBjHsau8sWNLfPdm2oFDaUJ0PA%40mail.gmail.com.
