Binding JSON data to TVML documents

At a glance

Project structure

Source bundle/
├── DataBindings/
│   ├── DataBindings/
│   │   ├── application.js
│   │   ├── AppDelegate.swift
│   │   └── Info.plist
│   ├── DataBindingsTests/
│   │   ├── DataBindingsTests.swift
│   │   └── Info.plist
│   ├── DataBindingsUITests/
│   │   ├── DataBindingsUITests.swift
│   │   └── Info.plist
│   └── DataBindings.xcodeproj/
│       ├── .xcodesamplecode.plist
│       └── project.pbxproj
└── Configuration/
    └── SampleCode.xcconfig

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: JavaScript, Swift.
• The verified tree contains 6 project/configuration file(s) and 3 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["TVMLKit APIs"]
    N1 --> N2

Reference code

DataBindings/DataBindings/AppDelegate.swift:11 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, TVApplicationControllerDelegate {
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into TVMLKit JS.

Ownership and state

classDiagram
    application *-- XMLHttpRequest : xhr
    application *-- XMLHttpRequest : templateXHR
    application *-- DataItem : objectItem
    AppDelegate o-- UIWindow : window

Ownership evidence

DataBindings/DataBindings/application.js:11 — stored dependency or nearest verified ownership anchor

    var xhr = new XMLHttpRequest();
    xhr.onreadystatechange = function () {
        if (this.readyState == 4 && this.status == 200) {
            getJson(jsonURL, xhr.responseXML);
        }
    }
    xhr.open("GET", url, false);

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

DataBindings/DataBindings/AppDelegate.swift:12 — representative type boundary

class AppDelegate: UIResponder, UIApplicationDelegate, TVApplicationControllerDelegate {
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

DataBindings/DataBindings/AppDelegate.swift:12 — representative boundary

class AppDelegate: UIResponder, UIApplicationDelegate, TVApplicationControllerDelegate {
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Delegate: AppDelegate.
• Protocols: no local protocol declaration in the scanned source.
• Methods: getTemplate, getJson, insertJson, loadTemplate, pushDoc, executeRemoteMethod, application, applicationWillResignActive.
• Files: DataBindings/DataBindings/AppDelegate.swift, DataBindings/DataBindingsTests/DataBindingsTests.swift, DataBindings/DataBindingsUITests/DataBindingsUITests.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches DataBindings, TVMLKit, UIKit through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation