Downloadable VSCode extension

[JaroslavTulach]

Pull Request Description

Updating the Enso4Igv GitHub action to also archive the .vsix extension.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated including installation instructions
• Screenshots/screencasts have been attached
• All code follows proper XML formatting
• All code has been tested:
  • CI produces and uploads the right the artifact

[JaroslavTulach]

CI actions run has just produced a ZIP file with VSCode Extension.

Download "VSCode Extension" artifact from the latest actions run, unzip, install into VSCode:

Your Enso files will get proper syntax coloring. You'll be able to debug Java/Enso code interchangeably.

[Akirathan]

Very cool! I have just downloaded the VSIX artifact and installed it in my VSCode. Everything works as expected. Thanks.

[Akirathan]

In the future, we might want to add these artifacts as additional assets to nightly releases.

[JaroslavTulach]

One can test "pristine" code with:

code --extensions-dir /tmp/code/ext --user-data-dir /tmp/code/usr

then the code starts with completely empty configuration. After installing the Enso .vsix file (and reloading window) I see two extensions:

With such configuration I can choose File/Open Folder... and open root of Enso Git Repository (presumably already built with sbt buildEngineDistribution). Following set of projects is opened and ready for use:

With the workspace opened, you an open any Enso or Java file. Let's for example open Vector_Spec.enso - a set of unit tests for Vector:

It is possible place breakpoints into the Vector_Spec.enso file. For example:

Let's do a bit of debugging. Select "Listen to 5005" debug configuration:

And then just execute the engine distribution in debug mode:

sbt:enso> runEngineDistribution --debug --run test/Tests/src/Data/Vector_Spec.enso

The same way you can place breakpoint into Java class like PanicException.java and continue debugging:

Enjoy. And if you ever want to jump from Java to Enso, please remember there is the "Pause in GraalVM Script" action. Select it and continue with F5 - as soon as the code reaches a statement in Enso, it stops:

[radeusgd]

Cool that it will be now much easier for users to get the extension.
And the docs look great!

[JaroslavTulach]

This is the "major and minor" version of the .nbm file and .vsix extension. Bump it up when some important functionality changes.

[JaroslavTulach]

Every build of enso4igv.yml github action produces extension with a unique version. The major and minor numbers are specified by human and are taken from the pom.xml. The "micro" version is the $GITHUB_RUN_NUMBER.

To avoid the "micro" version to reach the sky, feel free to bump the minor version and then decrease the $GITHUB_RUN_NUMBER by a constant (currently 1666) to start counting from zero again.

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2023-09-21):

Progress: - publishing VSCode extension: #7861

• upgrading frgaal PR: Upgrading to Frgaal compiler 20.0.1 #7860
• evaluating gu install js: Adjusting to GraalVM for JDK21+ #7855 (comment)
• review of conversion method suggestions: Send conversion method suggestions #7857 (review)
• discussing y.js and how to emulate WebSocket in Graal.js: https://graalvm.slack.com/archives/CN9L59P61/p1695307846813729?thread_ts=1695300535.788289&cid=CN9L59P61 It should be finished by 2023-09-22.

Next Day: Getting ready for next week's GraalVM workshop

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2023-09-22):

Progress: - merged GraalVM21 support: #7855

• fixed & merged VSCode extension: Downloadable VSCode extension #7861
• Preparing presentation for GraalVM meetup
• Reported: Enso Engine bundle doesn't work without downloading #7871
• standup & meetings It should be finished by 2023-09-22.

Next Day: Getting ready for next week's GraalVM workshop