mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() * Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs |
||
---|---|---|
.. | ||
flutterapp | ||
ios_add2app | ||
ios_add2app.xcodeproj | ||
ios_add2app.xcworkspace | ||
ios_add2appTests | ||
.gitignore | ||
build_and_test.sh | ||
Podfile | ||
README.md |
iOS Add2App Test
This application demonstrates some basic functionality for Add2App, along with a native iOS ViewController as a baseline and to demonstrate interaction.
The following functionality is currently implemented:
- A regular iOS view controller (UIViewController), similar to the default
flutter create
template (NativeViewController.m). - A FlutterViewController subclass that takes over full screen. Demos showing this both from a cold/fresh engine state and a warm engine state (FullScreenViewController.m).
- A demo of pushing a FlutterViewController on as a child view.
- A demo of showing both the native and the Flutter views using a platform channel to to interact with each other (HybridViewController.m).
- A demo of showing two FlutterViewControllers simultaneously (DualViewController.m).
A few key things are tested here (IntegrationTests.m):
- The ability to pre-warm the engine and attach/detatch a ViewController from it.
- The ability to use platform channels to communicate between views.
- The ability to simultaneously run two instances of the engine.
- That a FlutterViewController can be freed when no longer in use (also tested from FlutterViewControllerTests.m).
- That a FlutterEngine can be freed when no longer in use.