|Product:||fontconfig||Reporter:||Behdad Esfahbod <freedesktop>|
|Component:||library||Assignee:||Akira TAGOH <akira>|
|Status:||ASSIGNED ---||QA Contact:||Behdad Esfahbod <freedesktop>|
|Priority:||medium||CC:||akira, fontconfig-bugs, freedesktop, samuel|
|i915 platform:||i915 features:|
Description Behdad Esfahbod 2015-05-01 18:47:17 UTC
Perhaps using gobject-introspection, like we do in HarfBuzz... G-I sucks for non-GObject projects though; a SWIG or even ctypes alternative might be easier. Not sure. Just filing the request for now.
Comment 1 Akira TAGOH 2015-05-11 01:43:55 UTC
sounds nice. let me take a look.
Comment 2 Akira TAGOH 2015-05-13 07:33:24 UTC
FWIW providing all of public APIs for language bindings may be hard. some of them isn't designed like OOP concept. this is another topic but may be good to polish them in fontconfig 3 but anyway.
Comment 3 Behdad Esfahbod 2015-05-13 20:00:57 UTC
Right... But just in case, which API pieces do you have in mind exactly?
Comment 4 Akira TAGOH 2015-05-14 01:53:32 UTC
Given that we use g-i, it assumes the function takes the object in the first argument. in that sense, we can't provide bindings for functions one will mostly uses like FcFont*List(), FcFont*Match(), FcFont*Sort() because these aren't placed at the namespace of FcConfig say. we need to wrap up to make them language-bindings available.
Comment 5 Behdad Esfahbod 2015-05-14 02:30:18 UTC
Functions that don't match the naming pattern will be bound as module functions, so that's not a problem. We would get fc.FontSort(cfg, ...).