- 02 3月, 2019 2 次提交
-
-
由 Gary Qian 提交于
- 01 3月, 2019 1 次提交
-
-
由 Greg Spencer 提交于
Fix the spelling errors in the dartdocs for the engine. There are no functionality changes here, just documentation fixes.
-
- 28 2月, 2019 1 次提交
-
-
由 Jason Simmons 提交于
Use a map instead of a switch to replace deprecated language and country codes. Also cache the result for the most recently used locale.
-
- 22 2月, 2019 2 次提交
-
-
由 Chris Bracken 提交于
* Roll back three Dart SDK rolls Revert "Roll src/third_party/dart 75ee523f91..4cff5a4fd6 (6 commits)" Revert "Roll src/third_party/dart 5ddd157809..75ee523f91 (19 commits)" Revert "Roll src/third_party/dart c92d5ca288..5ddd157809 (153 commits)" `pub upgrade` appears to fail 100% reproducibly on broken on Windows. This rollback rolls back both what appears to be the breaking roll (61fc1786) and the following roll. This reverts commit 0053c1d5. This reverts commit 1cf6b8b6. This reverts commit 61fc1786. * Revert "Revert "Revert "Remove unnecessary entry-point closurization. (#7827)" (#7876)" (#7904)" This reverts commit 93eeb48b.
-
- 21 2月, 2019 2 次提交
-
-
由 Chris Bracken 提交于
Flutter's accessibility APIs consist of three main calls from the embedder to the Dart application: 1. FlutterEngineUpdateSemanticsEnabled: enables/disables semantics support. 2. FlutterEngineUpdateAccessibilityFeatures: sets embedder-specific accessibility features. 3. FlutterEngineDispatchSemanticsAction: dispatches an action (tap, long-press, scroll, etc.) to a semantics node. and two main callbacks triggered by Dart code: 1. FlutterUpdateSemanticsNodeCallback: notifies the embedder of updates to the properties of a given semantics node. 2. FlutterUpdateSemanticsCustomActionCallback: notifies the embedder of updates to custom semantics actions registered in Dart code. In the Flutter framework, when accessibility is first enabled, the embedder will receive a stream of update callbacks notifying the embedder of the full semantics tree. On further changes in the Dart application, only updates will be sent.
-
由 Chris Bracken 提交于
Reference to `accessibilityFlags` corrected to `accessibilityFeatures`.
-
- 20 2月, 2019 3 次提交
-
-
由 Chris Bracken 提交于
Fixes a minor pluralisation error in docs for didGainAccessibilityFocus, didLoseAccessibilityFocus.
-
- 18 2月, 2019 1 次提交
-
-
由 sjindel-google 提交于
-
- 16 2月, 2019 1 次提交
-
-
由 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.
-
- 14 2月, 2019 2 次提交
- 09 2月, 2019 1 次提交
-
-
由 Brian Osman 提交于
This does several things: - It adds CPU time on the IO thread, but avoids GPU time on the GPU thread. - For images that are never drawn with mipmaps, it adds about 33% memory overhead. For images that are drawn with mipmaps, it saves an entire copy of the base level. - It fixes https://github.com/flutter/flutter/issues/24517, which is a driver bug related to mip-mapping and cross-context images. Overall, I think the tradeoff is good, but I'm curious to see what benchmarks look like.
-
- 08 2月, 2019 2 次提交
-
-
由 Michael Klimushyn 提交于
`MultiFrameCodec` now uses whatever previously cached required frame is available instead of panicking if it doesn't have the exact frame requested by `SkCodec::FrameInfo#fRequiredFrame`. `SkCodec::FrameInfo#fRequiredFrame` doesn't point to the one and only frame that's required to decode the given frame. It points to the latest frame that's disposal method none and filling a greater surface area than the current frame. The last required frame `MultiFrameCodec` has actually cached is also valid in these cases and can be supplied as `fPriorFrame` instead. [flutter/flutter#26757](https://github.com/flutter/flutter/issues/26757#issuecomment-459522530) has a more detailed explanation. Fixes flutter/flutter#26757
-
由 Dan Field 提交于
-
- 07 2月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 05 2月, 2019 2 次提交
-
-
由 Matt Carroll 提交于
-
由 Matt Carroll 提交于
-
- 31 1月, 2019 3 次提交
-
-
由 Kaushik Iska 提交于
- Moved versions from shell to common - versions singleton contains all the required versions.
-
由 Gary Qian 提交于
-
由 Gary Qian 提交于
Engine half of flutter/flutter#26332
-
- 30 1月, 2019 1 次提交
-
-
由 Dan Field 提交于
* Improve PathMetrics * Use index instead of dirty * revert unintended change * space
-
- 25 1月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
Re-land "Wrap the user entrypoint function in a zone with native exception callback. (#7512)" (#7551) This reverts commit 4c135c29 and applies relevant fixes.
-
- 17 1月, 2019 2 次提交
-
-
由 Vyacheslav Egorov 提交于
Revert "Wrap the user entrypoint function in a zone with native exception callback. (#7512)" (#7522) This reverts commit 25559ed0. Reason for revert: broken in AOT mode. @pragma('vm:entry-point') placed on a function only instructs the compiler to retain the function itself, but does not tell compiler to generate and retain tear-off for this function. In this PR _runMainZoned was marked as an entry-point but C++ code was trying to tear it off and use a closure, instead of invoking it directly, which is not supported.
-
由 Chinmay Garde 提交于
-
- 16 1月, 2019 4 次提交
-
-
由 Michael Goderbauer 提交于
This reverts commit 24cf93e2.
-
由 Jason Simmons 提交于
-
由 Michael Goderbauer 提交于
This reverts commit 6c29fb4d.
-
由 Michael Goderbauer 提交于
-
- 15 1月, 2019 4 次提交
-
-
由 Dan Field 提交于
* Make IOManager own resource context
-
由 Ian Hickson 提交于
* Documentation cleanup * Typo fix
-
由 Razvan Lung 提交于
* add ColorFilter matrix support
-
由 Jason Simmons 提交于
Reuses the implementation that was previously done for Scene.toImage (see https://github.com/flutter/engine/commit/20c805c97312fb69e67984847d031339242a9924) This introduces a breaking API change: Picture.toImage is now asynchronous and returns a Future<Image> Fixes https://github.com/flutter/flutter/issues/23621
-
- 12 1月, 2019 1 次提交
-
-
由 Dan Field 提交于
* fix up analysis for Dart in Engine, particularly for tests
-
- 11 1月, 2019 2 次提交
-
-
-
由 liyuqian 提交于
The defaultClipBehavior is no longer used anywhere in the Flutter framework and Google3.
-
- 10 1月, 2019 1 次提交
-
-
由 Justin McCandless 提交于
-