bQUARKz 2f289b9425
All checks were successful
JaCoCo Coverage #### Project Overview No changes detected, that affect the code coverage. * Line Coverage: 61.88% (17291/27941) * Branch Coverage: 52.91% (6692/12647) * Lines of Code: 27941 * Cyclomatic Complexity: 11191 #### Quality Gates Summary Output truncated.
Test / Build skipped: 11, passed: 577
Intrepid/Prometeu/Studio/pipeline/head This commit looks good
Intrepid/Prometeu/Studio/pipeline/pr-master This commit looks good
update gitignore
2026-05-08 10:30:54 +01:00
..
2026-05-05 13:39:24 +01:00
2026-05-06 15:28:37 +01:00
2026-05-08 10:30:54 +01:00
2026-05-05 13:39:24 +01:00
2026-05-06 15:28:37 +01:00
2026-05-05 13:39:24 +01:00

Prometeu VS Code Extension

VS Code bridge for Prometeu Studio.

This extension does not start the language server itself. It connects to the Prometeu Studio LSP server running locally.

VS Code Extension
    -> vscode-languageclient
    -> TCP 127.0.0.1:7775
    -> Prometeu Studio Java/LSP4J

Requirements

  • Node.js
  • npm
  • VS Code
  • Prometeu Studio running with the embedded LSP server enabled

The Studio LSP server must be listening on:

127.0.0.1:7775

Install dependencies

From this directory:

npm install

Compile

npm run compile

This generates:

out/extension.js

Run in development mode

Open this extension folder in VS Code:

code .

Press:

F5

This opens a second VS Code window called Extension Development Host.

In that second window, open a Prometeu project and create/open a file like:

main.pbs

or:

main.barrel

Expected output in:

View -> Output -> Prometeu LSP
Prometeu VS Code extension activated.
Connecting to Prometeu Studio LSP at 127.0.0.1:7775...
TCP connection established with Prometeu Studio.
Prometeu Studio LSP client started.
[Info] Hello from Prometeu Studio LSP

Run commands manually

In the Extension Development Host window:

Cmd+Shift+P
Prometeu: Connect to Studio LSP

To restart the client:

Cmd+Shift+P
Prometeu: Restart Studio LSP

Package as VSIX

npm run compile
vsce package --allow-missing-repository

This creates a file like:

prometeu-vscode-extension-0.0.1.vsix

Install locally

code --install-extension prometeu-vscode-extension-0.0.1.vsix --force

Then open a Prometeu project normally:

code /path/to/prometeu-project

With Prometeu Studio running, opening .pbs or .barrel files should activate the extension and connect to the Studio LSP server.

Configuration

Default settings:

{
  "prometeu.studio.host": "127.0.0.1",
  "prometeu.studio.port": 7775
}

These can be changed in VS Code settings if needed.

Current status

The extension currently provides only the minimal LSP client bridge:

  • registers .pbs
  • registers .barrel
  • connects to Prometeu Studio over TCP
  • starts a VS Code LanguageClient
  • receives LSP messages from the Java/LSP4J server

The Studio remains the source of trut