The ToolDef interpreter now supports reading .tooldefx files, ToolDef files in an XML format (issues #701 and #731).

The ToolDef documentation breadcrumbs are now consistent with the table of contents (issue #38).

The ToolDef documentation table of contents now has proper links for items that link to sections on pages rather than to entire pages (issue #38).

The ToolDef website has an improved link color (issue #38).

The ToolDef interpreter has a new Tool invocation option to invoke a specific tool with chosen arguments, rather than executing the entire script (issue #578).

The writefile built-in tool has a new optional newline parameter, allowing to configure new line handling. The default is still to use the new lines of the current platform. See the documentation for further details (issue #571).

The readlines and writefile built-in tools have been made more robust with respect to closing file streams in case of I/O errors (issue #571).

The readlines built-in tool now uses the UTF-8 encoding when reading files, rather than the platform’s default encoding (issue #571).

The readlines and writefile built-in tools now have improved documentation (issue #571).

The ToolDef interpreter’s help text now properly explains the tool’s exit codes (issue #573).

The ToolDef interpreter documentation has been slightly improved (issue #578).

The ToolDef documentation has some improvements related to 'file separator' terminology (issue #450).

The ToolDef documentation for the chfileext tool has some formatting fixes (issue #536).

The filenewer tool now only checks for modification time differences that are at least one millisecond (issue #259).

Small documentation improvement for the filenewer tool documentation (issue #456).

Normally, .tooldef files are opened with the ToolDef text editor. Large files are now however opened with the default non-ToolDef text editor to avoid performance issues. You can open a file in an editor of your choosing by right clicking it and selecting Open With and then selecting the editor of your choosing, or choosing Other…​ to open a dialog to choose from a larger selection of editors (issue #199).

The ToolDef text editor now has theming support, and comes with a dark theme in addition to the existing light theme. The text editor now automatically uses its dark theme when the Eclipse built-in dark theme is used, and uses a light theme otherwise. The text editor theming behavior can be configured via the Eclipse Preferences dialog (issue #347).

The ToolDef text editor light theme’s default color has changed from a near-black slightly-brown color to pure black (issue #347).

Links in the documentation to non-ToolDef ESCET documentation webpages now use version-specific URLs (issue #386).

The issue numbers in the release notes now link to the corresponding GitLab issue (issue #396).

Small website style improvements (issue #367).

The release notes for each version now contain the release date, with the exception of milestone releases and release candidates (issue #314).

Introduced a brand new website (issue #35).

Many website URLs have changed due to various website structure changes (issues #35 and #73).

Various documentation/website textual improvements, style improvements and other changes (issues #35 and 54).

Multiple small error message improvements (issue #248).

The website and Eclipse help now use multi-page HTML rather than a single HTML file, although the website still contains a link to the single-page HTML that allows easily searching the full documentation (issue #36).

Enabled section anchors for documentation on the website, and disabled section anchors for Eclipse help (issue #36).

Several small documentation fixes and improvements (issue #166).

We no longer use separate language and tool versions. The .tooldef2 file extension has been changed to .tooldef as part of this change.