On Wed, Sep 24, 2008 at 5:03 PM, Corey O'Connor <[EMAIL PROTECTED]> wrote: > > Is there any reason to develop both a Pango and vanilla GTK frontend? > Or should effort be focused on just one? > > As far as I can tell, the Pango implementation uses the backing text > buffer directly. This would offer better performance than the vanilla > GTK implementation which, effectively, duplicates the backing text > buffer into a GTK text buffer for display. However, the Pango > implementation is not nearly as far along so perhaps there is a reason > it is not favored? >
I would definitely like to get the Pango frontend replace the Gtk one (following our terminology), and I think that in the long run drawing the text "by hand" is the only sensible option. Unfortunately, I did not manage to make it "good enough": 1. It sometimes crashes 2. It's quite slow Duncan offered a solution to track the crashes, but I did not look into it. I /guessed/ that the slowness is caused by my using pango in a "bizzare way": the layout is re-done from scratch every time we draw something (necessary since we want to display only part of the buffer). An alternative might be to layout the text by hand, assuming that all characters have the same size. Cheers, JP. Duncan wrote: You can catch those GError exceptions and print more interesting info. Use: > catchGError > (do ... > ...) > (\(GError dom code msg) -> fail msg) --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
