* Implement TooltipThemeData and TooltipTheme
* Add text style property
* Updated tooltip default colors for light and dark theme to match Material specification
72341ed032...89142b55db
git log 72341ed032867b36ba97b05c5e3b76af0a197ba5..89142b55db0de1b9c823b855de9489b69ec28db8 --no-merges --oneline
89142b55d Roll fuchsia/sdk/core/linux-amd64 from RfQgXVCVII4_oiWfVIkIMMVepj5wklCOhiClVRyYNucC to NrExSKBKIhY3SnE4sD0-vHjEMCBYYffzarRM2rWONUUC (flutter/engine#10131)
44cf59c38 Roll fuchsia/sdk/core/mac-amd64 from gvGDLzElkEmPrBTbtjW6rhPqr78z-b4ytTxE2k58CFAC to 9EcA--gzHNo80R_fAuB_Tq7ECubTP0Uz3UrycPIvRpsC (flutter/engine#10130)
fcd67323b [fuchsia] Use the patched sdk to generate the flutter jit runner far (flutter/engine#10122)
cfd43a105 Roll fuchsia/sdk/core/linux-amd64 from gTG1jp04GzBudVJqRxulXYOEQgbYTUQgnqLDYAq7z3sC to RfQgXVCVII4_oiWfVIkIMMVepj5wklCOhiClVRyYNucC (flutter/engine#10126)
936c74dfc Roll fuchsia/sdk/core/mac-amd64 from UCAnzi4k9pA30l_iZ2Ru51Tc3Ke6iacIdjFMgVUVdRMC to gvGDLzElkEmPrBTbtjW6rhPqr78z-b4ytTxE2k58CFAC (flutter/engine#10121)
aaf6bad4b Fixed memory leak with engine registrars. (flutter/engine#10068)
4bf81b8cf [fuchsia] Use manifest file to better replicate the existing build (flutter/engine#10102)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (cbracken@google.com), and stop
the roller if necessary.
An optimization to the coverage collection speed was added in #30811. This commit further expands on it to parameterize the CoverageCollector with a custom predicate, allowing internal use cases to filter the RPC calls to the Dart VM based on scripts of interest to coverage collection.
* Implement TooltipThemeData and TooltipTheme
* Add tooltip text style property
* Update default tooltip text style and decoration to match Material specification
* Fix debugLabel incorrectly labeling "white" as "black", and vice versa by default
Primarily these methods no longer allocate any objects other than their
return values.
Additionally, the math in the methods is reduced compared to the general
case math based on known input conditions.
`flutter build aar`
This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects.
This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps.
This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app.
`flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files.
In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`:
repositories {
maven {
url "<path-to-flutter-module>build/host/outputs/repo"
}
}
dependencies {
implementation("<package-name>:flutter_<build-mode>:1.0@aar") {
transitive = true
}
}
`flutter build aar`
This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects.
This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps.
This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app.
`flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files.
In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`:
repositories {
maven {
url "<path-to-flutter-module>build/host/outputs/repo"
}
}
dependencies {
implementation("<package-name>:flutter_<build-mode>:1.0@aar") {
transitive = true
}
}
