tom_d4rt_flutter_ast_test

Analyzer-free D4rt Flutter demo. A sample browser that loads **pre-compiled `AstBundle` JSON** from assets and renders each one through [`FlutterD4rt`](../tom_d4rt_flutter_ast) — the zero-analyzer, web-safe runtime.

This is the AST-runtime counterpart to `tom_d4rt_flutter_test` (which compiles `.dart` source on the device via the analyzer). The whole point here is **independence from the analyzer and `dart:io`**: the shipped app depends only on `tom_d4rt_flutter_ast` + `tom_d4rt_ast`, so it builds and runs on the web.

How it works

example/<name>/main.dart  ──(build time)──▶  assets/bundles/<name>.json
        (Dart source)         AstBundler            (AstBundle JSON)

assets/bundles/<name>.json ──(on device)──▶  AstBundle.fromJson ──▶ FlutterD4rt.build ──▶ Widget

• **Build time** — `tool/compile_samples_to_bundles.dart` parses each sample

with the analyzer (`tom_ast_generator`'s `AstBundler`), skipping the Flutter libraries that are bridged at runtime, and writes a serialized `AstBundle` per sample. It runs under `flutter test` because it needs `dart:ui` (to read `FlutterD4rt.interpreter.bridgedLibraryUris`) and `dart:io` (to write files) — neither of which ships in the runtime app. - **Runtime** — `lib/` loads the bundle JSON via `rootBundle`, reconstructs it with `AstBundle.fromJson`, and renders it with `FlutterD4rt.build<Widget>` — analyzer-free, `dart:io`-free, web-safe.

Usage

Recompile bundles after adding or editing any sample:

flutter test tool/compile_samples_to_bundles.dart

Run on a target:

./run_web.sh      # Chrome — the headline web-safety target
./run_macos.sh    # native macOS desktop
./run_ipad.sh     # iPad simulator
./run_iphone.sh   # iPhone simulator
./run_simulator.sh <udid>   # a specific iOS simulator

Each `run_*.sh` recompiles the bundles first, then launches the app.

Samples

Sample sources live in `example/<name>/`. Each is a normal multi-file D4rt program whose entry point `main.dart` exposes a top-level `Widget build(BuildContext context)`. Relative imports are followed and inlined into the bundle; bridged `package:flutter/*` imports are left for the runtime to resolve natively.

This project ships **33** AST-bundle samples — the shared subset of the canonical raw-source corpus in [`tom_d4rt_flutter_test`](../tom_d4rt_flutter_test) (37 samples). The same 33 programs run app-for-app on both runtimes, so the source-based and bundle-based paths can be compared directly.

The **4 samples that are source-only by design** — `profiler_field`, `profiler_life`, `particle_field_optimized`, `conway_life_optimized` — are **not** compiled to bundles here. The two `profiler_*` apps are self-running diagnostics for the source-interpreted render path, and the two `*_optimized` apps are GC-mitigation demos whose unoptimized twins (`particle_field`, `conway_life`) are already in this corpus. See the [`tom_d4rt_flutter_test` README "Sample corpus" section](../tom_d4rt_flutter_test/README.md#sample-corpus) for the per-sample rationale. The compiler (`tool/compile_samples_to_bundles.dart`) auto-discovers every `example/<name>/main.dart`, so this exclusion is enforced simply by **not** copying those four directories into this project's `example/`.

Layout

Path	Role
`lib/main.dart`	Sample-browser shell (grid → render page)
`lib/src/bundle_source.dart`	Loads the manifest + bundle JSON from assets
`lib/src/bundle_app_page.dart`	Renders one bundle via `FlutterD4rt`
`tool/compile_samples_to_bundles.dart`	Build-time source→`AstBundle` compiler
`example/<name>/`	Sample D4rt programs
`assets/bundles/`	Generated bundle JSON + `index.json` manifest
`test/render_bundle_test.dart`	Smoke test: a bundle deserializes and renders