Matthias Ladkau a1c29a0a08 feat: Debug support vor 5 Jahren
..
.vscode a1c29a0a08 feat: Debug support vor 5 Jahren
images 7f6ef4884b chore: Adding logo vor 5 Jahren
src a1c29a0a08 feat: Debug support vor 5 Jahren
syntaxes 0312fd1314 feat: Adding Game of Life example vor 5 Jahren
.vscodeignore f2ab07c742 feat: VS Code support vor 5 Jahren
README.md a1c29a0a08 feat: Debug support vor 5 Jahren
language-configuration.json f2ab07c742 feat: VS Code support vor 5 Jahren
notes.txt a1c29a0a08 feat: Debug support vor 5 Jahren
package.json a1c29a0a08 feat: Debug support vor 5 Jahren
tsconfig.json a1c29a0a08 feat: Debug support vor 5 Jahren

README.md

VSCode extension for ECAL

Folder content

  • package.json - manifest file
  • syntaxes/ecal.tmLanguage.json - Text mate grammar file
  • language-configuration.json - language configuration for VSCode

Build the extention

To build the extention you need npm installed.

VSIX file can be build with npm run package

Install the extension

The extention can be installed using a precompiled VSIX file which can be downloaded from here:

https://devt.de/krotik/ecal/releases

Launch config for ecal projects

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "ecaldebug",
			"request": "launch",
			"name": "Debug ECAL script with ECAL Debug Server",

			"serverURL": "localhost:43806",
            "dir": "${workspaceFolder}",
			"executeOnEntry": true,
			"trace": false,
		}
	]
}
  • serverURL: URL of the ECAL debug server.
  • dir: Root directory for ECAL debug server.
  • executeOnEntry: (optional) Execute the ECAL script on entry. If this is set to false then code needs to be manually started from the ECAL debug server console.
  • trace: (optional) Enable tracing messages for debug adapter (useful when debugging the debugger).

Developing the extension

In VSCode the extention can be launched and debugged using the included launch configuration. Press F5 to start a VS Code instance with ECAL support extention form the development code.