- 01 May, 2020 1 commit
-
-
Jonah Williams authored
-
- 29 Apr, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 23 Apr, 2020 2 commits
-
-
Dan Field authored
-
Yegor authored
* extract engine sub-metrics; change reported metrics - Extract sub-metrics reported by the Web engine: "preroll_frame", "apply_frame". - Add a concept of unreported metrics: displayed on the benchmark UI, but not on the dashboard. - Make "sceneBuildDuration" and "windowRenderDuration" unreported, which are too fine-grained. They are included in "drawFrameDuration" already. - Report outlier ratio instead of outlier average. The ratio is more useful of the two.
-
- 22 Apr, 2020 3 commits
-
-
Jonah Williams authored
Revert "[flutter_tools] default tree-shake-icons to enabled and improve performance (#54923)" (#55413) This reverts commit 0b93a921.
-
Jonah Williams authored
-
Jonah Williams authored
-
- 21 Apr, 2020 1 commit
-
-
Yegor authored
-
- 18 Apr, 2020 1 commit
-
-
Jim Graham authored
-
- 16 Apr, 2020 3 commits
-
-
Yegor authored
-
Yegor authored
* web benchmarks: separate outliers to reduce noise; add visualization
-
Michael Thomsen authored
-
- 15 Apr, 2020 2 commits
-
-
Jacob MacDonald authored
## Description Removes the `flutter_test` dependency on `quiver`, instead using the more targeted `clock` and `fake_async` packages. ## Related Issues https://github.com/flutter/flutter/issues/53908 ## Tests No changes to tests ## Checklist Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (`[x]`). This will ensure a smooth and quick review process. - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I signed the [CLA]. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] All existing and new tests are passing. - [x] The analyzer (`flutter analyze --flutter-repo`) does not report any problems on my PR. - [x] I am willing to follow-up on review comments in a timely manner. ## Breaking Change Did any tests fail when you ran them? Please read [Handling breaking changes]. - [ ] No, no existing tests failed, so this is *not* a breaking change. - [x] Yes, this is a breaking change. *If not, delete the remainder of this section.* - [x] I wrote a design doc: https://docs.google.com/document/d/1EkkLbECNBwHgddBQAZqEy7iQLTIxR1rgChKzxcLwhio/edit - [x] I got input from the developer relations team, specifically from: @RedBrogdon - [x] I wrote a migration guide: https://github.com/flutter/website/pull/3932 <!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview [Test Coverage]: https://github.com/flutter/flutter/wiki/Test-coverage-for-package%3Aflutter [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [Features we expect every widget to implement]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene [Handling breaking changes]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
-
tauu authored
Co-authored-by: Georg Wechslberger <wechslbe@ma.tum.de>
-
- 14 Apr, 2020 1 commit
-
-
Jenn Magder authored
-
- 12 Apr, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 10 Apr, 2020 1 commit
-
-
Mouad Debbar authored
-
- 09 Apr, 2020 2 commits
-
-
Jacob MacDonald authored
-
Filip Hracek authored
-
- 08 Apr, 2020 3 commits
-
-
Yegor authored
-
Michael Goderbauer authored
-
Jonah Williams authored
-
- 07 Apr, 2020 2 commits
-
-
Michael Thomsen authored
-
Konstantin Scheglov authored
-
- 06 Apr, 2020 2 commits
-
-
Mouad Debbar authored
-
stuartmorgan authored
This moves the app template more toward being a more generic starting point for any Flutter application, eliminating some hard-code assumptions about there being a single window/engine pair that is directly bound to the life of the application: - Moves the runloop into its own class, making it capable of servicing any number of engine instances. - Moves the logic for setting up a window containing only a Flutter view into a window subclass for ease of re-use. - Makes quit-on-window-close an optional property. (Long term this should be even more generic, like a quit-when-last-window-closes option, but this is a short-term improvement that removes the binding between the runloop and the window). - Allows for multiple instances of Win32Window to exist without issues relating to the window class registration. Since there are getting to be a non-trivial number of files associated with the runner, this moves the source into a runner/ directory, as is already done on some other platforms. Note that creating multiple Flutter windows at the same time still doesn't work correctly even with this change, but this addresses some of the known issues, and makes it easier to test in the future (e.g., for debugging engine-level issues with multiple instances). Fixes #45397
-
- 03 Apr, 2020 1 commit
-
-
- 01 Apr, 2020 1 commit
-
-
Yegor authored
-
- 31 Mar, 2020 2 commits
-
-
Emmanuel Garcia authored
-
Kate Lovett authored
-
- 30 Mar, 2020 1 commit
-
-
Jonah Williams authored
-
- 27 Mar, 2020 1 commit
-
-
Mouad Debbar authored
-
- 25 Mar, 2020 1 commit
-
-
Mouad Debbar authored
-
- 24 Mar, 2020 1 commit
-
-
Jonah Williams authored
Should fix issues introduced in web-server device and allow loading org-dartlang-app URIs
-
- 19 Mar, 2020 1 commit
-
-
Emmanuel Garcia authored
-
- 18 Mar, 2020 5 commits
-
-
Emmanuel Garcia authored
-
Emmanuel Garcia authored
This reverts commit 1f173184.
-
Emmanuel Garcia authored
-
Jonah Williams authored
This is necessary to ensure the tests can run in google3. Fixes https://b.corp.google.com/issues/151657461
-
Jonah Williams authored
Update to latest dwds APIs, moving back to dwds driven hot restart and enabling future work on expression evaluation.
-