Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Current »

Pre-requisites

  • Visual Studio Code  [use VSCode version 1.72.1]
    https://code.visualstudio.com/download

  • ARES Commander 2024 x64, any other ARES verticals (ARES Mechanical ARES Maps, etc.) & Graebert OEM Applications.

Platform support
Greabert LISP Extension available on Windows, Mac & Linux OS.

System Requirements

Setup

To install Graebert LISP Extension [FLISP] plugin:

  1. Do one of the following:
    Type LISPIDE.
    - or -
    Type VLIDE.
    The following message displays: “Do you want to Install the Graebert LISP Extension?“.

  2. Confirm by clicking OK.
    Graebert LISP Extension will install using VLIDE command from VS Code Market Place.

Alternatively, you can install the Graebert LISP Extension directly from Market Place by searching Extension Section(Ctrl+shift+X) of VS Code.

FLISP Extension adds in %userprofile%/.vscode of the system. You can see the Extension Profile in the VS Code application.

Debugging

  1. Run ARES Commander 2024 or later.

  2. In the Options dialog box, select System Options > Lisp Debugger and select Enable Debugging.

  3. Close ARES Commander to save the settings and launch it again.

  4. From the Visual Studio Code Menu select Run > Add Configuration.

  5. Add the Launch and Attach configuration options:

    • FLISP Debug: Attach

    • FLISP Debug: Launch

      Launch and Attach configuration options are added.

  6. FLISP Debug: Attach
    From the Run and Debug side palette of Visual Studio Code, select FLISP Debug: Attach and click Run (or press F5).
    The list of all running ARES Commander applications and OEMs appears. On attach, the status bar color changes from blue to orange. LISP files automatically load.
    You can run the LISP command in ARES Commander and debug the LISP functions.

    Tip: Pressing Ctrl+Shift+D displays the Run and Debug palette.

  7. FLISP Debug: launch
    First, you need to specify the path to ARES Commander executable file (ARESC.exe or the file corresponding to any other Graebert OEM application) in the Extension setting of Graebert LISP Extension.
    From the Run and Debug side palette of Visual Studio Code, select FLISP Debug: Launch and click Run (or press F5).
    When launching ARES Commander, the status bar color changes from blue to orange. LISP files automatically load. You can run the LISP command in ARES Commander and debug the LISP functions.

Features:

LISP Editor:

  • Syntax Highlighting

  • Snippet Completion for LISP & DCL

  • Smart Brackets

  • Comment Toggling

  • AutoComplete for LISP & DCL

  • Go-To-Definition and Peek Definition

  • Localization

  • LISP Encryption / Protection

  • Add & Update Header

  • Insert Region

  • Online Help

  • Load Current LISP File

  • Create Workspace

 LISP Debugger:

  • Attach/Launch

  • Start Debugging

  • Breakpoints

  • Step Over/In/Out

  • Variables [show last value]

  • Watch

  • Call Stack

  • Debug Console

  • Break On Error

  • Hover

 LISP Encryption / Protection

1.Click via Right Mouse Click to the top of your Lisp-file or press the shortcut keys CTRL+Shift+P to open the Command Palette…

2. Now select in the upcoming Combobox “FLISP: Protect LISP File

3. Before the protection you can configure a 2 characters key binding string, which is used for the encryption. This is not mandatory. It also works without these characters.

4. The resulting encrypted files can be found in a subfolder below the working or source files LISP folder. The protection tool encrypts all found LISP files of this folder and saved the encrypted copies under the subfolder \Out. A message is shown in the the right left corner of Microsoft Visual Code, where the files can be found.

  • No labels