extend FontConfigInterface to start to match new fontmgr design

trunk/include/ports/SkFontConfigInterface.h

Index: trunk/include/ports/SkFontConfigInterface.h
===================================================================
--- trunk/include/ports/SkFontConfigInterface.h	(revision 8444)
+++ trunk/include/ports/SkFontConfigInterface.h	(working copy)
@@ -8,6 +8,7 @@
 #ifndef SkFontConfigInterface_DEFINED
 #define SkFontConfigInterface_DEFINED
 
+#include "SkFontStyle.h"
 #include "SkRefCnt.h"
 #include "SkTypeface.h"
 
@@ -50,6 +51,7 @@
         uint32_t    fID;
         int32_t     fTTCIndex;
         SkString    fString;
+        SkFontStyle fStyle;
     };
 
     /**
@@ -81,6 +83,14 @@
      *  libfontconfig. This does not affect the refcnt of the returned instance.
      */
     static SkFontConfigInterface* GetSingletonDirectInterface();
+
+    // New APIS, which have default impls for now (which do nothing)
+
+    virtual int countFamilies();
+    virtual int getFamilySet(int index, SkString* outFamilyName,
+                             FontIdentity outIdentities[], int maxCount);
+    virtual int matchFamilySet(const char familyName[], SkString* outFamilyName,
+                               FontIdentity outIdentities[], int maxCount);
 };

[bungeman-skia, 2013/03/29 21:13:37]

Maybe we also want matchFamilyStyle which does 'system fallback' for styles,
whatever that may mean. This could be seen as a helper, in that the user doesn't
need to do their own matching. On the other hand, DirectWrite doesn't have the
notion of fallback or closest fit styles, it pretty much has exactly what we
have here. So we'd have to write something for that. Then again, maybe it's
better that we write that once than having everyone else implement over and
over.

 
 #endif