date:20240102

Re: LeoJS - How To Print javascript Output?

2024-01-02 Thread jkn


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 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 indeed the equivalent of python's *print 
>> *function, 
>> which prints in the terminal instead of Leo's Log Window), will itself 
>> indeed print in the developer's-tools-terminal. (not recommended)
>>
>> What I recommend in contrast, is the *g.es  *function (and 
>> other 'g' methods like es_print, etc.) which does print in the Log Window. 
>>
>> See (and study) this example script that gives a few pointers on how to 
>> do various useful stuff :
>>
>> @language javascript
>> const vscode = g.app.vscode;
>> g.es("hahahaha");
>> // 'await' for doCommandByName required only if other code in script is 
>> 'awaited'.
>> await c.doCommandByName('insert-headline-time');
>>
>> const userInput = await vscode.window.showInputBox({
>> placeHolder: 'Enter something', // Placeholder text in the input box
>> prompt: 'Please enter some text:', // Prompt message above the input 
>> box
>> });
>> if (userInput === undefined) {
>> g.es('User canceled the input.');
>> } else {
>> g.es('User input:', userInput);
>> }
>> try {
>> const apiUrl = 'https://jsonplaceholder.typicode.com/users';
>> const response = await fetch(apiUrl);
>> g.es("about to call");
>> if (!response.ok) {
>> throw new Error('Network response was not ok');
>> }
>> const data = await response.json();
>> g.es("got it!!", JSON.stringify(data));
>> } catch (error) {
>> g.es("oh no!");
>> console.error('Fetch error:', error);
>> }
>>
>>
>> It will insert the current time on the selected node, then pop an input 
>> box and print it back out in the log window, along with the result of an 
>> HTTP fetch call to some test API. Here is a screenshot of the result of 
>> running this script online in vscode on the web :
>> [image: screen_script_web.png]
>>
>> Hope this helps! 
>>
>> Félix
>>
>> On Tuesday, January 2, 2024 at 12:43:46 PM UTC-5 tbp1...@gmail.com wrote:
>>
>>> 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 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/d7fd99f7-6e40-495f-9d1f-ba3c06673f6dn%40googlegroups.com.

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

2024-01-02 Thread jkn


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 useful error report.

Regards, Jon N

On Wednesday, January 3, 2024 at 1:37:39 AM UTC Félix wrote:

> 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 
> gets read and written as-is to not corrupt any Leo files with custom 
> attributes outside of regular 'UA's
>
> I'll open an issue as soon as I can try it out.
>
> Thanks again!
>
> Félix
> On Tuesday, January 2, 2024 at 12:11:05 PM UTC-5 jkn wrote:
>
>> 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 occasional use of node icons.
>>
>> AFAICT a node icon just gets turned into an "icons=long_hex_string" in 
>> the node entry:
>>
>> > icons="5d71007d71012858040074797065710258040066696c65710368035834002f686f6d652f6a6b6e2f6c656f2d656469746f722f686561646c696e652d6974656d732f746869737765656b5f67726e2e706e67710458070072656c5061746871055834002f686f6d652f6a6b6e2f6c656f2d656469746f722f686561646c696e652d6974656d732f746869737765656b5f67726e2e706e67710658050077686572657107580e006265666f7265486561646c696e657108580700796f73657471094b00580700786f736574710a4b0258040078706164710b4b015802006f6e710c580500564e6f6465710d75612e">
>>
>> ### (body of node) ###
>> 
>>
>> I'm unclear of the encoding, but FWIW I seemed to have recovered things, 
>> and allowed Leo Classic to open the files, by deleting the 'icons=' part in 
>> my file - luckily there were only a few of them.
>>
>> Perhaps foolishly I did update my copy of Leo classic in the middle of 
>> all of my playing.
>> But I'm wondering if LeoJS somehow mangled something here, or if recent 
>> changes to Leo might have caused this.
>>
>> I can try to recreate the problem and get a fuller error message if that 
>> would be useful. I thought I'd put this out in case this jogged any 
>> memories.
>>
>> Thanks, Jon n
>>
>>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/ae9f2353-c81e-4672-9780-89875a4b30a1n%40googlegroups.com.

