DarkMatter Software
DarkMatter | DarkForge IDE / SDK 1.3.0 Beta
DarkMatter Development Systems

DarkForgeIDE. SDK. Module Forge. Development Command Center.

1.3.0BETA

DarkForge has evolved from a focused development baseline into an entirely new, test-ready IDE and SDK package. Version 1.3.0 brings source development, project spaces, local environments, task execution, module discovery, offline dependency storage, documentation, packaging, testing, delivery tools, and selectable themes into one integrated desktop system.

DarkMatter DarkForge icon
Release1.3.0 Beta
ReadinessOfficially test ready
DistributionPrivate beta group
Module SystemPlug-and-play defaults
Public DownloadNot available

An Entirely New IDE / SDK Package

BETA CORE

DarkForge 1.3.0 is no longer just a source editor with supporting utilities. It is the central control panel for the DarkMatter development ecosystem, designed so projects, tools, environments, documentation, builds, packages, and delivery targets can share a common home without being welded into one brittle monolith.

01CreateStart or import a project space.
02CodeOpen Kode and work with project source.
03PrepareCreate local environments and resolve dependencies.
04RunExecute project tasks and inspect output.
05PackageBuild release assets and desktop launchers.
06DeliverTest or deploy through integrated modules.

IDE Functions

INTEGRATED
  • Project and module explorers
  • Project spaces with icon-aware navigation
  • Quick Launch module slider with custom ordering
  • Kode source editor integration
  • Tabbed workspaces, headers, console, and docked tools
  • Project creation, documentation, packaging, delivery, and settings routes

Local Environments & Tasks

ISOLATED
  • Create and manage project-local Python environments
  • Keep the IDE runtime separate from project dependencies
  • Run project commands and tasks through the selected interpreter
  • Capture task output in the integrated console
  • Reuse cached packages without polluting system Python
  • Maintain project-specific requirements and launch behavior

Modules Designed for the Forge

DEFAULT MODULE SET

DarkForge modules live as independent applications inside the Modules directory. Each module can provide a manifest, icon, entry point, framework information, dependencies, services, warnings, and launch mode. The IDE discovers them, presents them in the interface, and launches them as separate processes when isolation is the safer choice.

Module Storage & Dependency Strategy

PORTABLE FOUNDATION

The module architecture is deliberately plug-and-play. A module can be added beneath Modules/, described through darkforge.module.json, and discovered without rewriting the IDE. Shared storage provides a home for wheels, cached installers, requirements, indexes, and other reusable development resources, while individual modules remain independently maintainable.

DarkForge package structure
DarkForge/
├── IDE/
├── Modules/
│   ├── LUX/
│   ├── ModUI/
│   ├── CVE_Explorer/
│   └── ...
├── Storage/
│   ├── wheels/
│   ├── package-cache/
│   └── requirements/
└── tools/

Theme Engine

NEW
  • DarkForge Default command-center palette
  • Forge Light daytime workspace
  • Dark Sorcerer violet theme
  • Theme-aware project spaces, tabs, headers, and controls
  • Icon fallback when a module has no icon.png
  • SkinLab path toward custom image-driven interfaces

Control Center Routes

WORKFLOW
  • Projects: browse and open active work
  • Modules: discover and launch installed tools
  • Create App: enter the Kode development workspace
  • Documentation: open LUX
  • Package: open Desktop Generator
  • Deliver: route toward Flask, FlexHost, or VoidCrawler

Project History: From Baseline to Beta

0.3.0 → 1.3.0

The original 0.3.0 project established the stable foundation: project scaffolding, source editing, isolated environments, project intelligence, build history, release preparation, SQLite-backed project metadata, and protection of system Python. That release remains an important historical checkpoint.

Later experimental development proved which ideas belonged in the core and which should become modules. A failed branch was deliberately rejected when it harmed file editing and introduced distracting watcher behavior. The stable line was protected, the master interface was rebuilt as the DarkForge Control Panel, and independent DarkMatter applications were converted into manifest-driven modules.

Versions 1.0 through 1.3 transformed the project into a broader IDE / SDK package: module discovery, Quick Launch, project and module workspaces, integrated routes, Kode, ModUI, shared storage, dependency management, icon-aware navigation, theme selection, and the default module ecosystem now presented in this beta.

Beta Access

APPLICATION REQUIRED
β
DarkForge 1.3.0 is officially test ready, but it is not a public download.
Developers and testers interested in joining the beta group can apply through the DarkMatter Software Facebook page. Beta participation is intended for hands-on testing, useful feedback, module validation, and real development workflows.

Beta Focus

TEST
  • Module discovery and launch reliability
  • Environment and dependency workflows
  • Project navigation and task execution
  • Theme consistency across the IDE
  • Packaging and delivery integration
  • Usability on real projects