Active system program · native interfaces

GUI.Forms
and Web.Forms

Keep the convenient language of web layout. Replace the browser with an owned tree of typed native controls.

Current question

How much familiar web-shaped authoring can compile into a small, inspectable native control system without losing native behavior?

Two layers, one direction

Runtime

GUI.Forms

A custom-rendered C++ alternative to WinForms with retained controls, layout, input, painting, and native macOS output alongside PE64/Wine proving builds.

Compiler

Web.Forms

A strict browser-valid subset of HTML and CSS becomes a typed intermediate representation, native descriptors, and a GUI.Forms control tree.

Boundary

No browser in the shipped program

The browser is an authoring and preview surface. The compiled application contains native controls and the owned runtime, not Chromium or a web view.

Proving ground

File Manager

The interface system is being exercised inside a real local-computing application rather than a catalogue of isolated widgets.

What exists

The program already includes a strict parser, typed intermediate representation, native descriptor output, retained control trees, AppKit hosting, and Win32-oriented proving paths. The next work is not to declare web compatibility. It is to enlarge the bounded language only where each addition compiles into a clear native behavior.