Parse theme info for font declarations

Working on this one now. Just to make sure: what should happen when a font is added using the .info file?

If the provider isn't enabled, @font-your-face would display an error prompting an administrator to enable it. Otherwise, it would enable the font from the provider at the URL, so that font can be reliably referenced in the theme CSS.

Suppose a provider has been enabled, but the import has not been run yet. Should one run the importer first? Of should we load the font without imported font info?

Adding Google Fonts using the .info file is quite easy, because Google Fonts only need a drupal_add_css($path_to_font, array('type' => 'external')). Other @font-your-face font-providers need to download the font and serve the CSS from the local file system, like FontSquirrel.

The easiest solution would be to use the module to:

1. Enable providers
2. Import font definitions
3. Add them using the interface AND/OR adding them to the .info file in your theme.

I'm already done implementing this for Google Fonts and Fontsquirrel, and now working on implementing it in the other modules.

However; it would be better if step 2 could be skipped, so to only load the font definitions of the font that is added via the interface.

My thoughs:
- Import the fonts of the provider automatically if those haven't been loaded yet. So they will be loaded by fontyourface_preprocess_page()
- Expand hook_fontyourface_import() with an attribute to import just one font, so only that font can be enabled.

For now I'll just continue working on the current solution (first enable and import the fonts), then add them using the .info file.

The way fonts can be added now:

fonts[google_fonts_api][] = "Salsa"
fonts[google_fonts_api][] = "Vast Shadow"
fonts[fontsquirrel][] = "1942 Report"

Committed to 7.x-2.x-dev. Please test.

Added support for:

- Google Fonts API
- TypeKit API
- KERNEST
- Fontsquirrel

Update README.txt

Fonts can be added in your THEMENAME.info like:

fonts[typekit_api][] = "Lobster"
fonts[fontsquirrel][] = "1942 Report"
fonts[kernest][] = "Alte DIN 1451 Mittelschrift Gepraegt"

Committed to 7.x-2.x-dev

1) Hmm, I think you are right. That one isn't used anymore. Must have been a left-over from a night hacking ;) I've removed it.
2) I agree, there is room for improvement. As you might have noticed, I've made the 'name' column unique - so we could use that one to search on instead of path and/or family.
3) That's exactly why I've chosen this setup. The problem with URL's is that there can be a lot of confusion of which URL to use. Some examples:

- http://fonts.googleapis.com/css?family=Contrail+One
- http://www.google.com/webfonts/specimen/Contrail+One
- http://www.google.com/webfonts/family?family=Contrail One&subset=latin#regular

Which one to use? That's why I've chosen to use the names like this:

fonts[google_fonts_api][] = "Abril Fatface 400"
fonts[google_fonts_api][] = "Vast Shadow"
fonts[fontsquirrel][] = "1942 Report"

By te way, I've just added a small helper function to count the number of fonts. I see a lot of separate SQL queries to count fonts, I'll walkthrough the code soon to replace those strolled queries with a function call.

/**
 * Returns the amount of fonts that exists in the database
 *
 * $provider can be used to filter on provider (eg 'google_fonts_api')
 * @status can be used to filter on status (NULL / TRUE / FALSE)
 */
function fontyourface_count_fonts($provider = NULL, $status = NULL) {
  
  $query = db_select('fontyourface_font', 'fonts');
  $query->fields('fonts');
  
  if (!empty($provider)) {
    $query->condition('provider', $provider);
  }
  if (!empty($status)) {
    $query->condition('status', (int) $status);
  }
  
  $count = $query->execute()->rowCount();
  
  return $count;
}

What if I change the UNIQUE key in the table from using name only to a combination of provider and name?

That combination should be unique. The problem with using the URL is that it can be hard for the end-user to determine which URL to use in the .info file. As given in the example above, the last one is the one returned by the API (http://www.google.com/webfonts/family?family=Contrail One&subset=latin#regular). And that URL cannot be found on the Google Web Fonts library. So you first have to enable the FYF UI and the Google Fonts submodule to determine which URL to use.

In my solution, just the following line would work:
fonts[google_fonts_api][] = "Contrail One"