- 20 7月, 2018 1 次提交
-
-
由 Jonah Williams 提交于
-
- 19 7月, 2018 3 次提交
-
-
由 Stanislav Baranov 提交于
-
由 Jonah Williams 提交于
-
由 amirh 提交于
-
- 18 7月, 2018 1 次提交
-
-
由 Jonah Williams 提交于
-
- 17 7月, 2018 3 次提交
-
-
由 Michael Goderbauer 提交于
-
-
由 Jonah Williams 提交于
-
- 14 7月, 2018 6 次提交
-
-
由 Jonah Williams 提交于
-
由 Jonah Williams 提交于
Reverts flutter/engine#5740
-
由 amirh 提交于
Each platform view created (by a plugin supplied factory) is attached to a virtual display. The virtual displays are controlled by VirtualDisplayController objects. The PlatformViewsController maintains a mapping from a platform view's id to its VirtualDisplayController, which allows it to operate on the virtual display for a given platform view ID when asked so over the method channel. This is using API level 20 APIs, on lower API levels all platform views method channel calls are noops. We can make this work on API 19 with some refactoring to the TextureRegistry (allow the engine Java code to recycle a texture entry id). This CL also adds a platform view id parameter to the PlatformViewFactory#create() method. This allows plugins to route platform channel messages to specific instances of a platform view. TBD in future CLs: * Forward touch events to the platform views. * Support accessibility for platform views. flutter/flutter#19030
-
由 Jonah Williams 提交于
-
由 Ben Konyi 提交于
-
由 amirh 提交于
-
- 12 7月, 2018 3 次提交
-
-
由 Jonah Williams 提交于
-
由 amirh 提交于
To keep the scope of this CL as small of possible I'm leaving the actual implementation of the platform view mechanics to a following CL. This CL introduces: * A PlatformViewsController class which will be responsible for creating, resizing, and disposing platform views. * A PlatformViewRegistry which is exposed through the PluginRegistry and allows plugins to register factories for platform views. Android plugin code will add support for a new platform view type by implementing PlatformViewFactory, and registering a factory with the registry, e.g: ```java registrar.platformViewRegistry().registerViewFactory( 'webview', new FlutterWebViewFactory() ); ``` On the Dart side, the framework will ask the engine to create new platform views by sending a create message over the platformviews method channel with the unique platform view type id, dimensions, and a unique id allocated by the framework for the new platform view instance. The platformviews method channel is also used for resizing and disposing platform views.
-
由 Jonah Williams 提交于
-
- 11 7月, 2018 1 次提交
-
-
由 Jonah Williams 提交于
-
- 10 7月, 2018 2 次提交
-
-
由 Jonah Williams 提交于
-
由 Jonah Williams 提交于
-
- 04 7月, 2018 3 次提交
-
-
由 Jonah Williams 提交于
-
由 Jason Simmons 提交于
Do not make an extra submit callback during SurfaceFrame destruction if the frame was already submitted (#5669)
-
由 amirh 提交于
-
- 02 7月, 2018 1 次提交
-
-
由 matthew-carroll 提交于
* Support all keyboard actions. (#11344)
-
- 29 6月, 2018 1 次提交
-
-
由 Jonah Williams 提交于
-
- 28 6月, 2018 1 次提交
-
-
由 Jason Simmons 提交于
These functions were made obsolete by the engine refactoring (https://github.com/flutter/engine/commit/6baff4c821350bbcb64e7d029574b567f3801a1a)
-
- 26 6月, 2018 2 次提交
-
-
由 Jason Simmons 提交于
-
由 Chinmay Garde 提交于
Part of fixing https://bugs.chromium.org/p/skia/issues/detail?id=7741
-
- 21 6月, 2018 2 次提交
-
-
由 Sigurd Meldgaard 提交于
-
由 Jason Simmons 提交于
Required by the Fuchsia embedder
-
- 20 6月, 2018 3 次提交
-
-
-
由 Ryan Macnak 提交于
Toward no-copy loading of kernel.
-
由 Chinmay Garde 提交于
-
- 19 6月, 2018 1 次提交
-
-
由 Chinmay Garde 提交于
This accounts for changes made in https://github.com/flutter/engine/pull/5556
-
- 16 6月, 2018 2 次提交
-
-
由 Ian Hickson 提交于
These are making some of the tests that are sensitive to output flakey.
-
由 Maurice Parrish 提交于
-
- 15 6月, 2018 1 次提交
-
-
由 Jason Simmons 提交于
Previously the engine would load all embedded fonts listed in the app's font manifest during startup. This change creates a Skia font manager that is backed by the engine's AssetManager and can load embedded font assets on demand.
-
- 14 6月, 2018 2 次提交
-
-
由 Jason Simmons 提交于
-
由 Ben Konyi 提交于
* Reland "Added IsolateNameServer functionality (#5410)" This reverts commit c3976b3c. * Fixed issue with isolate_name_server_test which caused test to timeout * Disabled thread_annotations on Android as they aren't supported in the NDK headers for std::mutex. Readded thread annotations to IsolateNameServer.
-
- 13 6月, 2018 1 次提交
-