[rfw] Remove the RFW WASM example

customer_testing.sh

@@ -29,7 +29,6 @@ pushd packages/rfw
 
 # Update the subpackages so that the analysis doesn't get confused.
 pushd example/remote; flutter packages get; popd
-pushd example/wasm; flutter packages get; popd
 pushd test_coverage; dart pub get; popd
 
 flutter analyze --no-fatal-infos

packages/rfw/CHANGELOG.md

@@ -1,6 +1,7 @@
 ## NEXT
 
 * Updates minimum supported SDK version to Flutter 3.27/Dart 3.6.
+* Removes the wasm example.
 
 ## 1.0.31
 

packages/rfw/README.md

@@ -582,11 +582,9 @@ The last kind of argument that widgets can have is callbacks.
 
 Since remote widget libraries are declarative and not code, they
 cannot represent executable closures. Instead, they are represented as
-events. For example, here is how the "7" button from the
-[calculator example](https://github.com/flutter/packages/blob/main/packages/rfw/example/wasm/logic/calculator.rfwtxt)
-is represented:
+events. For example:
 
-<?code-excerpt "example/wasm/logic/calculator.rfwtxt (button7)"?>
+<?code-excerpt "test/readme_test.dart (button7)"?>
 ```rfwtxt
 CalculatorButton(label: "7", onPressed: event "digit" { arguments: [7] }),
 ```
@@ -600,7 +598,7 @@ In that example, `CalculatorButton` is itself a remote widget that is
 defined in terms of a `Button`, and the `onPressed` argument
 is passed to the `onPressed` of the `Button`, like this:
 
-<?code-excerpt "example/wasm/logic/calculator.rfwtxt (CalculatorButton)"?>
+<?code-excerpt "test/readme_test.dart (CalculatorButton)"?>
 ```rfwtxt
 widget CalculatorButton = Padding(
   padding: [8.0],
@@ -762,8 +760,8 @@ by calling
 [`encodeLibraryBlob`](https://pub.dev/documentation/rfw/latest/formats/encodeLibraryBlob.html)
 on the results of calling `parseLibraryFile`.
 
-The example in `example/wasm` has some [elaborate remote
-widgets](https://github.com/flutter/packages/blob/main/packages/rfw/example/wasm/logic/calculator.rfwtxt),
+The example in `example/remote` has some [elaborate remote
+widgets](https://github.com/flutter/packages/blob/main/packages/rfw/example/remote/remote_widget_libraries/counter_app2.rfwtxt),
 including some that manipulate state (`Button`).
 
 #### State
@@ -773,12 +771,12 @@ Buttons must react immediately (in milliseconds) and cannot wait for
 logic that's possibly running on a remote server (maybe many hundreds
 of milliseconds away).
 
-The aforementioned `Button` widget in the `wasm` example tracks a
-local "down" state, manipulates it in reaction to
+The aforementioned `Button` widget in the `remote_widget_libraries` example
+tracks a local "down" state, manipulates it in reaction to
 `onTapDown`/`onTapUp` events, and changes the shadow and margins of
 the button based on its state:
 
-<?code-excerpt "example/wasm/logic/calculator.rfwtxt (Button)"?>
+<?code-excerpt "example/remote/remote_widget_libraries/counter_app2.rfwtxt (Button)"?>
 ```rfwtxt
 widget Button { down: false } = GestureDetector(
   onTap: args.onPressed,

packages/rfw/example/README.md

@@ -8,6 +8,3 @@ There are several examples.
 
 * `remote` is a proof-of-concept showing files being obtained from a
   remote server and rendered by the application at runtime.
-
-* `wasm` shows how package:rfw can be combined with package:wasm to
-  configure logic as well as the user interface at runtime.

packages/rfw/example/remote/remote_widget_libraries/counter_app2.rfwtxt

@@ -17,6 +17,7 @@ widget Counter = Container(
   ),
 );
 
+// #docregion Button
 widget Button { down: false } = GestureDetector(
   onTap: args.onPressed,
   onTapDown: set state.down = true,
@@ -57,3 +58,4 @@ widget Button { down: false } = GestureDetector(
     ),
   ),
 );
+// #enddocregion Button