- 16 2月, 2019 10 次提交
-
-
由 Stanislav Baranov 提交于
This reverts commit d48de7a3.
-
由 Chris Bracken 提交于
From build log: ``` ../../flutter/shell/platform/android/io/flutter/view/FlutterView.java:95: error: cannot find symbol private final LocalizationChannel localizationChannel; ^ symbol: class LocalizationChannel location: class FlutterView ../../flutter/shell/platform/android/io/flutter/view/FlutterView.java:172: error: cannot find symbol localizationChannel = new LocalizationChannel(dartExecutor); ^ symbol: class LocalizationChannel location: class FlutterView 2 errors ``` This reverts commit 256db4bc.
-
由 Chinmay Garde 提交于
The shell was already designed to cleanly shut down the VM but it couldnt earlier as |Dart_Initialize| could never be called after a |Dart_Cleanup|. This meant that shutting down an engine instance could not shut down the VM to save memory because newly created engines in the process after that point couldn't restart the VM. There can only be one VM running in a process at a time. This patch separate the previous DartVM object into one that references a running instance of the DartVM and a set of immutable dependencies that components can reference even as the VM is shutting down. Unit tests have been added to assert that non-overlapping engine launches use difference VM instances.
-
由 Matt Carroll 提交于
-
由 Todd Volkert 提交于
-
由 Amir Hardon 提交于
On Android we were never deleting the textures allocated for the texture registry, which resulted in a memory leak, see: https://github.com/flutter/flutter/issues/24145
-
由 najeira 提交于
-
由 najeira 提交于
-
由 Ben Konyi 提交于
Added `FlutterPluginRegistrantCallback` typedef and optional `setPluginRegistrantCallback` static method in `FlutterPlugin`. `setPluginRegistrantCallback` is used to set a callback defined in AppDelegate.m which registers some subset of plugins with a `FlutterPluginRegistry` (for example, a headless FlutterEngine). This allows for plugins which utilize background execution functionality to enable the use of other plugins on the background isolate. This puts iOS on par with Android for background execution. Along with updated examples and Medium posts, this fixes [flutter/flutter#21925](https://github.com/flutter/flutter/issues/21925).
-
由 Jason Simmons 提交于
Also extend the embedder unit tests to cover AOT execution
-
- 15 2月, 2019 1 次提交
-
-
由 Gary Qian 提交于
(Authored by @nathanrogersgoogle )
-
- 14 2月, 2019 1 次提交
-
-
由 nathanrogersgoogle 提交于
-
- 12 2月, 2019 4 次提交
-
-
由 Stanislav Baranov 提交于
-
由 Chinmay Garde 提交于
-
由 Matt Carroll 提交于
-
-
- 09 2月, 2019 6 次提交
-
-
由 KyleWong 提交于
Provide public api to allow FlutterEngine related context to be destoryed.
-
由 nathanrogersgoogle 提交于
If a frame is scheduled by the time the delayed animator notify idle task runs, then we should not call |NotifyIdle|. Also, add a trace event in the task, to make it more clear in traces when a notify idle call is coming from here (as opposed to |Animator::AwaitVSync|).
-
由 Chris Bracken 提交于
In 93452747 (#7642), //shell/platform/darwin:framework_shared was added without the root flutter config, causing a build breakage in Fuchsia, where flutter sits under //third_party/flutter as opposed to at the root. The flutter root config is required to set -I../../third_party as an include path.
-
由 Chinmay Garde 提交于
-
由 stuartmorgan 提交于
Avoids potential confusion due to the iOS framework already being called Flutter.framework.
-
由 Stanislav Baranov 提交于
* Dynamic patching support for AOT mode. * Cleanup.
-
- 08 2月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 07 2月, 2019 2 次提交
-
-
由 Matt Carroll 提交于
-
由 Chris Bracken 提交于
Allows embedders to specify a callback to be invoked in isolate scope once root isolate has been created and marked runnable. As an example of where this is useful, embedder unit test fixtures may want to include Dart functions backed by a native implementation. On isolate creation, this patch allows the unit test author to call Dart_SetNativeResolver in root isolate scope.
-
- 06 2月, 2019 1 次提交
-
-
由 liyuqian 提交于
This reverts commit 093b2fea. For https://github.com/flutter/flutter/issues/24058, We now only get a "Program linking failed" error message on Windows Android simulators without crahsing. Skia seems to have handled the linking failure in https://skia-review.googlesource.com/c/skia/+/180372 by rebuilding the program.
-
- 05 2月, 2019 2 次提交
-
-
由 Matt Carroll 提交于
-
由 Kaushik Iska 提交于
-
- 01 2月, 2019 1 次提交
-
-
由 stuartmorgan 提交于
Merges the current flutter-desktop-embedding macOS framework into the engine. Notable changes: - All channel/codec related code is eliminated in favor of using the existing iOS implementations. - All .m files renamed to .mm for consistency with the iOS code. - Some minor code changes to fix new warnings in Objective-C++ mode. - License headers, basic format (e.g., clang-format changes) updated to use repo style. - Xcode project is not included; instead adds GN build rules to create an integrated framework that combines what was the FDE library with what is present in FlutterEmbedder.framework. Other changes are left as follow-ups, including: - Moving shared code out of ios/ into common/. - Potentially improving sharing between iOS and macOS BUILD.gn. - Class renaming; the FLE prefix will be eliminated, but that API surface isn't stable yet, so that can be changed later.
-
- 31 1月, 2019 4 次提交
-
-
由 Chris Bracken 提交于
-
由 Kaushik Iska 提交于
- Moved versions from shell to common - versions singleton contains all the required versions.
-
由 Chinmay Garde 提交于
Document make_resource_current on FlutterOpenGLRendererConfig and warn if the callback is not set. (#7648)
-
由 Jason Simmons 提交于
Prior to this the Android embedder code would extract the icudtl.dat asset out of the APK and write it to local disk during the first startup of the app. This change will make that work unnecessary and eliminate the risk of ICU failures due to errors in the extraction process.
-
- 30 1月, 2019 1 次提交
-
-
由 stuartmorgan 提交于
FlutterResult is also the name of a class in the Objective-C API surface, which is problematic when building a framework that contains both (such as a macOS implementation of the Flutter framework).
-
- 29 1月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 25 1月, 2019 2 次提交
-
-
由 Chinmay Garde 提交于
-
由 Dan Field 提交于
-
- 24 1月, 2019 1 次提交
-
-
由 Qxyat 提交于
ForwardingGestureRecognizer was previously accepting the gesture when the touch sequence ended, this was causing some other gesture recognizers to not accept the gestures (e.g tapping on the my location button in a Google Map didn't work).
-
- 23 1月, 2019 2 次提交