文件最后提交记录最后更新时间
[various] Align Flutter and Dart SDK constraints (#3349) As described in https://github.com/flutter/flutter/issues/121684, we currently have inconsistencies between Flutter SDK constraints and Dart SDK constraints; we have often updated only the former. This PR: 1. Adds CI enforcement via the repo tooling that the minimum versions are consistent. 2. Adds a new repo tooling command to update SDK constraints, to help mass-fix all the violations of the new enforcement in step 1 (and for future mass changes, such as when we update our test matrix and mass-drop support for versions that are no longe tested). - In all cases, the looser constraint was updated to match the more restrictive constraint, such that there's no actual change in what Flutter version any package actually supports. 3. Runs dart fix --apply over all changed packages to automatically fix all of the analysis failures caused by step 2 suddenly making all of our packages able to use super parameters. Fixes https://github.com/flutter/flutter/issues/121684 Fixes https://github.com/flutter/flutter/issues/1216853 年前
Update boilerplate (#1973) * Update boilerplate * trigger checks * trigger checks3 年前
[rfw] Add some more documentation for RFW (#4349) 2 年前
[various] Add Swift Package Manager integration to example apps (#8219) This migrates various example apps to have Swift Package Manager integration. This raises the example apps' Flutter SDK requirement to 3.24.0 or higher. I will get a text exemption for this change. The example apps were migrated using the following commands: ``` dart run script/tool/bin/flutter_plugin_tools.dart build-examples --ios --swift-package-manager dart run script/tool/bin/flutter_plugin_tools.dart build-examples --macos --swift-package-manager ``` ⚠️ The following plugins' example apps are **not* included in this change as their migration included non-SPM changes that require closer review: 1. google_sign_in 1. google_sign_in_ios 1. image_picker 1. image_picker_ios 1. image_picker_macos 1. pigeon Part of: https://github.com/flutter/flutter/issues/1591731 年前
[various] Commit Windows build migrations (#6175) Commits the changes caused by building all examples for Windows with a recent version of Flutter, to minimize noise in CI logs and local builds. All changes are entirely tool-generated.2 年前
[rfw] Remote Flutter Widgets package (#452) 4 年前
[rfw] Remote Flutter Widgets package (#452) 4 年前
[rfw] Remote Flutter Widgets package (#452) 4 年前
[rfw] Remote Flutter Widgets package (#452) 4 年前
Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).1 年前
README.md

Example of using Wasm with RFW

In this example, the application downloads both RFW descriptions of UI and Wasm logic to drive it. The Flutter application itself does not contain any of the calculator UI or logic.

Currently this only runs on macOS, Windows, and Linux, since package:wasm does not yet support Android, iOS, or web.

Building

Before running this package, you must run flutter pub run wasm:setup in this directory. Before doing this, you will need to have installed Rust and clang.

To rebuild the files in the logic/ directory (which are the files that the application downloads at runtime), you will additionally need to have installed clang and lld, and dart must be on your path.

Conventions

The application renders the remote widget named root defined in the logic/calculator.rfw file, and loads the Wasm module defined in the logic/calculator.wasm file.

The Wasm module must implement a function value that takes no arguments and returns an integer, which is the data to pass to the interface. This will be the first function called.

That data is stored in the value key of the data exposed to the remote widgets, as a map with two values, numeric (which stores the integer as-is) and string (which stores its string representation, e.g. for display using a Text widget).

The remote widgets can signal events. The names of such events are looked up as functions in the Wasm module. The arguments key, if present, must be a list of integers to pass to the function.

Only the core.widgets local library is loaded into the runtime.

Application behavior

The demo application fetches the RFW and Wasm files on startup, if it has not downloaded them before or if they were downloaded more than six hours earlier.