Google Git
Sign in
chromium / chromium / src / 01ec60159c14759e5b99c917bd14108c5c2d0f5e
commit01ec60159c14759e5b99c917bd14108c5c2d0f5e[log] [tgz]
authorAngus L. M. McLean IV <angusmclean@chromium.org>Tue Apr 19 16:28:21 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 19 16:28:21 2022
tree60a05f7ba2e18c7057f6f8f3b18714d848d30ecc
parent9b6234bc7457363dc199f152b56c6aa01390297b [diff]
personalization: Add Daily Refresh for Google Photos wallpapers

Adds the Daily Refresh functionality to Google Photos wallpapers, from
the mojo interface backwards. Does not include UI changes to allow the
user to actually use this functionality.

Quick note:

`GooglePhotosWallpaperParams` will contain an album id in the id member
if this is for daily refresh, but when we move to `WallpaperInfo`, it
will be put in `WallpaperInfo.collection_id`. Shortly after
instantiation, we populate `WallpaperInfo.location` with the id of the
current photo, so that we can load it properly from cache on start up.

Alternatively, I could add a `collection_id` field to
`GooglePhotosWallpaperParams`, but in that case only one of
`collection_id` and `id` will be used in that class at a time, never
both.

Bug: 229018723
Change-Id: I3e07f6611509c3c03c0c6a0b95d3cf34169c1f03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3584728
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: David Black <dmblack@google.com>
Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Angus McLean <angusmclean@chromium.org>
Cr-Commit-Position: refs/heads/main@{#993739}
20 files changed
tree: 60a05f7ba2e18c7057f6f8f3b18714d848d30ecc
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.