- 27 8月, 2019 1 次提交
-
-
由 Amir Hardon 提交于
This change sets up a "spying canvas" to try and detect empty canvases. When using platform views with a custom embedder, if a platform view overlay canvas is known to be empty we skip creating a compositor layer for that overlay.
-
- 24 8月, 2019 2 次提交
-
-
由 Chinmay Garde 提交于
Uses the same technique used during OpenGL composition to elide root surface access. The refactoring of this approach is tracked in https://github.com/flutter/flutter/issues/38466 Fixes https://github.com/flutter/flutter/issues/39009.
-
由 Chinmay Garde 提交于
We will end up creating fewer threads in tests.
-
- 23 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 22 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
No functional change. Just makes testing with fixture images easier. Adding a whole lot more tests that use this path for the embedder surface rotation patches. Want to land stuff in smaller chunks.
-
- 21 8月, 2019 2 次提交
-
-
由 Chinmay Garde 提交于
The root canvas is managed by the external view embedder when using a custom compositor. Due to this, frame submission on the surface will not end up flushing the same (because the surface doesn’t have it to begin with). Fixed with tests.
-
由 Jason Simmons 提交于
This test queues tasks to a custom task runner that runs the tasks on the platform thread. After shutting down the engine, the test must wait until these tasks are drained before the test exits.
-
- 20 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
This issue would only manifest when a custom task runner was being used with a custom compositor. Both were tested separately but not together. A new test has been added for this. We still create the GPU thread merger unnecessarily but I can patch that later. I also cleaned up the existing custom task runner test to not submit tasks on a dead engine as they just log errors unnecessarily. Filed new: https://github.com/flutter/flutter/issues/38844
-
- 14 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
This patch allows embedders to split the Flutter layer tree into multiple chunks. These chunks are meant to be composed one on top of another. This gives embedders a chance to interleave their own contents between these chunks. The Flutter embedder API already provides hooks for the specification of textures for the Flutter engine to compose within its own hierarchy (for camera feeds, video, etc..). However, not all embedders can render the contents of such sources into textures the Flutter engine can accept. Moreover, this composition model may have overheads that are non-trivial for certain use cases. In such cases, the embedder may choose to specify multiple render target for Flutter to render into instead of just one. The use of this API allows embedders to perform composition very similar to the iOS embedder. This composition model is used on that platform for the embedding of UIKit view such and web view and map views within the Flutter hierarchy. However, do note that iOS also has threading configurations that are currently not available to custom embedders. The embedder API updates in this patch are ABI stable and existing embedders will continue to work are normal. For embedders that want to enable this composition mode, the API is designed to make it easy to opt into the same in an incremental manner. Rendering of contents into the “root” rendering surface remains unchanged. However, now the application can push “platform views” via a scene builder. These platform views need to handled by a FlutterCompositor specified in a new field at the end of the FlutterProjectArgs struct. When a new platform view in introduced within the layer tree, the compositor will ask the embedder to create a new render target for that platform view. Render targets can currently be OpenGL framebuffers, OpenGL textures or software buffers. The type of the render target returned by the embedder must be compatible with the root render surface. That is, if the root render surface is an OpenGL framebuffer, the render target for each platform view must either be a texture or a framebuffer in the same OpenGL context. New render target types as well as root renderers for newer APIs like Metal & Vulkan can and will be added in the future. The addition of these APIs will be done in an ABI & API stable manner. As Flutter renders frames, it gives the embedder a callback with information about the position of the various platform views in the effective hierarchy. The embedder is then meant to put the contents of the render targets that it setup and had previously given to the engine onto the screen (of course interleaving the contents of the platform views). Unit-tests have been added that test not only the structure and properties of layer hierarchy given to the compositor, but also the contents of the texels rendered by a test compositor using both the OpenGL and software rendering backends. Fixes b/132812775 Fixes flutter/flutter#35410
-
- 09 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 07 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
This exposes the `Settings::leak_vm` flag to custom embedders. All embedder unit-tests now shut down the VM on the shutdown of the last engine in the process. The mechanics of VM shutdown are already tested in the Shell unit-tests harness in the DartLifecycleUnittests set of of assertions. This just exposes that functionality to custom embedders. Since it is part of the public stable API, I also switched the name of the field to be something less snarky than the field in private shell settings.
-
- 17 7月, 2019 1 次提交
-
-
由 Pierre Champion 提交于
-
- 07 7月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 04 7月, 2019 1 次提交
-
-
- 18 6月, 2019 1 次提交
-
-
由 Jason Simmons 提交于
Applications can use an embedder API to obtain the isolate ID and then use it in calls to the Dart service protocol.
-
- 13 6月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
Currently, all our host unit-tests that have rendering concerns use the software backend because of OpenGL ES availability and stability issues on the various platforms where we run host tests. Unfortunately, entire subsystems are disabled (and not tested) when rendering with the software backend. This patch pulls in SwiftShader and via pending patches in the buildroot, configures the host unit-tests to optionally use OpenGL ES in a stable manner without relying on the OpenGL drivers being present (and functional). I have wired up the embedder test fixture in this patch to use the SwiftShader based OpenGL ES driver. I will update the shell and runtime unittests in a subsequent patch as well. The on and offscreen surfaces are configured as 1x1 pbuffer surface because we should be able to write pixel tests using OpenGL directly wihout having to deal with surfaces.
-
- 26 5月, 2019 1 次提交
-
-
由 Chris Bracken 提交于
Corects a bnuch of typeos throughout teh engien codebsae. Also makes a couple minor Commonwealth -> US spelling adjustments for consistency with the rest of Flutter's codebase. Made use of `misspell` tool: https://github.com/client9/misspell
-
- 10 4月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 29 3月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 28 3月, 2019 2 次提交
-
-
由 Chinmay Garde 提交于
Currently, all Flutter threads are managed by the engine itself. This works for all threads except the platform thread. On this thread, the engine cannot see the underlying event multiplexing mechanism. Using the new task runner interfaces, the engine can relinquish the task of setting up the event multiplexing mechanism and instead have the embedder provide one for it during setup. This scheme is only wired up for the platform thread. But, the eventual goal is to expose this message loop interoperability for all threads.
-
由 Chinmay Garde 提交于
This reverts commit 7e77d5c4 after fixing Windows issues.
-
- 27 3月, 2019 3 次提交
-
-
由 Chinmay Garde 提交于
Revert "Allow specification of std::functions as native entrypoints from Dart code. (#8309)" (#8312) This reverts commit 400a86a6.
-
由 Chinmay Garde 提交于
This allows for the specification of std::functions (using EmbedderContext::NativeEntry) with their captures as native entrypoints. Earlier, only C functions we allowed which meant that there were no captures and assertions had to use globals which could introduce bugs when used with gtest_repeat.
-
由 Chinmay Garde 提交于
-
- 26 3月, 2019 2 次提交
-
-
由 Chinmay Garde 提交于
Also allows tests to specify their own embedder contexts.
-
由 Chinmay Garde 提交于
All embedder unit-tests have to setup the Flutter project arguments from scratch before launching the engine. The boilerplate and having to deal with the low level C API during each engine launch is a hinderance to writing tests. This patch introduces an EmbedderTest fixture that sets up all the embedder side snapshots before allowing the unit test to create a FlutterConfigBuilder` that the test can use to incrementally build and edit the Flutter project configuration. From the given state state of a configuration, multiple engines can be launched with their lifecylces managed by appropriate RAII wrappers. This allows the a fully configured Flutter engine to be launched using 4 lines of code in a fixture. ``` EmbedderConfigBuilder builder; builder.SetSoftwareRendererConfig(); builder.SetAssetsPathFromFixture(this); builder.SetSnapshotsFromFixture(this); auto engine = builder.LaunchEngine(); ```
-
- 16 2月, 2019 1 次提交
-
-
由 Jason Simmons 提交于
Also extend the embedder unit tests to cover AOT execution
-
- 07 2月, 2019 1 次提交
-
-
由 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.
-
- 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).
-
- 17 1月, 2019 1 次提交
-
-
由 Chris Bracken 提交于
As of Dart 2, running from Dart source is no longer supported. Dart code should now be compiled to kernel form and will be loaded by from kernel.blob in the assets directory. We retain the struct members for ABI stability. package_path is also not required since kernel blobs are self-contained.
-
- 17 12月, 2018 1 次提交
-
-
由 Chris Bracken 提交于
As of the migration to Dart 2, it has been necessary to compile Dart to kernel prior to execution. The embedder currently requires that the resulting kernel file be named `kernel_blob.bin` and be located at the root of the assets directory passed to the embedder API. This patch updates the test_fixtures build rule to perform a kernel compile using frontend_server, outputting `kernel_blob.bin` to `fixtures/test_target_name` directory, and updates the embedder unittests to specify the kernel file rather than the Dart source file. Since the kernel compiler requires a `main()` function to be defined, it also updates `simple_main.dart` from runtime_unittests to define `main()` rather than `simple_main()`. This also updates all existing sub-targets to be testonly. This relands commit ac9e521a, which was reverted in commit 49411258. Rather than running as prebuilt_dart_action, we use dart_action to ensure the frontend snapshot it compatible with the VM on which it's executed.
-
- 16 12月, 2018 2 次提交
-
-
由 Chris Bracken 提交于
This reverts commit ac9e521a. This broke dynamic release mode builds of //flutter/runtime:runtime_fixtures_kernel (likely all product-mode builds).
-
由 Chris Bracken 提交于
Compile embedder unit test Dart to kernel As of the migration to Dart 2, it has been necessary to compile Dart to kernel prior to execution. The embedder currently requires that the resulting kernel file be named `kernel_blob.bin` and be located at the root of the assets directory passed to the embedder API. This patch updates the test_fixtures build rule to perform a kernel compile using frontend_server, outputting `kernel_blob.bin` to `fixtures/test_target_name` directory, and updates the embedder unittests to specify the kernel file rather than the Dart source file. Since the kernel compiler requires a `main()` function to be defined, it also updates `simple_main.dart` from runtime_unittests to define `main()` rather than `simple_main()`. This also updates all existing sub-targets to be testonly.
-
- 27 11月, 2018 1 次提交
-
-
由 Chris Bracken 提交于
Reduces spurious error log messages in GLContextMakeCurrent() attempting set up the GR context: [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(42)] Could not make the context current to setup the gr context.
-
- 08 11月, 2018 1 次提交
-
-
由 Michael Goderbauer 提交于
-
- 26 5月, 2018 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 31 10月, 2017 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 26 10月, 2017 1 次提交
-
-
由 Chinmay Garde 提交于
-