THE NEXUS ECOSYSTEM
Six products. One development ecosystem.
Create in a workspace that understands the project. Compile native code, describe the relationships, and automate the work around it. Bring applications and games to life on a shared engine foundation.
Nexus connects these activities through six first-class products. Each has its own purpose; together they cover the workspace, languages, workflow, and application foundation.
Create and experience
- Nexus Code: Integrated Development Environment. The Nexus IDE experience built on Visual Studio Code: Pascal and Nexus Script language services, project integration, builds, targets, and native debugging.
- Nexus Gear: Mobile & Game Development. A shared application engine for mobile experiences and games, including desktop games, with Lua authoring, application controls, native extensions, and connected build workflows.
Compile and build
- Nexus Pascal: Compiler and Runtime. Native Object Pascal compilation with matching destination runtimes and compiler-native runtime packages.
- Nexus Build: Project Build System. Explicit projects, dependencies, tools, and published outputs, with producers built before consumers.
Model and automate
- Nexus Script: Structured Modeling Language. Structured information, references, composition, dialects, and selected variants.
- Nexus Forge: Workflow Automation. Compose builds with filesystem operations, downloads, archives, generation, and release assembly.
How the pieces connect
Nexus Code brings language and project context into VS Code. Nexus Script describes projects and workflows. Nexus Build interprets project descriptions and invokes tools such as Nexus Pascal; Nexus Forge composes those builds with wider automation.
Nexus Gear supplies a distinct application foundation for Lua-based mobile experiences and games. Pascal plugins connect through the native bridge and matching SDKs. Code's Pascal and Nexus Script services support that side of the workflow; Lua authoring and debugging retain their own tooling.
These are complementary responsibilities, not a requirement to use every product in every project. The command-line tools work independently of VS Code. Gear applications do not have to contain a Pascal plugin.
Pascal with access to the native ecosystem
C and C++ projects can participate in the same dependency graph as Pascal applications. Nexus Build coordinates native producers and their published paths; Nexus Pascal links compatible objects and libraries through explicit declarations and bindings. NXArchive's C codecs and Nexus Gear's native engine/plugin boundary show this in practice.
Explore native project integration
Continue exploring
The ecosystem also includes desktop GUI libraries, NexusTest, and the wider Nexus libraries.
See platform support for the distinction between development hosts, compiler destinations, engine builds, and device validation.