boxlang-runtime-desktop

Coordinate Electron desktop BoxLang apps with a local MiniServer runtime.

16|78|Updated Nov 28, 2014

Search Tags:#devops #packaging #electron #lifecycle #desktop #boxlang #miniserver

Ready to run

npx skills add https://github.com/ortus-docs/coldbox-docs --skill boxlang-runtime-desktop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: boxlang-runtime-desktop
Source: https://github.com/ortus-docs/coldbox-docs/tree/main/.agents/skills/boxlang-runtime-desktop
Command: npx skills add https://github.com/ortus-docs/coldbox-docs --skill boxlang-runtime-desktop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the complexity of building and packaging BoxLang desktop apps that embed Electron and a local MiniServer by coordinating lifecycle, development-time controls, and cross-platform packaging rules.

Core Features & Use Cases

Electron lifecycle management: window, tray, menu, and keyboard shortcuts coordinated with a local MiniServer.
MiniServer orchestration: start/stop/restart/readiness with dev versus production configurations.
Packaging and runtime configuration: manage runtime packaging via runtime/Package.bx and the .boxlang-dev.json/.boxlang.json defaults.
File-system layout guidance: preserve modular boundaries with app/electron/* and runtime files, ensuring predictable structure.

Quick Start

Set up the Electron desktop shell, initialize the BoxLang MiniServer, and validate the development packaging workflow using miniserver.json and runtime/Package.bx.

Frequently Asked Questions about boxlang-runtime-desktop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I package a BoxLang desktop app with Electron for cross-platform deployment?▼

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.

How does the BoxLang MiniServer lifecycle work inside an Electron desktop app?▼

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.

What is the correct file-system layout for a BoxLang MiniServer and Electron frontend?▼

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.

Can I manage Electron window and tray menus using a BoxLang MiniServer runtime?▼

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.

Why do I need both .boxlang-dev.json and .boxlang.json configuration files for desktop development?▼

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.

What are the packaging constraints when embedding a local MiniServer in Electron?▼

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.