🚀 LeoJS Beta 0.2.13 Released

[Félix]

Introducing LeoJS Beta 0.2.13 🚀

I'm thrilled to announce the arrival of LeoJS Beta 0.2.13! This release is all about enhancing your experience and smoothing out the edges for a sleeker, more intuitive interaction.

What's new? 🎥 Dive into "Intro to Leo" and the "LeoJS Features Demo" videos now included in the readme — perfect for both newcomers and veteran Leonistas looking to deepen their understanding of what LeoJS can do.

🛸The Future is Here!

• 🎨Enhanced Visuals: I've fixed the disabled/enabled states of command icons and upgraded icon aesthetics by switching from SVG to a webfont (woff2), ensuring a cleaner and more consistent look across different platforms.
• 🤯Multiple Body Panes: The revamped 'Open Aside' command now launches detached body panes, offering a dedicated space for text editing linked to a fixed gnx. (Issue #120 originally proposed by Jabobian)
• 🔧New Globals for Leo Scripts: The 'vscode' API instance along with other global libs of node.js like 'Buffer', 'crypto', 'child_process', etc... are now available in the global scope along with c, g and p when running scripts.

Available via automatic update or on the VSCode Marketplace, and for VSCodium, on the Open VSX Registry Marketplace!

I highly value your feedback and contributions to further refine LeoJS. If you have any comments, encounter any issues, or have suggestions for future updates, please don't hesitate to share them on the GitHub Issues page.

I'll now also port those enhancements to LeoInteg in the next few days, and continue working towards a version 1.0 release of LeoJS. (Hopefully this spring!)

Happy coding! 🦁

Félix

[Edward K. Ream]

On Sun, Apr 28, 2024 at 10:46 PM Félix <felix...@gmail.com> wrote:

Introducing LeoJS Beta 0.2.13 🚀

Congratulations! I've been playing with LeoJS, and it looks great. I'll be using LeoJS more now.

LeoJS is already a viable alternative to desktop leo.

It will be valuable to compare the vs-code way with the Leo way as we explore improving the VR pane.

Love the graphics.  Candlelight on the console.  Hehe. Old old disk format. Hilarious. I expected to see Chewbacca!

Edward

P.S. Some suggestions:

Please fix #123 asap.

It's way too easy to miss the excellent demo movies! I suggest creating a separate section in the readme just for the videos near the top so everyone will be sure to see them.

EKR

[Thomas Passin]

Nice work and nice graphics!  VSCodium on my system doesn't know about this new version yet, I've still got 0.2.11.

I like the way that the new Open Aside works.  Trying it out, I noticed that it makes #104 more important.  That's because it's so easy to forget which node belongs to the Aside editor, and the new-style gnx-based identifiers don't help the user know which node it is.  Or if the path-based UNL is too long, at least show the node headline.

[Edward K. Ream]

On Monday, April 29, 2024 at 5:13:42 AM UTC-5 Edward K. Ream wrote:

I've been playing with LeoJS, and it looks great. I'll be using LeoJS more now.

This release of LeoJS is a personal milestone. I shall work on the remaining desktop issues using LeoJS!

Edward

[Viktor Ransmayr]

Hello Felix,

Same situation as reported by Thomas for me as well.

That is my VSCodium (version 1.88.1) instance running w/i a Fedora-39 VM does  not get notified about new versions of LeoJS.

tbp1...@gmail.com schrieb am Montag, 29. April 2024 um 13:52:36 UTC+2:

Nice work and nice graphics!  VSCodium on my system doesn't know about this new version yet, I've still got 0.2.11.

I noticed this already when you announced LeoJS 0.2.12 - but - thought it was a local issue on my side, since I was in the midst of upgrading from Qubes OS 4.1 to 4.2 ...

Let me know if you need further info about my environment details !

With kind regards,

Viktor

[Félix]

Victor and Thomas (and other vscodium users)

As you can see from this link, https://open-vsx.org/extension/boltex/leojs the new version was successfully deployed on open-vsx, at around the same time I deployed it to Microsoft's marketplace.  

Not sure here, but I think the 'auto update' of vscodium's extensions might require a restart of vscodium. Even if you just opened it. (at startup it will detect a new version and download it but it will not 'restart' the extension with the new version.) The regular vscode also does that, but it does automatically update them. It's just that it needs to restart once it detects that a new version is available after boot up.

... Or, maybe vscodium needs their extensions to be manually updated when a new version is published on their market. I'm not sure because I've never used  vscodium personally.

I've just made a quick google search and it seems to be many issues and tickets about vscodium not automatically updating extensions that have newer versions available. 

Hope this helps...

In any cases thanks for posting those reports, as someone else who's more knowledgeable with vscodium might chime in and give a better explanation! :)

Félix

[Thomas Passin]

On Monday, April 29, 2024 at 7:22:18 PM UTC-4 Félix wrote:

Victor and Thomas (and other vscodium users)

As you can see from this link, https://open-vsx.org/extension/boltex/leojs the new version was successfully deployed on open-vsx, at around the same time I deployed it to Microsoft's marketplace.  

I have no idea how to use open-vsx...

 

Not sure here, but I think the 'auto update' of vscodium's extensions might require a restart of vscodium. Even if you just opened it. (at startup it will detect a new version and download it but it will not 'restart' the extension with the new version.) The regular vscode also does that, but it does automatically update them. It's just that it needs to restart once it detects that a new version is available after boot up.

... Or, maybe vscodium needs their extensions to be manually updated when a new version is published on their market. I'm not sure because I've never used  vscodium personally.

There's  a control to search for updates to the extensions at the top of the Explorer pane.  At the same place you can enable automatic refresh, which is enabled on my copy of vscodium.  Searching for updates says they are all up to date.  

I solved the problem by uninstalling LeoJS, then re-installing it.  I still had to "Restart Extensions" and then I had to restart vscodium. Finally, I now have 0.2.13 running in vscodium.

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Dienstag, 30. April 2024 um 01:22:18 UTC+2:

Victor and Thomas (and other vscodium users)

As you can see from this link, https://open-vsx.org/extension/boltex/leojs the new version was successfully deployed on open-vsx, at around the same time I deployed it to Microsoft's marketplace. 

 

Yes, I was aware of that.

 

Not sure here, but I think the 'auto update' of vscodium's extensions might require a restart of vscodium. Even if you just opened it. (at startup it will detect a new version and download it but it will not 'restart' the extension with the new version.) The regular vscode also does that, but it does automatically update them. It's just that it needs to restart once it detects that a new version is available after boot up.

What was unexpected to me is that VSCodium did not notify me about the available update of the extension.

What ( I think ) I did, is that I had to explicitly search for 'leo' in the extension view - and - only then it did show the notification & allowed me to install the update ...

And you are right that an explicit restart of VSCodium instance IS required - but - at least I did not have to re-install LeoJS as Thomas has reported.

I'll look into the exact behavior details of VSCodium, when you publish the next version of LeoJS.

 

... Or, maybe vscodium needs their extensions to be manually updated when a new version is published on their market. I'm not sure because I've never used  vscodium personally.

I've just made a quick google search and it seems to be many issues and tickets about vscodium not automatically updating extensions that have newer versions available. 

Hope this helps...

Thanks a lot for your feedback & support !

Viktor

 

[Thomas Passin]

On Tuesday, April 30, 2024 at 4:07:16 AM UTC-4 viktor....@gmail.com wrote:

Hello Felix,

Félix schrieb am Dienstag, 30. April 2024 um 01:22:18 UTC+2:

Victor and Thomas (and other vscodium users)

As you can see from this link, https://open-vsx.org/extension/boltex/leojs the new version was successfully deployed on open-vsx, at around the same time I deployed it to Microsoft's marketplace. 

 

Yes, I was aware of that.

 

Not sure here, but I think the 'auto update' of vscodium's extensions might require a restart of vscodium. Even if you just opened it. (at startup it will detect a new version and download it but it will not 'restart' the extension with the new version.) The regular vscode also does that, but it does automatically update them. It's just that it needs to restart once it detects that a new version is available after boot up.

What was unexpected to me is that VSCodium did not notify me about the available update of the extension.

It was the same for me.  It has shown me updates for other extensions in the past, though.  I wonder if a recent update to vscodium broke that ability. 

What ( I think ) I did, is that I had to explicitly search for 'leo' in the extension view - and - only then it did show the notification & allowed me to install the update ...

I saw LeoJS in the extension  view but it didn't show an update was available.

 

And you are right that an explicit restart of VSCodium instance IS required - but - at least I did not have to re-install LeoJS as Thomas has reported.

I had restarted vscodium several times without any updates happening to LeoJS before I thought to un-install it first.

 

[Edward K. Ream]

On Monday, April 29, 2024 at 9:41:57 AM UTC-5 Edward K. Ream wrote:

This release of LeoJS is a personal milestone. I shall work on the remaining desktop issues using LeoJS!

I can now recommend LeoJS without reservation! LeoJS supports all of Leo's essential features enhanced with vs-code's stupendous capabilities.

I have filed some minor LeoJS issues: #123, #124, #125, #126, #127, and #128. Most contain easy workarounds.

LeoJS rocks!

Edward

[Thomas Passin]

On Tuesday, April 30, 2024 at 10:46:00 AM UTC-4 Edward K. Ream wrote:

On Monday, April 29, 2024 at 9:41:57 AM UTC-5 Edward K. Ream wrote:

This release of LeoJS is a personal milestone. I shall work on the remaining desktop issues using LeoJS!

I can now recommend LeoJS without reservation! LeoJS supports all of Leo's essential features enhanced with vs-code's stupendous capabilities.

I can't go that far at this time because I depend on several GUI plugins I've written.  Maybe at some point I'll learn enough to port them to LeoJS...

Speaking of that, is there a plugin capability for LeoJS, or if not how would we do something equivalent? 

[Viktor Ransmayr]

Hello Edward,

Am Di., 30. Apr. 2024 um 16:46 Uhr schrieb Edward K. Ream <edre...@gmail.com>:

On Monday, April 29, 2024 at 9:41:57 AM UTC-5 Edward K. Ream wrote:

This release of LeoJS is a personal milestone. I shall work on the remaining desktop issues using LeoJS!

I can now recommend LeoJS without reservation! LeoJS supports all of Leo's essential features enhanced with vs-code's stupendous capabilities.

I'd agree to your statement, if #80 would have been addressed already.

IMO Leo's essential features include / require the ability to create rST - and / or - sphinx documents.

With kind regards,

Viktor

[Edward K. Ream]

On Tue, Apr 30, 2024 at 9:52 AM Thomas Passin <tbp1...@gmail.com> wrote:

>> I can now recommend LeoJS without reservation! LeoJS supports all of Leo's essential features enhanced with vs-code's stupendous capabilities.

> I can't go that far at this time because I depend on several GUI plugins I've written.

Fair enough. I was talking about LeoJS's basic editing capabilities.

And as Viktor says, testing the effect of changes on desktop Leo does still require Leo.

Edward

[Edward K. Ream]

On Tuesday, April 30, 2024 at 9:46:00 AM UTC-5 Edward K. Ream wrote:

I have filed some minor LeoJS issues: #123, #124, #125, #126, #127, and #128. Most contain easy workarounds.

I have just closed #127 because the requested page already exists as part of the readme file:

https://github.com/boltex/leointeg?tab=readme-ov-file#keybindings

Edward

[Félix]

Thanks Edward, Thomas and Viktor for the bug reports and feature requests you've filed on the repository! 

really appreciated. 

#80 will be addressed soon after I setup LeoInteg with the new cool features I just added to LeoJS! 

(Yes, LeoJS now leads LeoInteg feature-wise!)

Thanks again to you all for trying out and reporting bugs on the LeoJS beta issues page!!

(I've now added an issue template to help remind leonistas to grab a screenshot when reporting and describing an issue! 😋 hehe! )

Félix

[Edward K. Ream]

On Wed, May 1, 2024 at 8:02 PM Félix <felix...@gmail.com> wrote:

Thanks Edward, Thomas and Viktor for the bug reports and feature requests you've filed on the repository! 

You're welcome. I'm enjoying the transition to LeoJS!

(I've now added an issue template to help remind leonistas to grab a screenshot when reporting and describing an issue! 😋 hehe! )

Excellent. For reference, the template appears when someone chooses "New Issue" and then clicks "Get Started".

Edward