Re: LeoJS - How To Print javascript Output?

2024-01-02 Thread Thomas Passin

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 indeed the equivalent of python's *print 
> *function, 
> which prints in the terminal instead of Leo's Log Window), will itself 
> indeed print in the developer's-tools-terminal. (not recommended)
>
> What I recommend in contrast, is the *g.es  *function (and 
> other 'g' methods like es_print, etc.) which does print in the Log Window. 
>
> See (and study) this example script that gives a few pointers on how to do 
> various useful stuff :
>
> @language javascript
> const vscode = g.app.vscode;
> g.es("hahahaha");
> // 'await' for doCommandByName required only if other code in script is 
> 'awaited'.
> await c.doCommandByName('insert-headline-time');
>
> const userInput = await vscode.window.showInputBox({
> placeHolder: 'Enter something', // Placeholder text in the input box
> prompt: 'Please enter some text:', // Prompt message above the input 
> box
> });
> if (userInput === undefined) {
> g.es('User canceled the input.');
> } else {
> g.es('User input:', userInput);
> }
> try {
> const apiUrl = 'https://jsonplaceholder.typicode.com/users';
> const response = await fetch(apiUrl);
> g.es("about to call");
> if (!response.ok) {
> throw new Error('Network response was not ok');
> }
> const data = await response.json();
> g.es("got it!!", JSON.stringify(data));
> } catch (error) {
> g.es("oh no!");
> console.error('Fetch error:', error);
> }
>
>
> It will insert the current time on the selected node, then pop an input 
> box and print it back out in the log window, along with the result of an 
> HTTP fetch call to some test API. Here is a screenshot of the result of 
> running this script online in vscode on the web :
> [image: screen_script_web.png]
>
> Hope this helps! 
>
> Félix
>
> On Tuesday, January 2, 2024 at 12:43:46 PM UTC-5 tbp1...@gmail.com wrote:
>
>> 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 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/aad78de7-378b-45eb-9e88-4422c436ebban%40googlegroups.com.

Re: LeoJS - How To Print javascript Output?

2024-01-02 Thread Félix

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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/92755d0f-6063-4a97-8c04-fee411d7395dn%40googlegroups.com.

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

2024-01-02 Thread Félix

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 
gets read and written as-is to not corrupt any Leo files with custom 
attributes outside of regular 'UA's

I'll open an issue as soon as I can try it out.

Thanks again!

Félix
On Tuesday, January 2, 2024 at 12:11:05 PM UTC-5 jkn wrote:

> 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 
> occasional use of node icons.
>
> AFAICT a node icon just gets turned into an "icons=long_hex_string" in the 
> node entry:
>
>  icons="5d71007d71012858040074797065710258040066696c65710368035834002f686f6d652f6a6b6e2f6c656f2d656469746f722f686561646c696e652d6974656d732f746869737765656b5f67726e2e706e67710458070072656c5061746871055834002f686f6d652f6a6b6e2f6c656f2d656469746f722f686561646c696e652d6974656d732f746869737765656b5f67726e2e706e67710658050077686572657107580e006265666f7265486561646c696e657108580700796f73657471094b00580700786f736574710a4b0258040078706164710b4b015802006f6e710c580500564e6f6465710d75612e">
>
> ### (body of node) ###
> 
>
> I'm unclear of the encoding, but FWIW I seemed to have recovered things, 
> and allowed Leo Classic to open the files, by deleting the 'icons=' part in 
> my file - luckily there were only a few of them.
>
> Perhaps foolishly I did update my copy of Leo classic in the middle of all 
> of my playing.
> But I'm wondering if LeoJS somehow mangled something here, or if recent 
> changes to Leo might have caused this.
>
> I can try to recreate the problem and get a fuller error message if that 
> would be useful. I thought I'd put this out in case this jogged any 
> memories.
>
> Thanks, Jon n
>
>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/0f24e865-5851-42dc-ade9-fabf64e58c30n%40googlegroups.com.

Re: LeoJS - How To Print javascript Output?

2024-01-02 Thread Mike Hodson

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 intuitive? g.writelog ; g.print g.log
something; but 'es' ? What does 'es' mean?

Mike



