On Tue, Mar 2, 2021 at 11:08 PM Félix <[email protected]> wrote:
> I'm now switching to fixing & releasing leointeg 1.0! 😅 Well done, you. > What has been up with leojs so far in the last 3 months or so? well, > leojs doesn't 'fake' its outline and leo-documents anymore: I've translated > the core of Leo's Node Classes and the main Commander's API. So the 'test' > outlines and documents are 'live'. *Check it out at > : https://github.com/boltex/leojs <https://github.com/boltex/leojs>* > Done. *We're talking typescript here, not javascript, *so everything is > statically, strongly typed. Respecting Leo's internal methods idioms and > semantics, not simulating python on top of javascript with an automated > transliterator and then running leo on top of it... Although running as a > vscode extensions, the 'core' is independant of vscode. > Very interesting. > Since it's an emacs script syntax, and strongly typed, it could be used to > make a 'core leo engine' in c, rust, etc. > What do you mean "it's an emacs script syntax"? Many thanks for all your work. I'm working to make sure that Leo 4.6 is ready when leoInteg 1.0 is ready :-) 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/CAMF8tS2-RB9PwX9V%2Bg-HfSD2MiPCxtcEkVmLB%3D8nVyHOrCVVWw%40mail.gmail.com.
