Guys,
Note that the Eclipse Installer could help achieve the goal more
selectively, without respinning any packages. I.e., we could add
a so-called Eclipse Ini task to the Eclipse.org product catalog to
set this property into the eclipse.ini. Moreover, we could do it
selectively by specifying a filter (in the same style as is used
by p2) for this task task, and further restricting the task to be
a boot-strap only task so that the user could edit their
eclipse.ini and change it without Oomph setting it back.
I tested using (&(os.ws=gtk)(desktop.session=ubuntu)) to add
"--launcher.GTK_version 2". The intent being to add enable this
task to add the option to the eclipse.ini only if we're installing
on an OS whose window system is GTK and that has an environment or
system property set to this value. At least for my Ubuntu 15.10
installation there is an environment variable
DESKTOP_SESSION=ubuntu that serves this purpose. Certainly
Eclipse is less buggy for me when I use GTK 2.
We'd need to reach some kind of consensus that this is a good
idea.
Regards
Ed
On 06.05.2016 18:06, Bruno Medeiros
wrote:
So I just tried Eclipse Mars.2 in Ubuntu MATE (in a VM)....
It is quite broken - but not if launched with GTK2, with GTK2
it works ok.
With GTK3, it is buggy to the point of being unusable - closing
views leaves a ghost view pane in the workbench page. Certain
dialogs don't work because tree/list contents don't show up, so
you can't select items, etc.
Is this normal? When you mentioned those problems with GTK3 on
Ubuntu I thought it was "just" theming and visual artifact
problems, but that otherwise one could still use the IDE
normally.
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev