boxlang-runtime-desktop

To package a BoxLang desktop app with Electron, coordinate the runtime packaging via runtime/Package.bx and manage configuration defaults using the .boxlang-dev.json and .boxlang.json files. This ensures cross-platform deployment constraints are properly met.

The BoxLang MiniServer lifecycle inside an Electron desktop app is managed through coordinated start, stop, restart, and readiness checks. It relies on dev versus production configurations defined within the miniserver.json file to orchestrate the local server runtime.

The correct file-system layout preserves modular boundaries by separating Electron frontend files into app/electron/* and keeping runtime files in their designated structure. This predictable organization ensures proper lifecycle wiring and packaging for the desktop app.

Yes, you can manage Electron window, tray, menu, and keyboard shortcuts using a BoxLang MiniServer runtime. The desktop workflow coordinates these frontend Electron elements with the local MiniServer backend to enforce proper lifecycle wiring.

You need both .boxlang-dev.json and .boxlang.json configuration files to separate development-time controls from production defaults. This distinction enforces proper lifecycle wiring and manages MiniServer orchestration transitions between development and cross-platform deployment.

Packaging constraints when embedding a local MiniServer in Electron require managing the runtime via runtime/Package.bx and adhering to default configuration mappings. These constraints ensure the BoxLang runtime integrates predictably within the cross-platform desktop deployment.