mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() 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 |
||
---|---|---|
.. | ||
ios | ||
lib | ||
test_driver | ||
pubspec.yaml | ||
README.md |
Example of calling platform services from Flutter
This project demonstrates how to connect a Flutter app to platform specific services on iOS using Swift. The equivalent version of this project in Objective C is found in examples/platform_channel.
You can read more about accessing platform and third-party services in Flutter.
iOS
You can use the commands flutter build
and flutter run
from the app's root
directory to build/run the app or you can open ios/Runner.xcworkspace
in Xcode
and build/run the project as usual.
Android
We refer to the platform_channel project.