Eddy Petrişor wrote:
On 5/22/06, Sven Luther <[EMAIL PROTECTED]> wrote:
> Having GTKDFB 2.8.17, whose DFB backend is much more stable than the
old
> one found in GTKDFB 2.0.9, available as udeb may allow Etch to be
> released with graphical frontend enabled by default ?
I am not sure, i got the impression that the default choice was not
due to
this consideration, but more about the general maturity of it.
I think that is not the case, iirc, the 2.8 was preffered for the
exact reason of not having to maintain two gtk trees. Every arch
except hurd has libgtk2.0-0 at 2.8.17 while 2.8.16 has migrated in
testing:
For sure dropping unofficial source packages for both Cairo and GTK will
be a great step towards standradization of the g-i, prerequisite for it
to become the default Debian installation frontend, but i also expect
many benefits to come from the adoption of GTKDFB 2.8.17 (and related
stack of updated libraries like cairo and DFB)
-Better stability of the DFB backend: having worked a lot with Mike
Emmel during last months at debugging it, i know how much it has evolved
from the old 2.0.9 times and how many bugs have been fixed.
-Support for RTL text in GTKTreeView, available starting only from GTK 2.2
-Capability to automatically scroll a GTKTreeView to the active row
(broken in GTKDFB 2.0.9)
-Row selection via keyboard for GTKTreeView
-Better text rendering: currently, GTKDFB 2.0.9 tends to mangle some
glyphs in some circumstances
After integrating the g-i into regluar buils, i think moving to updated
libraries from standard trees is the most important thing that has yet
to happen for the g-i to become mature.
fiendly
Attilio
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
