Issue 111952 - vcl: Get ready for gtk3
Summary: vcl: Get ready for gtk3
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: DEV300m79
Hardware: All Unix, all
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2010-05-31 09:34 UTC by caolanm
Modified: 2013-03-28 23:17 UTC (History)
3 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---

gtk3 changes (21.04 KB, patch)
2010-05-31 09:34 UTC, caolanm
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description caolanm 2010-05-31 09:34:15 UTC
gtk3 is coming. Mostly appears to be gtk2 with all deprecated apis removed.
Attaching initial port to get started
Comment 1 caolanm 2010-05-31 09:34:38 UTC
Created attachment 69724 [details]
gtk3 changes
Comment 2 caolanm 2010-05-31 09:35:39 UTC
hanging onto this one
Comment 3 philipp.lohmann 2010-05-31 17:04:24 UTC
This is really nice. I think we'll want to be able to build gtk-2.0 and gtk-3.0
plugins in parallel. For once like the KDE3/4 conversion there will probably be
a time of choice between the new/old Gnome version. And there are some old
platforms to keep in mind where will still want to be able to built gtk-2.0
support. So I'd like to suggest making this change so that we there are e.g.
separate directories for gtk2/3 in vcl (and where else this later on matters
like fpicker) as well as have separate config options (like for KDE where there
Comment 4 caolanm 2010-05-31 20:16:46 UTC
It would be rather horrible to duplicate the dirs because as far as I can see so
far gtk3 isn't really different to gtk2 except that what used to be deprecated
is now totally gone and immediately after a dup they're going to fall out of
sync and cause misery. Though I take the point we would ideally want to be able
to build gtk2 and gtk3 versions side by side for a while. There is a (much
unloved) in sal which builds two versions of a .so from the same
source which might be an acceptable solution.

What I'd like is to simply first get what version of gtk2 is the Hamburg
baseline ? We could simply replace any calls deprecated since that baseline with
their modern equivalents, e.g. some are deprecated right from 2.0.1. 
Comment 5 philipp.lohmann 2010-06-01 10:03:21 UTC
What RelEng seems to use for building is gtk 2.4.1 (. As for the plugins going
out of sync: true, but part of that would be on purpose wouldn't it ? I guess
gtk-3 will continue developing and the gtk3 will need/want to, too. I ceratinly
understand your point about duplication, but are you sure that that special
makefile is going to be available when build-2.0 comes around (especially since
you say it's "unloved").
Comment 6 caolanm 2010-06-16 16:15:01 UTC
committed to gtk3
Comment 7 Pedro Giffuni 2013-03-28 17:57:08 UTC
This was never merged.
Comment 8 Ariel Constenla-Haile 2013-03-28 23:17:36 UTC
(In reply to comment #7)
> This was never merged.

The CWS looks with more stuff than the patch attached here: