🦁 leojs and leointeg status update 🦁

[Félix]

I know i know ok ok ok I got leojs far enough, I'm now switching to fixing & releasing leointeg 1.0! 😅

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

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... Altough running as a vscode extensions, the 'core' is independant of vscode.

Since it's an emacs script syntax, and strongly typed, it could be used to make a 'core leo engine' in c, rust, etc. 

to try/show off : The 'demo' build so far creates 2 test commanders at startup, (in leoUi constructor) with their respective outlines. 

leojs Demo Features: 

No body pane but the tree browsing is working, expanding/collapsing nodes, context menu shows relevant commands, the document switching works too, but anything else is just commands mapped to message popups. Also, you can turn on the 'leo tree browsing mode / ar-jans suggestion ;) ' on and off in the outline title menu. You can then see that command mapped to message popups are then behaving differently accordingly. 

Feel free to explore and ask about it, I'll try to answer anything that comes my way in relation to that ! :)

So, no more fiddling around with fun side-projects: I'll continue leojs later for sure, but I'll now switch back to fixing the last remaining feature/bug (body pane undos) that prevents the launch of leoInteg 1.0 !

Félix

[Edward K. Ream]

On Tue, Mar 2, 2021 at 11:08 PM Félix <felix...@gmail.com> 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

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

[Offray Vladimir Luna Cárdenas]

Hi,

Thanks for this work and the link to the issue about what inspired LeoJS at https://github.com/leo-editor/leo-editor/issues/1025 . Even as a long time Leo user (not so much now) I find the succinct definition of the defining features pretty enlightening. In fact I would like to have links from the unique and essential features document to some documentation or example using them, as I think they provide a wide overview particularly for those with experience in other outliners and code/text editors.

Coming back to LeoJS, I suggest a more that 4 lines longer readme, to make the "Enjoy!" invitation reachable for wider people.

Cheers,

Offray

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f391f757-fc33-497b-bcbb-03881003a267n%40googlegroups.com.

[Félix]

To Edward

> What do you mean "it's an emacs script syntax"?

I made a typo, i meant ECMAS script syntax, which is something very similar to c, actionscript, javascript, on the syntactic level. ( semicolons at end of expressions , parenthesis use, available code structural and control flow keywords, etc.)

To Offray

> Coming back to LeoJS, I suggest a more that 4 lines longer readme, to make the "Enjoy!" invitation reachable for wider people.

Sh*t - Yeah, you made me realize I had completely forgotten about filling up the readme file with a description and basic install, build & running info! Made the mistake of thinking only people familiar with vscode extensions and leoInteg would read all this I guess..   itsallgood, I'm on it :)

Thanks for your comments Offray ! 

Félix