diff options
| author | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-18 22:31:09 +0000 |
|---|---|---|
| committer | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-18 22:31:09 +0000 |
| commit | d259a8ecab95cd657b9c7d413e8bfa3c86d0d4cb (patch) | |
| tree | 83805324a9ffeeb10b334d544b13155c8c52b069 /content/content_common.gypi | |
| parent | 772b57ab0dcd7843157b961f10999e48088e8973 (diff) | |
| download | chromium_src-d259a8ecab95cd657b9c7d413e8bfa3c86d0d4cb.zip chromium_src-d259a8ecab95cd657b9c7d413e8bfa3c86d0d4cb.tar.gz chromium_src-d259a8ecab95cd657b9c7d413e8bfa3c86d0d4cb.tar.bz2 | |
Support getting the font list in Pepper. This currently only works out of
process.
This adds a function to the font interface to get the font list. Since we
don't have arrays or dictionaries in Pepper yet, I used a string with nulls
separating the names. A previous attempt to make a "font list resource" proved
excessively complicated and not actually much easier for clients to deal with.
This refactors the existing font list getting that used to be in the options
for the browser. I moved it to content and split it into two pieces, the
synchronous version, and then an asynchronous wrapper around that which both
the prefs code and the pepper code use. This cleaned up some of the preferences
code, and also fixes the leak of the entire font list in the code.
I used the new callback/bind system for the async font loading. I had to add
BrowserThread support for the new system.
This uses the PepperMessageFilter to listen for font load requests from the
plugin in the browser process. This is nice because we can add stuff here and
have messages serviced for both in-process and out-of-process plugins. This
proved to be complicated due to the HostResolver used in some of the existing
code, and thread restrictions for how to deal with it. This is why there are
two modes for the filter object.
I changed the delegates around for the Dispatcher. Now the PluginDispatcher
has the delegate interface since the HostDispatcher didn't actually need any
of them and we were accumulating a lot of empty functions in the
PepperPluginRegistry.
It's possible for the fonts to be loaded on Windows and Mac without IPC, since
enumerating fonts should be possible inside the sandbox. I didn't implement
this since it adds extra complexity and probably doesn't give that much
benefit.
TEST=manual
BUG=none
Review URL: http://codereview.chromium.org/7044012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85827 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/content_common.gypi')
| -rw-r--r-- | content/content_common.gypi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/content/content_common.gypi b/content/content_common.gypi index e22ee0c..5e237d4 100644 --- a/content/content_common.gypi +++ b/content/content_common.gypi @@ -99,6 +99,10 @@ 'common/font_config_ipc_linux.h', 'common/font_descriptor_mac.h', 'common/font_descriptor_mac.mm', + 'common/font_list.h', + 'common/font_list_gtk.cc', + 'common/font_list_mac.mm', + 'common/font_list_win.cc', 'common/font_loader_mac.h', 'common/font_loader_mac.mm', 'common/geolocation_messages.h', |