On Tue, Jan 2, 2024, 18:16 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 indeed the equivalent of python's *print 
> *function,
> which prints in the terminal instead of Leo's Log Window), will itself
> indeed print in the developer's-tools-terminal. (not recommended)
>
> What I recommend in contrast, is the *g.es  *function (and
> other 'g' methods like es_print, etc.) which does print in the Log Window.
>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAN%2B%2B4hFu3zMMLS4Q_D-zdce%3Dyxmz9tegT5CP-%3D3SpHmYc%2BTK_A%40mail.gmail.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread jkn


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 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 OS/distribution specific. I am running VSCodium under 
> Kubuntu Linux. When I try to open a file, the open dialog appear *in the 
> panel/toolbar*, ie. not as a sized window. I have to explicitly open the 
> dialog by clicking in the toolbar. as I say, I think this is an artefact of 
> my distribution, but if anyone knows how to fix it I'd be grateful
>
>
> I just installed it on XUbuntu and didn't see this issue. 
>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/8ea04b73-ea15-40a6-afec-b097abdcc99en%40googlegroups.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread Thomas Passin

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 environment as I run 'Leo Classic' in:

1) This is probably OS/distribution specific. I am running VSCodium under 
Kubuntu Linux. When I try to open a file, the open dialog appear *in the 
panel/toolbar*, ie. not as a sized window. I have to explicitly open the 
dialog by clicking in the toolbar. as I say, I think this is an artefact of 
my distribution, but if anyone knows how to fix it I'd be grateful


I just installed it on XUbuntu and didn't see this issue. 

-- 
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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/d059e6ac-36d0-4e3f-8914-0f3a29f58041n%40googlegroups.com.

LeoJS - How To Print javascript Output?

2024-01-02 Thread Thomas Passin

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 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/26bae114-6eff-4dc6-babe-7517a82bc4fcn%40googlegroups.com.

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

2024-01-02 Thread jkn

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 
occasional use of node icons.

AFAICT a node icon just gets turned into an "icons=long_hex_string" in the 
node entry:



### (body of node) ###


I'm unclear of the encoding, but FWIW I seemed to have recovered things, 
and allowed Leo Classic to open the files, by deleting the 'icons=' part in 
my file - luckily there were only a few of them.

Perhaps foolishly I did update my copy of Leo classic in the middle of all 
of my playing.
But I'm wondering if LeoJS somehow mangled something here, or if recent 
changes to Leo might have caused this.

I can try to recreate the problem and get a fuller error message if that 
would be useful. I thought I'd put this out in case this jogged any 
memories.

Thanks, Jon n

-- 
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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/c454772a-4cf9-49b5-860c-3084719291fbn%40googlegroups.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread Thomas Passin

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.

On Tuesday, January 2, 2024 at 11:07:46 AM UTC-5 jkn wrote:

> 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 added a workaround rule to 
> the Window configuration.
>
> In the course of all of this I have updated 'Leo classic' and seem to have 
> hit a different issue ... I will raise as a separate thread.
>
> Sorry for the noise, J^n
>
>
> On Tuesday, January 2, 2024 at 3:36:44 PM UTC 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 environment as I run 'Leo Classic' in:
>>
>> 1) This is probably OS/distribution specific. I am running VSCodium under 
>> Kubuntu Linux. When I try to open a file, the open dialog appear *in the 
>> panel/toolbar*, ie. not as a sized window. I have to explicitly open the 
>> dialog by clicking in the toolbar. as I say, I think this is an artefact of 
>> my distribution, but if anyone knows how to fix it I'd be grateful
>>
>> 2) I am getting severe problems, having exited Codium and trying to start 
>> 'Leo Classic', with 'File already opened in another copy of Leo' errors. It 
>> took me a while to find the button to close a file in LeoJS; but even after 
>> going through the list of files and doing this one by one I am still 
>> getting this on multiple files. I recall there used to be some sort of 
>> cache file you could delete in these circumstances, but I can recall the 
>> details. anyone, please?
>>
>> Thanks, J^n
>>
>> On Tuesday, January 2, 2024 at 2:36:02 PM UTC tbp1...@gmail.com wrote:
>>
>>> 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 9:24:18 AM UTC-5 jkn wrote:
>>>
 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 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: _56d93bdf-e7f0-4625-85a2-cbf3cfc87fee.jpg]
