Re: LeoJS - How To Print javascript Output?

Yes, "es" == "emit string" is one of the arcane bits of Leo-lore, IMO. I think the docs should mention this, IIRC they do not and it must have caused some puzzlement over the years... On Wednesday, January 3, 2024 at 2:02:15 AM UTC tbp1...@gmail.com wrote: > Ha! Should have tried that right

Re: Strangeness with tratment of node Icons - LeoJS and/or 'Classic'?

Hi Felix - yes, I will try to make a small file that demonstrates the issue. I think the long hex string must be a path to a file (encoded), but I am not sure of the mechanism. IIRC LeoJS indicated this as some sort of note attribute (JSON?), but I need to re-run properly so as to give a more

Re: LeoJS - How To Print javascript Output?

Ha! Should have tried that right off!. Thanks. On Tuesday, January 2, 2024 at 8:16:51 PM UTC-5 Félix wrote: > Hi Thomas! :) > > I gather that by an 'Output window' you mean the LeoJS Log Window? (The > equivalent of Leo's Log Window) > [image: log_pane.png] > > Using *console.log (*which is

Re: LeoJS - How To Print javascript Output?

Lo and behold, it means *emit string *  Félix -- 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

Re: Strangeness with tratment of node Icons - LeoJS and/or 'Classic'?

jkn Can you give more info about those node icons? (custom attributes) Is the long hex string image file data, of just a path to a file on disk? and share a sample .leo file that has only one or two nodes with icons ? (the smaller the better) I'll use it to make experiments and ensure that it

Re: LeoJS - How To Print javascript Output?

I'll admit I have not scripted Leo at all, and have only used it sparingly as an editor/organizer because of oddities in autosave.. But why in all the world is a function called 'es' [I presume g means global scope] something that prints to the log window? Why is it not named something

Re: ✨LeoJS beta 0.2.8 Released!

Yes, this seems to be a Kubuntu/Codium interaction issue. I 'fixed' it with a window management workaround. On Tuesday, January 2, 2024 at 9:02:25 PM UTC tbp1...@gmail.com wrote: > On Tuesday, January 2, 2024 at 10:36:44 AM UTC-5 jkn wrote: > > (I have also probably been getting confused

Re: ✨LeoJS beta 0.2.8 Released!

On Tuesday, January 2, 2024 at 10:36:44 AM UTC-5 jkn wrote: (I have also probably been getting confused between LeoInteg and LeoJS: the page Felix links to has 'how to install LeoInteg' at the top...) I have two issues on first attempts to use LeoJS, or at least to use it in the same

LeoJS - How To Print javascript Output?

This script apparently runs without error but nothing shows in the Output window: @language javascript console.log('this is another test'); Using print() doesn't work, of course, because there isn't a print() function. How can we get a visible output? -- You received this message because

Strangeness with tratment of node Icons - LeoJS and/or 'Classic'?

Has anything changed in the treatment of node Icons recently, please? In the course of trying out LeoJS recently, and getting in a few knots re. 'file already open in another copy of Leo', I also hit an error where Leo 'classic' was failing to fully read a file. This seemed to be related to my

Re: ✨LeoJS beta 0.2.8 Released!

I just installed VSCodium and leoJS on Linux Mint in a Virtual Machine. I followed the instructions here to install VSCodium. It all worked like a charm and I opened the Workbook without noticing anything unusual so far.

Re: ✨LeoJS beta 0.2.8 Released!

update: 1) I have got past my 'files open in another instance of Leo' problem. I did remember that the cache is in ~/.leo/db etc, although I ended up not doing it this way 2) I also seem to have sorted out my dialog opening issue - it does indeed seem to be a VSCodium/Kubuntu problem. I have

Re: ✨LeoJS beta 0.2.8 Released!

(I have also probably been getting confused between LeoInteg and LeoJS: the page Felix links to has 'how to install LeoInteg' at the top...) I have two issues on first attempts to use LeoJS, or at least to use it in the same environment as I run 'Leo Classic' in: 1) This is probably

Re: ✨LeoJS beta 0.2.8 Released!

That would probably be hard for a developer to keep up with, I would think. I remember the first time I went to install leoJS I got a similar message, but VSC/odium upgraded in a flash so that I hardly knew what had happened. So it was a non-issue for me. On Tuesday, January 2, 2024 at

Re: ✨LeoJS beta 0.2.8 Released!

A small point - it would be nice if the release notes mentioned what version of VSCode/VSCodium was needed. I got a message that my version was too old. (I am running 1.77.1 of VSCodium, will upgrade shortly) Thanks, jon N On Tuesday, January 2, 2024 at 9:43:20 AM UTC jkn wrote: > I like the

Re: Installing nim was easy!

So did I, but at one point my distro called "gcc.exe", so I had to add it to the path. On Tuesday, January 2, 2024 at 5:35:25 AM UTC-5 Edward K. Ream wrote: > On Monday, January 1, 2024 at 11:05:00 AM UTC-6 Thomas wrote: > > How did you install gcc? Using minGW? > > > where gcc reports

Re: ✨LeoJS beta 0.2.8 Released!

On Monday, January 1, 2024 at 9:38:21 PM UTC-6 Félix wrote: Introducing LeoJS Beta 0.2.8 Congratulations. The New Year is better with LeoJS :-) This new version is the result of continuous, careful, diligent effort since the last release. Leo's community is blessed by your work. You said

Re: Installing nim was easy!

On Monday, January 1, 2024 at 11:05:00 AM UTC-6 Thomas wrote: How did you install gcc? Using minGW? where gcc reports C:\msys64\ucrt64\bin\gcc.exe, so the answer was probably msys2 . Iirc, I installed this package for use by a music engraving package, maybe

Re: ✨LeoJS beta 0.2.8 Released!

I like the graphic Felix, well done! ;-) Jon N On Tuesday, January 2, 2024 at 3:38:21 AM UTC Félix wrote: > Introducing LeoJS Beta 0.2.8 > LeoJS Beta 0.2.8 is here, bringing a substantial update filled with > enhancements and critical fixes. > [image: