2d623278e7
This moves the app template more toward being a more generic starting point for any Flutter application, eliminating some hard-code assumptions about there being a single window/engine pair that is directly bound to the life of the application: - Moves the runloop into its own class, making it capable of servicing any number of engine instances. - Moves the logic for setting up a window containing only a Flutter view into a window subclass for ease of re-use. - Makes quit-on-window-close an optional property. (Long term this should be even more generic, like a quit-when-last-window-closes option, but this is a short-term improvement that removes the binding between the runloop and the window). - Allows for multiple instances of Win32Window to exist without issues relating to the window class registration. Since there are getting to be a non-trivial number of files associated with the runner, this moves the source into a runner/ directory, as is already done on some other platforms. Note that creating multiple Flutter windows at the same time still doesn't work correctly even with this change, but this addresses some of the known issues, and makes it easier to test in the future (e.g., for debugging engine-level issues with multiple instances). Fixes #45397
Samples Catalog
A collection of sample apps that demonstrate how Flutter can be used.
Each sample app is contained in a single .dart file located in the lib
directory. To run each sample app, specify the corresponding file on the
flutter run command line, for example:
flutter run lib/animated_list.dart
flutter run lib/app_bar_bottom.dart
flutter run lib/basic_app_bar.dart
...
The apps are intended to be short and easily understood. Classes that represent the sample's focus are at the top of the file; data and support classes follow.
Each sample app contains a comment (usually at the end) which provides some standard documentation that also appears in the web view of the catalog. See the "Generating..." section below.
Generating the web view of the catalog
Markdown and a screenshot of each app are produced by bin/sample_page.dart
and saved in the .generated directory. The markdown file contains
the text taken from the Sample Catalog comment found in the app's source
file, followed by the source code itself.
This sample_page.dart command line app must be run from the examples/catalog
directory. It relies on templates also found in the bin directory, and it
generates and executes test_driver apps to collect the screenshots:
cd examples/catalog
dart bin/sample_page.dart