>>
>> What's New in 0.2.8:
>>
>>- *Help Commands*: 'helpCommands.py' was converted to typescript, 
>>enabling help commands.
>>- *UNL Support*: Works in log pane, body panes, and all editor 
>>windows.
>>- *Goto-Script Fix*: Now works seamlessly with @button items.
>>- *Markdown*: The @auto markdown importer and writer now ensures 
>>flawless read-write integrity.
>>- *Undo/Redo for UAs*: Enhanced command support for 'Clear UAs' 
>>and 'Set UA'.
>>- *Clone Related Commands*: Fixes to 'show clone ancestors' and 
>>'show clone parents' commands.
>>- *Workspace-Specific Sessions*: Session management is now more 
>>personalized with workspace-specific settings.
>>- *Stable Node Selection*: LeoJS maintains focus on the selected 
>>node when refreshing external files.
>>- *gnx-kind Setting*: Choose between uuid, ksuid, or traditional 
>>GNX.
>>
>>  Continuous Improvements Since Launch:
>>
>>- Refined tooltips, language coloring support, and bug fixes in 
>>various importers.
>>- Enhanced keyboard navigation and pattern support for web 
>>browsers.
>>- Streamlined mobile experience, including 'ConfirmBeforeClose' 
>>improvements.
>>- Resolved issues with goto-next-clone and goto-next-marked 
>>refresh cycles, session management, and body pane labeling.
>>- Introduced user-friendly 'Recent Files' icons and buttons.
>>
>> If you can help to test it and note the bugs you find on the issues 
>> page , that'd be great! Join 
>> me and the

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread jkn

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 added a workaround rule to 
the Window configuration.

In the course of all of this I have updated 'Leo classic' and seem to have 
hit a different issue ... I will raise as a separate thread.

Sorry for the noise, J^n


On Tuesday, January 2, 2024 at 3:36:44 PM UTC 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 environment as I run 'Leo Classic' in:
>
> 1) This is probably OS/distribution specific. I am running VSCodium under 
> Kubuntu Linux. When I try to open a file, the open dialog appear *in the 
> panel/toolbar*, ie. not as a sized window. I have to explicitly open the 
> dialog by clicking in the toolbar. as I say, I think this is an artefact of 
> my distribution, but if anyone knows how to fix it I'd be grateful
>
> 2) I am getting severe problems, having exited Codium and trying to start 
> 'Leo Classic', with 'File already opened in another copy of Leo' errors. It 
> took me a while to find the button to close a file in LeoJS; but even after 
> going through the list of files and doing this one by one I am still 
> getting this on multiple files. I recall there used to be some sort of 
> cache file you could delete in these circumstances, but I can recall the 
> details. anyone, please?
>
> Thanks, J^n
>
> On Tuesday, January 2, 2024 at 2:36:02 PM UTC tbp1...@gmail.com wrote:
>
>> 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 9:24:18 AM UTC-5 jkn wrote:
>>
>>> 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 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: _56d93bdf-e7f0-4625-85a2-cbf3cfc87fee.jpg]
>
> What's New in 0.2.8:
>
>- *Help Commands*: 'helpCommands.py' was converted to typescript, 
>enabling help commands.
>- *UNL Support*: Works in log pane, body panes, and all editor 
>windows.
>- *Goto-Script Fix*: Now works seamlessly with @button items.
>- *Markdown*: The @auto markdown importer and writer now ensures 
>flawless read-write integrity.
>- *Undo/Redo for UAs*: Enhanced command support for 'Clear UAs' 
>and 'Set UA'.
>- *Clone Related Commands*: Fixes to 'show clone ancestors' and 
>'show clone parents' commands.
>- *Workspace-Specific Sessions*: Session management is now more 
>personalized with workspace-specific settings.
>- *Stable Node Selection*: LeoJS maintains focus on the selected 
>node when refreshing external files.
>- *gnx-kind Setting*: Choose between uuid, ksuid, or traditional 
>GNX.
>
>  Continuous Improvements Since Launch:
>
>- Refined tooltips, language coloring support, and bug fixes in 
>various importers.
>- Enhanced keyboard navigation and pattern support for web 
>browsers.
>- Streamlined mobile experience, including 'ConfirmBeforeClose' 
>improvements.
>- Resolved issues with goto-next-clone and goto-next-marked 
>refresh cycles, session management, and body pane labeling.
>- Introduced user-friendly 'Recent Files' icons and buttons.
>
> If you can help to test it and note the bugs you find on the issues 
> page , that'd be great! Join 
> me and the community of Leo enthusiasts in refining LeoJS. Your feedback 
> is 
> invaluable in making LeoJS the best it can be.
>
>  Get Started: LeoJS Beta 0.2.8 
>  (also 
> available on open-vsx.org 
> )
>
> *Many thanks to Edward, Thomas Kevin, and the rest of the Leo 
> community for your contributions and support!!*
>

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread jkn

