1 Status of the GTK+ 2.0 port :
2 ---------------------------
4 GtkList and GtkCList ==> GtkTreeView conversion :
6 - column_prefs.c : done
7 - decode_as_dlg.c : done
8 - dfilter_expr_dialog.c : done
9 - filter_prefs.c : done
11 - plugins_dlg.c : done
13 GtkCTree ==> GtkTreeView conversion : done
15 GtkText ==> GtkTextView conversion : done
19 - gtk_font_selection_dialog_set_filter doesn't exist anymore (but hasn't
20 been removed from the documentation). There is no way to filter the
21 font selection to get only fixed width fonts; in a message at
23 http://mail.gnome.org/archives/gtk-devel-list/2002-July/msg00202.html
25 Owen Taylor explains why Pango (and hence GTK+ 2.0) doesn't know what
26 fonts are fixed-width and what fonts aren't:
28 From: Owen Taylor <otaylor redhat com>
29 To: Allin Cottrell <cottrell wfu edu>
30 Cc: gtk-devel-list.gnome.org
31 Subject: Re: fonts in gtk-2.0/pango
32 Date: Sat, 27 Jul 2002 10:06:52 -0400 (EDT)
36 > Second observation: Pango has an elaborate classification system for
37 > fonts, but this system has some serious blind spots. So far as I can
38 > tell, Pango maintains no record of whether a font is monospaced or
39 > proportional. (I believe the X11 backend to pango reads this
40 > information when it queries the X server for available fonts, but then
41 > throws it away.) I presume this has something to do with its failure
42 > to provide correct metrics for Lucida Typewriter. I presume, too,
43 > that it has something to do with the removal of the "filter" mechanism
44 > on the GTK font selection dialog between 1.2 and 2.0. That is, you
45 > used to be able to specify that the font selection should show only
46 > monospaced fonts (rather essential for terminal/console type
47 > applications) but you can't any more -- I guess, because pango has no
48 > notion of what's a monospaced font and what's not.
50 Give us code that can distinguish reliably between monospaced and
51 not-monospaced fonts for Type1 and TrueType fonts and at that
52 point it becomes reasonable to think about such an API. It's
53 not all that easy to do.
55 Even then, there are still problems - Pango by default will
56 draw characters not in the main font using fallback fonts --
57 whose metrics almost certainly don't match your grid. So,
58 you'd have to be able to turn this off.
60 - we have to remove GUI prefs which are not useful anymore, such as the
61 tree line style and tree expander style. Those two items aren't
62 settable in GTK+ 2.0's new tree view widget, as the GTK+ developers
63 consider them per-user preferences rather than items that should be
64 set by individual applications.
67 - double click on item in protocol tree doesn't expand or collapse its
71 - the spacing between lines in the tree view is too big ;
73 - merge gtk and gtk2 directories. Create a gtk12 directory if necessary.
76 - replace gtk_signal_xxx function with g_signal_xxx equivalent. The GTK+
77 2.0 documentation says :
78 The GTK+ 2.0 signal system merely proxies the GSignal system now. For
79 future usage, direct use of the GSignal API is recommended.
82 - gdk_font_from_description() may return NULL. It would be better to use
83 pango and drop GdkFont (and functions which use it, like
84 gdk_string_width, gdk_draw_string).