Gtk+3.0 support

1 view
Skip to first unread message

Massimo Corà

unread,
Oct 19, 2010, 5:53:05 PM10/19/10
to scintilla-interest
Hi all,

I was wondering if you've planned to support gtk+3.0 into Scintilla
development.
Anjuta has a Scintilla plugin but being its dependence set to gtk+3.0
I see some problems maintaining it.

thanks and regards,
Massimo

Neil Hodgson

unread,
Oct 19, 2010, 11:21:58 PM10/19/10
to scintilla...@googlegroups.com
Massimo Corà:

> I was wondering if you've planned to support gtk+3.0 into Scintilla
> development.
> Anjuta has a Scintilla plugin but being its dependence set to gtk+3.0
> I see some problems maintaining it.

As of release 2.21, Scintilla does not use any GTK+ 2.20 deprecated
APIs when compiled with the DISABLE_GDK_FONT option turned on. For
GTK+ 2.22, there are about 30 deprecation errors. While I will
probably work on the deprecated calls at some point, it would help if
others were to work on fixing these.

I personally don't use versions of GTK+ until they turn up in a
release of Fedora or Ubuntu. However, I am willing to incorporate
changes for GTK+ 3.0 compatibility. As Scintilla needs to support
older versions of GTK+, there may need to be conditional compilation
of variants for different GTK+ versions. I have mostly been trying to
stay compatible with GTK+ 2.8 although some fixes have recently been
made for 2.4.

Neil

Neil Hodgson

unread,
Oct 20, 2010, 8:37:39 PM10/20/10
to scintilla...@googlegroups.com
Looks like GTK+ 2.22 deprecates the gdk_* calls in favour of cairo
so this will be a major change and unlikely to be completed for
Scintilla 2.22. Committed change that fixes all of the widget flag
deprecations except for GTK_HAS_FOCUS which wasn't obvious.

Neil

Massimo Corà

unread,
Oct 25, 2010, 6:13:20 PM10/25/10
to scintilla-interest
Hi,
indeed the gdk_* calls were the ones that worried us most.
I hope you can deal with them without too much pain.

thanks and regards,
Massimo

Neil Hodgson

unread,
Oct 26, 2010, 6:13:33 PM10/26/10
to scintilla...@googlegroups.com
Massimo Corà:

> indeed the gdk_* calls were the ones that worried us most.
> I hope you can deal with them without too much pain.

Cairo uses antialiased drawing so there will be differences. Some
will be improvements but there will probably be some effects that do
not look as good or do not suit some users. Using GDK with Cairo works
well in some directions as Cairo can wrap a GDK drawable but not the
other way as a cairo_surface_t is not a GDK drawable.

Neil

Reply all
Reply to author
Forward
0 new messages