e1f6cb431e
In apps following the pattern to do all the things in fragments, and possibly loading different fragments for different form factors, their activity would need to remain a stub and can't contain phone-only layout, making CollapsingToolbarBaseActivity unsuitable for them. So add a CollapsingToolbarBaseFragment for integrating the same functionality in fragments. The layout files are also moved to be under the same name, but different content depending on the platform version, to simplify the logic loading them. Bug: 177638625 Test: manual Change-Id: Ie9e2a147dd4bd2c1ee3924b1afc4c10a6f735e59
29 lines
817 B
Plaintext
29 lines
817 B
Plaintext
package {
|
|
// See: http://go/android-license-faq
|
|
// A large-scale-change added 'default_applicable_licenses' to import
|
|
// all of the 'license_kinds' from "frameworks_base_license"
|
|
// to get the below license kinds:
|
|
// SPDX-license-identifier-Apache-2.0
|
|
default_applicable_licenses: ["frameworks_base_license"],
|
|
}
|
|
|
|
android_library {
|
|
name: "SettingsLibCollapsingToolbarBaseActivity",
|
|
|
|
srcs: ["src/**/*.java"],
|
|
resource_dirs: ["res"],
|
|
|
|
static_libs: [
|
|
"androidx.annotation_annotation",
|
|
"androidx.core_core",
|
|
"com.google.android.material_material",
|
|
],
|
|
sdk_version: "system_current",
|
|
min_sdk_version: "21",
|
|
apex_available: [
|
|
"//apex_available:platform",
|
|
"com.android.cellbroadcast",
|
|
"com.android.permission",
|
|
],
|
|
}
|