Example 24 is a post-boundary Tree widget progression example.
The diagram copies system_tree.value.selected_node_value to published_tree.value.selected_node_value and to the public selected_node_value output. It also declares system_tree.nodes.* -> published_tree.nodes.* as a frog.tree.records dataflow so editable Tree cell content is published by Execute through the example graph, not by an implicit UI synchronization. The .frog file owns the finite hierarchy, node ids, node tags, labels, numeric node values, editable record data, expansion state, selected node, layout, visible-item posture, behavior flags, and instance-level style. The .wfrog package references the Default Tree realization and SVG asset. A hardcoded HTML-only replacement is not a valid implementation.
This example is accepted at the same C++ / Python / Rust private-runtime source level. The C++ runtime remains the visually inspected reference host for this slice, and the Python and Rust runtimes carry the same validated Example 24 Tree behavior. This status does not claim generalized runtime completeness beyond the validated Tree slice.
- Selecting a node patches front-panel state without executing the diagram.
- The Tree exposes one LabVIEW-like expand/collapse control per parent node; node icons are enabled from
.frognode icon enums and resolved through the Default Tree.wfrogitem-symbol SVG registry. - Optional checkboxes remain disabled in this example by
.frogdisplay properties. - Column headers are visible and fixed in this example; both visibility and fixed/scrolling posture are
.frogdisplay properties. - The source data deliberately includes more rows and columns than the viewport so vertical and horizontal scrollbars can be inspected.
Executeruns the manifest-backed nativeu16proof kernel.- The read-only Tree indicator updates its selected numeric node from the native execution result and its editable record display from the declared
frog.tree.recordsdiagram dataflow. - Node label, tag, value, item icon enum, visible items, selection, expansion, hierarchy lines, scrollbars, colors, border widths, font, and hit areas remain source/realization-owned.
- The SVG-backed shell can scale without bitmap pixelation, but each host must recompute overlays from published SVG parts and source-owned layout/style properties.
main.frog- source-owned Tree instances, hierarchy data, selection state, layout, bindings, and visual overrides.main.fir.json- FIR-facing value and UI binding summary.main.lowering.json- lowering intent toward the native manifest corridor.ui/tree_panel.wfrog- Example-local realization package that points to the Default Tree package, geometry SVG asset, and item-symbol SVG assets.../../Implementations/Reference/LLVM/examples/24_tree_node_selection_roundtrip/native_kernel_manifest.json- native kernel manifest consumed by the private runtime.