Community
Participate
Working Groups
I couldn't find a plan item for 4.2/3.8 so I'm creating one. Apologies if this is a dupe. GTK+ 3 is out: http://blogs.fedoraproject.org/wp/mclasen/2011/02/10/gtk-3-is-here/ http://ftp.gnome.org/pub/GNOME/sources/gtk+/3.0/ http://library.gnome.org/devel/gtk3/3.0/ I know we can't get rid of GTK+ 2.x support entirely, but it would be good to move to GTK+ 3.x where possible. Ideally one could build and run with an entirely GTK+ 3.x stack. This may also allow removal of some of the GNOME dependencies that SWT has at present.
+1, this would be nice
Is there any progress on this ?
This is not currently in the plan for Eclipse Juno (4.2). Some progress towards this goal is being planned, covered by bug 354978.
We (Red Hat Eclipse team) plan to look at this port. Initial plan is to make swt compile against gtk 2.24 without deprecation warnings(removed in gtk3) using the following rules: * there is a suitable replacement for the api in gtk 2.4.1(the minimum version required by eclipse) - drop it from OS.java and the codepaths elsewhere that use this OS.* calls. They are always guarded by OS.GTK_VERSION < OS.VERSION( 2, 4, 0) or even older gtk version so we should be pretty safe with this. * there isn't a suitable replacement in gtk 2.x where x>=4 - make the function binding dynamic. Bug reports(patches) will block this one effectively making this bug a tracking one. If someone wants to help with the effort feel free to say so here.
Ongoing work rowards building with gtk 2.24 without too many deprecated issues is available in http://fedorapeople.org/gitweb?p=akurtakov/public_git/eclipse.platform.swt.git;a=summary old_gtk_kill branch.
Hi Alex, thanks for your patches. I am going to review them. Please could take a look at http://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions and add the disclaimer in step four here.
(In reply to comment #6) > Hi Alex, thanks for your patches. I am going to review them. Please could take > a look at > http://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions and > add the disclaimer in step four here. I wrote all this code and have the rights to contribute it to Eclipse under the eclipse.org web site terms of use. It's enough to do it once here, right? Or I should do it in every bz ?
(In reply to comment #7) > I wrote all this code and have the rights to contribute it to Eclipse under the > eclipse.org web site terms of use. > > It's enough to do it once here, right? Or I should do it in every bz ? I think just doing it once is fine, since you are doing a large number of small commits as part of this single plan item. We may move to Gerrit later in the year, in which case we'd get rid of this awkward process.
Can we mark this fixed now?
(In reply to John Arthorne from comment #9) > Can we mark this fixed now? I think we should keep this open as we're still in the process of fixing some bugs for GTK+ 3. We can probably close this bug after the Luna release (by which time the GTK+ 3 port should be supported fully and all the pending bugs this bug is dependent on should get resolved).
Created attachment 238221 [details] N20131207 is not usable under gnome 3.10 I have downloaded today eclipse-SDK-N20131207-1500-linux-gtk-x86_64.tar.gz to test how the gtk3 support works. But the windows within eclipse remain white and the text is also not viewable as seen on the attachment. What can it be?
(In reply to Lado Kumsiashvili from comment #11) > Created attachment 238221 [details] > N20131207 is not usable under gnome 3.10 > > I have downloaded today eclipse-SDK-N20131207-1500-linux-gtk-x86_64.tar.gz > to test how the gtk3 support works. But the windows within eclipse remain > white and the text is also not viewable as seen on the attachment. What can > it be? It seems to be an issue when running with the newest GTK 3.10 (pls see Bug 423420).
(In reply to Arun Thondapu from comment #10) > (In reply to John Arthorne from comment #9) > > Can we mark this fixed now? > > I think we should keep this open as we're still in the process of fixing > some bugs for GTK+ 3. We can probably close this bug after the Luna release > (by which time the GTK+ 3 port should be supported fully and all the pending > bugs this bug is dependent on should get resolved). I'm marking this bug as fixed now as this was the plan item for GTK+ 3 support which is enabled by default in Luna for GTK+ versions prior to 3.10. There is still some pending work to be completed for the GTK+ 3 port, primarily to fix issues that have cropped up in more recent GTK+ versions like 3.10 and later. All the outstanding GTK+ 3 related bugs will now be targeted for Luna SR1 (4.4.1).