(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 OS/distribution specific. I am running VSCodium under 
Kubuntu Linux. When I try to open a file, the open dialog appear *in the 
panel/toolbar*, ie. not as a sized window. I have to explicitly open the 
dialog by clicking in the toolbar. as I say, I think this is an artefact of 
my distribution, but if anyone knows how to fix it I'd be grateful

2) I am getting severe problems, having exited Codium and trying to start 
'Leo Classic', with 'File already opened in another copy of Leo' errors. It 
took me a while to find the button to close a file in LeoJS; but even after 
going through the list of files and doing this one by one I am still 
getting this on multiple files. I recall there used to be some sort of 
cache file you could delete in these circumstances, but I can recall the 
details. anyone, please?

Thanks, J^n

On Tuesday, January 2, 2024 at 2:36:02 PM UTC tbp1...@gmail.com wrote:

> 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 9:24:18 AM UTC-5 jkn wrote:
>
>> 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 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: _56d93bdf-e7f0-4625-85a2-cbf3cfc87fee.jpg]

 What's New in 0.2.8:

- *Help Commands*: 'helpCommands.py' was converted to typescript, 
enabling help commands.
- *UNL Support*: Works in log pane, body panes, and all editor 
windows.
- *Goto-Script Fix*: Now works seamlessly with @button items.
- *Markdown*: The @auto markdown importer and writer now ensures 
flawless read-write integrity.
- *Undo/Redo for UAs*: Enhanced command support for 'Clear UAs' and 
'Set UA'.
- *Clone Related Commands*: Fixes to 'show clone ancestors' and 
'show clone parents' commands.
- *Workspace-Specific Sessions*: Session management is now more 
personalized with workspace-specific settings.
- *Stable Node Selection*: LeoJS maintains focus on the selected 
node when refreshing external files.
- *gnx-kind Setting*: Choose between uuid, ksuid, or traditional 
GNX.

  Continuous Improvements Since Launch:

- Refined tooltips, language coloring support, and bug fixes in 
various importers.
- Enhanced keyboard navigation and pattern support for web browsers.
- Streamlined mobile experience, including 'ConfirmBeforeClose' 
improvements.
- Resolved issues with goto-next-clone and goto-next-marked refresh 
cycles, session management, and body pane labeling.
- Introduced user-friendly 'Recent Files' icons and buttons.

 If you can help to test it and note the bugs you find on the issues 
 page , that'd be great! Join 
 me and the community of Leo enthusiasts in refining LeoJS. Your feedback 
 is 
 invaluable in making LeoJS the best it can be.

  Get Started: LeoJS Beta 0.2.8 
  (also 
 available on open-vsx.org 
 )

 *Many thanks to Edward, Thomas Kevin, and the rest of the Leo community 
 for your contributions and support!!*

 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/ce7443f6-8193-4faa-8591-9f56435a7b56n%40googlegroups.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread Thomas Passin

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 9:24:18 AM UTC-5 jkn wrote:

