Teek API Documentation

Walks a Document and realizes it into a live Teek::App - two passes:

  1. create - creates every widget, allocates a hierarchical/meaningful Tk path per node, fills each node’s realized slot.
  2. link - applies (placeholder, see below) geometry and wires event bindings, resolving target: references by name. Runs after create has finished the WHOLE tree, so a target declared later in the build already has a live path by the time it’s looked up - that ordering is what makes forward references work.

Every widget creation and mutation goes through Teek::App#command, so teek’s interceptor/leak-cleanup layer applies automatically.

Inherits: Object

Instance Methods

initialize(app, document, default_scroll: nil)

Parameters

Returns Realizer — a new instance of Realizer

@api private

realize

Returns void

realize_subtree(node, parent_node)

Realize a single already-built (but not-yet-realized) node - and its descendants - into an already-running app, scoped under a parent that’s realized already. Reuses the exact same create/link machinery #realize uses for the initial tree, just entered at an arbitrary node instead of the document root - see Session#add.

Parameters
  • node Node — freshly built, not yet realized
  • parent_node Node — already realized - node becomes its child

Returns void