Skip to content

v6.0.0

Choose a tag to compare

View all tags
@znorman-harris znorman-harris released this 12 Mar 20:19
· 679 commits to main since this release
v6.0.0
67dc3af

Introducing IDL Agent and ENVI Agent! This marks our first initiative to enable LLMs to more effectively use ENVI and IDL. Here's what they can do:

  • Write and run IDL code like a modern developer

  • IDL instructions are automatically configured for you and, through our extension settings, you can add your own instructions too

  • Plan and execute remove sensing workflows with ENVI (requires ENVI to be installed)

  • Open data in ENVI, run tools interactively, and summarize workflows as notebooks or code

Important note: These agents are auto-configured through VSCode and are based on MCP tools and instructions. Note that they are agents in name and not the VSCode agents that you can select in new chats.

Other Changes

Migrated support for our MCP server to use the formal VSCode API instead of setting configuration.

The MCP server will automatically find a port and be accessible when creating a nee chat.

You need to have ENVI installed to run the ENVI MCP tools.

The IDL type parsing logic uses a formal parser which addressed some issues and bugs. This new parser is more robust and offers some added benefits:

  • Full support for literal types (numbers, strings, etc.)

  • Track the literal value for types, which you will see in hover help

  • Reworked hover help for types that uses our IDL syntax highlighting and is aware of variables, keywords, properties, and more.

  • Our hover-help for properties from task files now uses choice lists and gives more insight into what valid parameters can be.

  • Another benefit of the new type parser is much richer type information about parameters and their literal values

Syntax highlighting for types has been updated to match the new type parser which resolved some issues with types not being highlighted in docs blocks.

Revamped hover help for variables, arguments, keywords, and properties to support new type changes.

Fixed a typo in one of the paths we check to find IDL on Mac when you have ENVI + IDL installed

New preference (enabled by default) that has the theme of IDL and ENVI match that of VSCode. This means, if you have a dark mode programming theme, IDL and ENVI will launch in dark mode. Do note that, if we detect IDL_THEME as an environment variable, this preference has no effect.

Change the way that we detect the types from ENVI and IDL tasks in your code. If we don't know which ENVI or IDL task you are using, we set the type as a generic ENVITask or IDLTask. This makes sure you still get some type of auto-complete and hover help for a better developer experience.

Fixed an issue with task generation not correctly adjusting the names of paired parameters.

Fixed a bug with IDL Notebooks embedding odd graphics from the ENVI UI when running cells with the ENVI UI open.

Fixed an issue where empty paths could be added to the IDL search path through VSCode settings.

Re-worked the logic for managing and setting IDL's search path. It follows this process:

  • If you have workspaces open, and have opted in to adding to the path (default), add each folder
  • If you have set IDL's path through VSCode preferences, add each folder
  • If you have IDL_PATH in your environment variable, add each folder
  • Always make sure the IDL_DEFAULT path is present

Added a new utility to migrate ENVI Deep Learning IDL code to ENVI Deep Learning 4.0 API (there were some task name changes.)

Fixed an issue where the IDL directory was not being automatically set on extension startup when it hasn't been specified.

Fixed an issue where, if IDL was not configured on a machine, that hover help generation would fail when getting links for images.

Assets 3
Loading