Reading pixel data from a drawable texture

At a glance

Project structure

Source bundle/
├── Application/
│   ├── AAPLViewController.m
│   ├── main.m
│   ├── WindowSceneDelegate.m
│   ├── AAPLAppDelegate.h
│   ├── AAPLViewController.h
│   └── AAPLAppDelegate.m
└── Renderer/
    ├── AAPLShaders.metal
    ├── AAPLRenderer.m
    └── AAPLShaderTypes.h

Structure observations

• The entry/composition boundary and renderer or operation boundary are separate in the source; AAPLRenderer is the principal feature coordinator.
• GPU-specific logic stays in Metal shader files; shared headers bridge host/shader layouts where present.
• The tree above is intentionally pruned to composition, resource, and shader files.

Overall architecture

flowchart LR
    N1["AAPLViewController"]
    N2["AAPLRenderer"]
    N3["drawable render and readback coordination"]
    N4["GPU-to-CPU pixel copy"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Application/AAPLViewController.m:137 — feature handoff or setup anchor

@implementation AAPLViewController
// ...
    AAPLImage *image = [_renderer renderAndReadPixelsFromView:_view
                                                   withRegion:readRegion];
// ...
@end

Interpretation

This is the dominant control/data path: platform code composes AAPLRenderer; that object controls drawable render and readback coordination; GPU-visible work ends in GPU-to-CPU pixel copy. The arrows summarize responsibility transfer, not a claim that every node directly calls the next.

Ownership and state

classDiagram
    AAPLViewController *-- AAPLRenderer : _renderer

Ownership evidence

Application/AAPLViewController.m:53 — AAPLViewController creates and stores _renderer

@implementation AAPLViewController
// ...
    _renderer = [[AAPLRenderer alloc] initWithMetalKitView:_view];
// ...
@end

Class and protocol design

Framework delegate conformance is a callback seam; the source does not justify calling the whole app protocol-oriented.

Access control

This sample does not use Swift private, fileprivate, or public for its native boundary. Objective-C/Objective-C++ use header versus implementation placement, C++ uses access specifiers/linkage, Python uses module conventions, and Metal entry points cross a compiled-library boundary; these are not Swift access levels.

Logic ownership and placement

Shader boundary reference

Renderer/AAPLShaders.metal:20 — representative GPU entry/helper

vertex RasterizerData

Design patterns

Naming conventions

• Role suffixes make ownership visible: AAPLViewController, AAPLRenderer, AAPLAppDelegate, WindowSceneDelegate.
• Method names describe setup or encoding actions: application, viewDidLoad, beginReadRegion, moveReadRegion, endReadRegion, viewDidAppear, acceptsFirstResponder.
• Shader entry points use stage/operation names: fragmentShader.
• AAPL is a sample namespace prefix, not a recommendation for production module naming; retain semantic suffixes such as Renderer, Manager, Scene, or Adapter.

Architecture takeaways

• Keep AAPLViewController focused on composition; AAPLRenderer is the owner of drawable render and readback coordination.
• Treat GPU-to-CPU pixel copy as a separate execution/compilation boundary with explicit resource and data-layout contracts.
• The verified ownership edge is AAPLViewController → _renderer; broader exclusive ownership is not inferred.
• Access-control rationale follows concrete language boundaries rather than translating every header or shader symbol into Swift terms.

Source map

• Official Apple documentation