CRESA's Browser Scenes Begin Sharing One Runtime

One problem, many browser scenes

As more of CRESA's presentation systems are built using HTML, CSS and JavaScript, a new architectural problem starts becoming increasingly important. Every browser scene needs a reliable way to communicate with the rest of CRESA. Rather than allowing each scene to develop its own completely separate solution, work begins on a shared browser scene runtime.

The goal is to give CRESA's browser-based presentations a common foundation for detecting where they are running and connecting to the services they need.

Local inside OBS, hosted outside it

Development also begins on a hybrid approach to browser scenes. CRESA's scenes primarily need to operate locally as part of the broadcast, but being able to run those same scenes as hosted previews is extremely useful during development and testing. Early hybrid runtime configuration is introduced for scenes including BRB and No Game Active, allowing them to adapt depending on the environment in which they are loaded.

This starts reducing the divide between the version being developed and the version actually running inside OBS.

Expanding the shared foundation

The runtime work quickly spreads beyond the first experimental scenes. Capture Status begins adopting the hybrid runtime, while Webcam Border gains its own local scene hosting as development on that presentation continues. Generic localhost scene hosting is also introduced, followed by engine support for starting that shared scene host.

Instead of every new browser presentation requiring another completely independent hosting arrangement, CRESA is beginning to establish infrastructure that can be reused across the suite.

Building a presentation platform

This work is largely invisible compared with a new alert animation or a new scene, but it becomes increasingly important as CRESA grows. Browser scenes are no longer being treated as isolated webpages. They are becoming parts of a wider presentation platform with shared expectations about how they are hosted, how they connect to CRESA and how they behave across development and production environments.

The more presentation systems CRESA gains, the more important it becomes that they all speak the same language underneath.