- 19 Aug, 2021 1 commit
-
-
Dan Field authored
-
- 29 Jul, 2021 1 commit
-
-
Jim Graham authored
This reverts commit 32c2e2ba.
-
- 27 Jul, 2021 1 commit
-
-
Dan Field authored
-
- 28 Jun, 2021 1 commit
-
-
Dan Field authored
-
- 01 Apr, 2021 1 commit
-
-
Chris Bracken authored
-
- 31 Mar, 2021 1 commit
-
-
Alexandre Ardhuin authored
-
- 12 Feb, 2021 1 commit
-
-
Ian Hickson authored
-
- 16 Sep, 2020 1 commit
-
-
Michael R Fairhurst authored
-
- 04 Aug, 2020 3 commits
-
-
Michael Goderbauer authored
-
Michael Goderbauer authored
This reverts commit 4518a72f.
-
Alexandre Ardhuin authored
* migrate part of painting to nullsafety * address review comments * address review comment
-
- 26 Jun, 2020 1 commit
-
-
Yegor authored
-
- 11 Jun, 2020 1 commit
-
-
Alexandre Ardhuin authored
* add language version 2.8 in packages/flutter * enable non-nullable analyzer flag
-
- 09 Apr, 2020 1 commit
-
-
Filip Hracek authored
-
- 07 Jan, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 03 Jan, 2020 1 commit
-
-
creativecreatorormaybenot authored
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 22 Nov, 2019 1 commit
-
-
Greg Spencer authored
No code changes, just comments: I spell-checked all the comments in the repo.
-
- 04 Oct, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 15 Aug, 2019 1 commit
-
-
liyuqian authored
The update is copied from an update we made to a Google-internal client: cl/260202900 The update will save 1 shader compilation. This should help solve our regression: https://github.com/flutter/flutter/issues/31203 More regressions on iOS might be introduced later by https://github.com/flutter/engine/pull/9813#issuecomment-520039890 Unfortunately, we didn't rebase our benchmarks so such regressions were not detected. Hence to fully solve https://github.com/flutter/flutter/issues/31203, we might need to revert some change in https://github.com/flutter/engine/pull/9813 to make iOS shader warm-up happen on the GPU thread again.
-
- 26 Jul, 2019 1 commit
-
-
gaaclarke authored
Sped up shader warmup by only drawing on a 100x100 surface and doing the draw calls on top of each other.
-
- 29 Apr, 2019 1 commit
-
-
Dan Field authored
* Re-enable const
-
- 11 Apr, 2019 1 commit
-
-
liyuqian authored
Thanks to cbracken@'s suggestion on another Google-internal change.
-
- 12 Mar, 2019 1 commit
-
-
liyuqian authored
* No image shader caching in default shader warm-up It turns out that no matter how small the image is, too much memory will be used. Hence remove the image shader caching and let the client implement itself based on needs. Fixes https://github.com/flutter/flutter/issues/29172 * Fix
-
- 07 Mar, 2019 1 commit
-
-
liyuqian authored
Fix issues in https://github.com/flutter/flutter/pull/28687
-
- 01 Mar, 2019 3 commits
-
-
Alexandre Ardhuin authored
* add trailing commas on list/map/parameters * add trailing commas on Invocation with nb of arg>1 * add commas for widget containing widgets * add trailing commas if instantiation contains trailing comma * revert bad change
-
liyuqian authored
## Description This moves another 15-20ms from the animation jank of one of our important client to the startup latency. Unfortunately, this is probably not captured in our current benchmarks (presumably some other bottlenecks overshadow this shader compilation in the worst_frame benchmark). Considering that drawing images is such a common operation, maybe we should add one in the future to benchmark this. We need this PR to land soon for our client because this changes the API to return Future. ## Related Issues https://github.com/flutter/flutter/issues/813
-
- 28 Feb, 2019 1 commit
-
-
liyuqian authored
One of our important client's SKP shows that this could improve one of their janky frame by 20ms. This also improves our flutter_gallery__transition_perf's worst frame time by ~20ms. On the other hand, 15ms has been added to the start-up latency. I guess it's a little faster to compile the shader on the start-up because we're compiling a lot of shaders there and the CPU cache must be hot. ## Related Issues https://github.com/flutter/flutter/issues/813
-
- 27 Feb, 2019 1 commit
-
-
liyuqian authored
This reverts commit adc8e159. This should be safe to land once https://github.com/flutter/flutter/pull/28530 gets merged Merge on yellow doc test because the doc test is actually green.
-
- 23 Feb, 2019 1 commit
-
-
liyuqian authored
This reverts commit a44f174e. Reason: start_up tests become flaky. See https://github.com/flutter/flutter/issues/28374 TBR: xster Merge on red to fix the tree
-
- 22 Feb, 2019 1 commit
-
-
liyuqian authored
This patch adds a default shader warm up process which moves shader compilation from the animation time to the startup time. This also provides an extension for `runApp` so developers can customize the warm up process. This should reduce our worst_frame_rasterizer_time_millis from ~100ms to ~20-30ms for both flutter_gallery and complex_layout benchmarks. Besides, this should also have a significant improvement on 90th and 99th percentile time (50%-100% speedup in some cases, but I haven't tested them thoroughly; I'll let our device lab collect the data afterwards). The tradeoff the is the startup time (time to first frame). Our `flutter run --profile --trace-startup` seems to be a little noisy and I see about 100ms-200ms increase in that measurement for complex_layout and flutter_gallery. Note that this only happens on the first run after install or data wipe. Later the Skia persistent cache will remove the overhead. This also adds a cubic_bezier benchmark to test the custom shader warm up process. This should fix https://github.com/flutter/flutter/issues/813 (either by `defaultShaderWarmUp`, or a `customShaderWarmUp`).
-