> 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 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: _56d93bdf-e7f0-4625-85a2-cbf3cfc87fee.jpg]
>>>
>>> What's New in 0.2.8:
>>>
>>>- *Help Commands*: 'helpCommands.py' was converted to typescript, 
>>>enabling help commands.
>>>- *UNL Support*: Works in log pane, body panes, and all editor 
>>>windows.
>>>- *Goto-Script Fix*: Now works seamlessly with @button items.
>>>- *Markdown*: The @auto markdown importer and writer now ensures 
>>>flawless read-write integrity.
>>>- *Undo/Redo for UAs*: Enhanced command support for 'Clear UAs' and 
>>>'Set UA'.
>>>- *Clone Related Commands*: Fixes to 'show clone ancestors' and 
>>>'show clone parents' commands.
>>>- *Workspace-Specific Sessions*: Session management is now more 
>>>personalized with workspace-specific settings.
>>>- *Stable Node Selection*: LeoJS maintains focus on the selected 
>>>node when refreshing external files.
>>>- *gnx-kind Setting*: Choose between uuid, ksuid, or traditional GNX.
>>>
>>>  Continuous Improvements Since Launch:
>>>
>>>- Refined tooltips, language coloring support, and bug fixes in 
>>>various importers.
>>>- Enhanced keyboard navigation and pattern support for web browsers.
>>>- Streamlined mobile experience, including 'ConfirmBeforeClose' 
>>>improvements.
>>>- Resolved issues with goto-next-clone and goto-next-marked refresh 
>>>cycles, session management, and body pane labeling.
>>>- Introduced user-friendly 'Recent Files' icons and buttons.
>>>
>>> If you can help to test it and note the bugs you find on the issues page 
>>> , that'd be great! Join me and 
>>> the community of Leo enthusiasts in refining LeoJS. Your feedback is 
>>> invaluable in making LeoJS the best it can be.
>>>
>>>  Get Started: LeoJS Beta 0.2.8 
>>>  (also 
>>> available on open-vsx.org )
>>>
>>> *Many thanks to Edward, Thomas Kevin, and the rest of the Leo community 
>>> for your contributions and support!!*
>>>
>>> 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/b1d778f5-0924-45c6-9270-1e739100e5d1n%40googlegroups.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread jkn

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 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: _56d93bdf-e7f0-4625-85a2-cbf3cfc87fee.jpg]
>>
>> What's New in 0.2.8:
>>
>>- *Help Commands*: 'helpCommands.py' was converted to typescript, 
>>enabling help commands.
>>- *UNL Support*: Works in log pane, body panes, and all editor 
>>windows.
>>- *Goto-Script Fix*: Now works seamlessly with @button items.
>>- *Markdown*: The @auto markdown importer and writer now ensures 
>>flawless read-write integrity.
>>- *Undo/Redo for UAs*: Enhanced command support for 'Clear UAs' and 
>>'Set UA'.
>>- *Clone Related Commands*: Fixes to 'show clone ancestors' and 'show 
>>clone parents' commands.
>>- *Workspace-Specific Sessions*: Session management is now more 
>>personalized with workspace-specific settings.
>>- *Stable Node Selection*: LeoJS maintains focus on the selected node 
>>when refreshing external files.
>>- *gnx-kind Setting*: Choose between uuid, ksuid, or traditional GNX.
>>
>>  Continuous Improvements Since Launch:
>>
>>- Refined tooltips, language coloring support, and bug fixes in 
>>various importers.
>>- Enhanced keyboard navigation and pattern support for web browsers.
>>- Streamlined mobile experience, including 'ConfirmBeforeClose' 
>>improvements.
>>- Resolved issues with goto-next-clone and goto-next-marked refresh 
>>cycles, session management, and body pane labeling.
>>- Introduced user-friendly 'Recent Files' icons and buttons.
>>
>> If you can help to test it and note the bugs you find on the issues page 
>> , that'd be great! Join me and 
>> the community of Leo enthusiasts in refining LeoJS. Your feedback is 
>> invaluable in making LeoJS the best it can be.
>>
>>  Get Started: LeoJS Beta 0.2.8 
>>  (also 
>> available on open-vsx.org )
>>
>> *Many thanks to Edward, Thomas Kevin, and the rest of the Leo community 
>> for your contributions and support!!*
>>
>> 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/b2a3bb79-8737-4961-a662-43535f5eeb2fn%40googlegroups.com.

Re: Installing nim was easy!

