After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 354860 - OpenGL backend for Pango
OpenGL backend for Pango
Status: RESOLVED OBSOLETE
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2006-09-07 23:02 UTC by Behdad Esfahbod
Modified: 2018-05-22 12:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Behdad Esfahbod 2006-09-07 23:02:01 UTC
There's a patch out there, lets open a tracker bug!
Comment 2 Behdad Esfahbod 2006-09-13 23:12:14 UTC
It occured to me that one can implement a glyph cache in cairo's glitz backend instead of inventing a new pango module.
Comment 3 Chris Wilson 2007-04-25 11:18:46 UTC
Compare and contrast:
http://svn.o-hand.com/view/clutter/trunk/clutter/clutter/pango/

Behdad, what are your current thoughts towards the requirements for a OpenGL backend? Does Pango need one? Can it share code or link against glitz?
Comment 4 Behdad Esfahbod 2007-04-25 17:41:12 UTC
(In reply to comment #3)
> Compare and contrast:
> http://svn.o-hand.com/view/clutter/trunk/clutter/clutter/pango/

Any idea why they had to implement their own?  Oh I think I remember, because pango's ft2 backend doesn't support color.

> Behdad, what are your current thoughts towards the requirements for a OpenGL
> backend? Does Pango need one? Can it share code or link against glitz?

I was thinking that the right approach is to just fix cairo's glitz backend and don't touch pango.  pangocairo is the way to go.  Any other backend is deprecated and falls behind as pango goes forward.
Comment 5 Emmanuele Bassi (:ebassi) 2013-02-27 14:51:39 UTC
[6 years later...]

the Pango renderer in Clutter was moved down to Cogl, and it's essentially just a special PangoRenderer that stores the glyphs in a textured cache and submits the correct geometry through GL to the GPU:

  http://git.gnome.org/browse/cogl/tree/cogl-pango

in the meantime: the glitz backend for Cairo is thoroughly deprecated (don't even think it's there any more) and Cairo has a GL and a GLES backends. the reason why we don't just use cairo-gl and and pangocairo is that we set up our own state in Cogl, and swapping out to another GL-using library may trump that state and cause performance degradation.

to be fair, I'd gladly use PangoCairo and cairo-gl, and drop Cogl-Pango (and I'm pretty sure the Cogl maintainers agree), but it's something that has to be investigated still.
Comment 6 Matthias Clasen 2018-01-04 05:02:47 UTC
gtk does something similar now
Comment 7 GNOME Infrastructure Team 2018-05-22 12:21:59 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pango/issues/56.