|author||dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>||Tue Oct 04 18:32:47 2022 +0100|
|committer||GitHub <email@example.com>||Tue Oct 04 18:32:47 2022 +0100|
Bump actions/setup-node from 3.4.1 to 3.5.0 (#796) Bumps [actions/setup-node](https://github.com/actions/setup-node) from 3.4.1 to 3.5.0. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](https://github.com/actions/setup-node/compare/2fddd8803e2f5c9604345a0b591c3020ee971a93...969bd2663942d722d85b6a8626225850c2f7be4b) --- updated-dependencies: - dependency-name: actions/setup-node dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <firstname.lastname@example.org> Signed-off-by: dependabot[bot] <email@example.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Flutter Gallery is a resource to help developers evaluate and use Flutter. It is a collection of Material Design & Cupertino widgets, behaviors, and vignettes implemented with Flutter. We often get asked how one can see Flutter in action, and this gallery demonstrates what Flutter provides and how it behaves in the wild.
cupertino, and other widgets
Flutter Gallery has been built to support multiple platforms. These include:
One can run the gallery locally for any of these platforms. For desktop platforms, please see the Flutter docs for the latest requirements.
cd gallery/ flutter pub get flutter run
The Flutter Gallery targets Flutter‘s
master channel. As such, it can take advantage of new SDK features that haven’t landed in the stable channel.
If you'd like to run the Flutter Gallery, you may have to switch to the
master channel first:
flutter channel master flutter upgrade
When you're done, use this command to return to the safety of the
flutter channel stable flutter upgrade
If this is the first time building the Flutter Gallery, the localized code will not be present in the project directory. However, after running the application for the first time, a synthetic package will be generated containing the app's localizations through importing
flutter pub get flutter pub run grinder l10n
See separate README for more details.
flutter pub get flutter pub run grinder update-code-segments
See separate README for more details.
Convert your animation to a
.gif file. Ideally, use a background color of
0xFF030303 to ensure the animation blends into the background of the app.
Add your new
.gif file to the assets directory under
assets/splash_effects. Ensure the name follows the format
splash_effect_$num.gif. The number should be the next number after the current largest number in the repository.
Update the map
_effectDurations in splash.dart to include the number of the new
.gif as well as its estimated duration. The duration is used to determine how long to display the splash animation at launch.
The process is largely automated and easy to set in motion.
First things first, bump the
pubspec.yaml version number. This can be in a PR making a change or a separate PR. Use semantic versioning to determine which part to increment. The version number after the
+ should also be incremented. For example
1.2.3+010203 with a patch should become
Then, use the following workflows. It is strongly recommended to use the staging/beta environments when available, before deploying to production.
Note Once an .aab is released with a particular version number, it can't be replaced. The version number must be incremented again.
Note The release draft is private until published. Upon being published, the specified version tag will be created.
For posterity, information about doing these things locally is available at go/flutter-gallery-manual-deployment.
The gallery has its own set of unit, golden, and integration tests.
In addition, Flutter itself uses the gallery in tests. To enable breaking changes, the gallery version is pinned in two places: