Font Access: Extract functions in Windows implementation.

The main goal of this CL is to make ExtractNamesFromFamily() in
//content/browser/font_access/font_enumeration_cache_win.cc smaller, and
therefore easier to read.

* COM interface function arguments that are only used during the
  function call are passed using raw pointers, instead of
  Microsoft::WRL::ComPtr smart pointers. This is similar to limiting the
  use of std::unique_ptr and scoped_refptr to arguments that are stored
  and used past the function call.

* GetNativeString() is folded into GetLocalizedString(). A key
  observation here is that, before this CL, GetLocalizedString() was
  only used for `full_name` (lines 176-179), and the two calls
  effectively implemented the same fallback logic used in the old
  GetNativeString() implementation. So, GetLocalizedString() now
  implements the fallback logic, and is used everywhere.

* For uniformity, GetLocalizedString() is updated to take a raw pointer
  to the IDWriteFont COM interface, instead of a Microsoft::WRL::ComPtr
  smart pointer. This is appropriate because GetLocalizedString() only
  uses the argument during the function call.

* GetSystemFonts() contains the logic that used to live at lines
  257-272 before this CL.

* GetFontInformation() contains logic that used to be duplicated at
  lines 143-151, 164-171, and 185-193 before this CL.

* GetFamilyName() contains the logic that used to live at lines 106-114
  before this CL.

* GetFontPostScriptName() contains the logic that used to live at lines
  134-154 before this CL.

* GetFontFullName() contains the logic that used to live at lines
  162-180 before this CL.

* GetFontStyleName() contains the logic that used to live at lines
  183-209 before this CL.

* Lines 211-213 before this CL were inlined in lines 269-271.

Bug: 1232812
Change-Id: Ie0e5a001bf6faf676a0188b906bb60a8ab0102f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3105730
Auto-Submit: Victor Costan <pwnall@chromium.org>
Reviewed-by: Austin Sullivan <asully@chromium.org>
Commit-Queue: Austin Sullivan <asully@chromium.org>
Cr-Commit-Position: refs/heads/main@{#915573}
1 file changed
tree: 2bd72fcbad6269f0f751fc962542d2c8e9792ccb
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.