INTEGRATED DEVELOPMENT ENVIRONMENT
Nexus Code
Understand the code. Work with the project.
Nexus Code brings the Nexus development environment into Visual Studio Code. Language services, project integration, build targets, and native debugging work together around the project you are developing.
VS Code supplies the editor platform, workbench, and extension host. Nexus supplies the language services and project/toolchain integration that connect the workspace to the wider development system.
Language services with project context
Separate Pascal and Nexus Script language servers provide language-aware editing rather than only syntax coloring.
| Pascal | Nexus Script |
|---|---|
| Diagnostics, completion, symbols, navigation, and references | Compiler and dialect diagnostics, completion, hover, symbols, and imported-file links |
| Routine declaration/implementation navigation and refactoring services | Definition navigation, binding-aware rename, references, semantic coloring, folding, and formatting |
| Analysis informed by the selected project and configured source/search paths | Shared compiler analysis with selected targets and unsaved imported documents |
Language-server analysis supports editing. Compiling the project with Nexus Pascal establishes compiler acceptance.
The project belongs in the editor
Select an active project, choose build and analysis targets, and run builds through Nexus Build. The editor uses the same project descriptions and installed tool environment as command-line development.
The project editor works with project variants, sources, packages, and configuration through the shared language services. Project creation and Lazarus import commands request a plan from the Pascal language server and create the planned files. Review imported projects against their intended compiler and dependencies.
Build and select targets Start or import a project
Native debugging in the same workspace
Nexus Code bundles CodeLLDB and its LLDB runtime for Windows x64 and Linux x64. The nexus debug type provides breakpoints, stepping, stack frames, variables, watches, and attachment through that backend. A configured build task can run before a debug launch.
The simple expression evaluator is not a Pascal expression parser. Lua debugging is a separate integration; seamless Pascal/Lua stepping is not provided.
Connected, with clear responsibilities
Nexus Script describes projects and their relationships. Nexus Build owns build execution. Nexus Forge composes wider workflows. Nexus Code brings those project and language concepts into the workspace without maintaining a second compiler environment.
For Nexus Gear, Code provides the Pascal plugin and Nexus Script workflow side of development. Its Pascal and Nexus Script language services are not a claim of a built-in Lua IDE or a visual mobile designer. The general resolved-definition inspector is also outside the current editor delivery.
Get started
Use the existing Nexus Setup editor-integration option and follow the quick start. VS Code remains the underlying editor; the Nexus command-line tools can also be used independently.