2024-01-02 Thread Thomas Passin

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  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 
> LilyPond.
>
> As usual, I did *not* alter the Windows path. Instead, I created *gcc.cmd*, 
> which *is* on the path.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b543f451-f44d-4959-9ad3-f3a755230197n%40googlegroups.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread Edward K. Ream

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 this two days ago in a comment to PR #3737 

:

QQQ
Historical Note: This is the very last feature/bug completing the 
rewrite/code review of Leo while making LeoJS. (A few weeks back I thought 
we were done, but I had yet to implement UNLS! haha! Now we're really at 
the last part - for real this time!  )
QQQ

This Beta is a milestone in Leo's history. Congratulations again.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/8910e7a1-7287-4f44-bca0-ad8363e561e2n%40googlegroups.com.

Re: Installing nim was easy!

2024-01-02 Thread Edward K. Ream

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 
LilyPond.

As usual, I did *not* alter the Windows path. Instead, I created *gcc.cmd*, 
which *is* on the path.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/bda83b22-2bbe-4cb2-b557-6ac132efcd86n%40googlegroups.com.

Re: ✨LeoJS beta 0.2.8 Released!

2024-01-02 Thread jkn

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: _56d93bdf-e7f0-4625-85a2-cbf3cfc87fee.jpg]
>
> What's New in 0.2.8:
>
>- *Help Commands*: 'helpCommands.py' was converted to typescript, 
>enabling help commands.
>- *UNL Support*: Works in log pane, body panes, and all editor windows.
>- *Goto-Script Fix*: Now works seamlessly with @button items.
>- *Markdown*: The @auto markdown importer and writer now ensures 
>flawless read-write integrity.
>- *Undo/Redo for UAs*: Enhanced command support for 'Clear UAs' and 
>'Set UA'.
>- *Clone Related Commands*: Fixes to 'show clone ancestors' and 'show 
>clone parents' commands.
>- *Workspace-Specific Sessions*: Session management is now more 
>personalized with workspace-specific settings.
>- *Stable Node Selection*: LeoJS maintains focus on the selected node 
>when refreshing external files.
>- *gnx-kind Setting*: Choose between uuid, ksuid, or traditional GNX.
>
>  Continuous Improvements Since Launch:
>
>- Refined tooltips, language coloring support, and bug fixes in 
>various importers.
>- Enhanced keyboard navigation and pattern support for web browsers.
>- Streamlined mobile experience, including 'ConfirmBeforeClose' 
>improvements.
>- Resolved issues with goto-next-clone and goto-next-marked refresh 
>cycles, session management, and body pane labeling.
>- Introduced user-friendly 'Recent Files' icons and buttons.
>
> If you can help to test it and note the bugs you find on the issues page 
> , that'd be great! Join me and 
> the community of Leo enthusiasts in refining LeoJS. Your feedback is 
> invaluable in making LeoJS the best it can be.
>
>  Get Started: LeoJS Beta 0.2.8 
>  (also 
> available on open-vsx.org )
>
> *Many thanks to Edward, Thomas Kevin, and the rest of the Leo community 
> for your contributions and support!!*
>
> 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 on the web visit 
https://groups.google.com/d/msgid/leo-editor/b2ac665a-d03f-4347-b2c7-41fa1e7f03dcn%40googlegroups.com.

Re: LeoJS - How To Print javascript Output?

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

Re: LeoJS - How To Print javascript Output?

Re: LeoJS - How To Print javascript Output?

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

Re: LeoJS - How To Print javascript Output?

Re: ✨LeoJS beta 0.2.8 Released!

Re: ✨LeoJS beta 0.2.8 Released!

LeoJS - How To Print javascript Output?

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

Re: ✨LeoJS beta 0.2.8 Released!

Re: ✨LeoJS beta 0.2.8 Released!

Re: ✨LeoJS beta 0.2.8 Released!

Re: ✨LeoJS beta 0.2.8 Released!

Re: ✨LeoJS beta 0.2.8 Released!

Re: Installing nim was easy!

Re: ✨LeoJS beta 0.2.8 Released!

Re: Installing nim was easy!

Re: ✨LeoJS beta 0.2.8 Released!

19 matches

Site Navigation

Mail list logo

Footer information