The library documents itself · Graphics

stzFrameGraph

16 own methods · 1 forms written with extensions, listed under their method

the source: base/graphics/stzFrameGraph.ring(opens in a new tab) · All classes · The area reference: Graphics

Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean

Examples: 0 come from the library's tests; 3 were composed from each method's signature and run for this page, on a fresh object, for example o1 = new stzFrameGraph(256, 256). 13 methods have none yet. Examples run on 2026-10-03 12:54 inside the library at commit 0e72e2e2c.

Method

Explanation, as the source carries it

init

(no comment in the source: the name reads as a sentence) initno extension

AddPass

declaring the frame ------------------------------------------------- paSpec: [ :Reads = [...], :Writes = [...], :Body = func ] The BODY is what actually draws; the graph only decides when it runs and what it draws into.QCSXTZZZIBWU

PassCount

(no comment in the source: the name reads as a sentence) pass count

composed example

o1 = new stzFrameGraph(256, 256)
? o1.PassCount()
#--> 0

composed from the signature, run for this page

no extension

ResourceCount

(no comment in the source: the name reads as a sentence) resource count

composed example

o1 = new stzFrameGraph(256, 256)
? o1.ResourceCount()
#--> 0

composed from the signature, run for this page

no extension

Compile

compiling ----------------------------------------------------------- Derive the order, the lifetimes and the aliasing, and PROVE the properties. Everything below is computed from the declaration; nothing here is a number somebody typed.no extension

Order

(no comment in the source: the name reads as a sentence) orderno extension

Lifetimes

(no comment in the source: the name reads as a sentence) lifetimesno extension

Aliasing

[ logical, physicalSlot ] -- two logicals sharing a slot never overlapno extension

PhysicalTargets

(no comment in the source: the name reads as a sentence) physical targetsno extension

TargetsSaved

What the schedule SAVED over giving every resource its own target. This is the number the kill criterion asks for.no extension

Findings

the proofs ---------------------------------------------------------- The house finding shape, so a frame graph is judged by the SAME gate as code rules and security rules: [ :rule, :subject, :where, :severity, :message ].no extension

IsSound

SOUND IS NO ERROR, and StzFindingsAreSound is the house's one answer to it -- the same one stzRuleReport, stzGraphRuleSet, stzPlasticGovernance and the picture domains give. This wrote its own loop over position 4 until 2026-09-12.no extension

Report

(no comment in the source: the name reads as a sentence) reportno extension

Execute

Each body is called as fBody(oFrameGraph, cPassName). It asks the graph which physical target its writes landed on.no extension

TargetOf

The physical target a logical resource lives on, for a pass body to draw into or sample.

composed example

o1 = new stzFrameGraph(256, 256)
? o1.TargetOf("a")
#--> 0

composed from the signature, run for this page

no extension

FreeTargets

(no comment in the source: the name reads as a sentence) free targetsno extension