Fabian Steeg <steeg@xxxxxxxxxxxxx>
GEF development <gef-dev@xxxxxxxxxxx>
02/11/2011 05:41 PM
Carbon unsupported platform in Eclipse 3.7
I've been using Cocoa exclusively since it's available
and I think it would make sense both for us and for users to stop supporting
Carbon, resolve the Carbon-only bugs as WONTFIX, remove workarounds, and
throw unsupported exceptions when running on Carbon (to explicitly point
everybody to the better option).
what about the Carbon issue (see below)? There hasn't
been much response to Anthony's inquiry so far...
Am 06.01.2011 um 22:17 schrieb Alexander Nyßen:
as I finally got my hands on a MacBook with Mac OS X Tiger
(10.4.11) I am now able to investigate all Carbon related issues as well
(even if we might decide to no longer support the platform, I think it
would be good to know, which of the currently reported issues still hold
and which workarounds are obsolete by now).
Am 22.12.2010 um 23:17 schrieb Alexander Nyßen:
I think it would be reasonable to announce to no longer
officially support Carbon, as most of the Mac OS X related issues are actually
caused by SWT inconsistencies, and as the SWT team is no longer going to
officially support Carbon, we cannot do much about it anyway. I also see
the problem that (as far as I know) nobody in the GEF team has a Carbon
Mac at hand (I have a Cocoa Mac, which I use for my daily work, so I can
investigate all Cocoa related issues but unfortunately not Carbon), so
we cannot really investigate most of the problems anyway. I tried to obtain
an old Carbon Mac from a working colleague, but unfortunately it got broken
I would not go as far as throwing unsupported exceptions
in case somebody tries to use GEF 3.7 on Carbon (I would say an "as-is"
usage would not harm us), but I think we should resolve the related bugs
as WONTFIX and we should not build in any more workarounds for the Carbon
platform; actually I think we should also remove all existing ones to get
a clean code base again. Probably most of them are related to SWT problems,
which have already been fixed in later SWT releases (e.g. the AWT-SWT-bridge
related issues), so they may not be needed any more anyway. Maybe there
is still a chance of somebody getting a Carbon Mac, so we could investigate
which of them are actually still needed to make a decision about that.
Concerning platform specific workarounds as a whole, I
think we should try to get rid of them anyway. I have already started to
investigate most of the Cocoa related bugs (there are actually not so many;
most were related to broken or missing xor painting, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=332872)
in the last two weeks. I successfully identified related SWT problems for
all that I investigated, and thanks to Scott Kovac of the SWT team, who
very quickly fixed all of them (and also implemented xor painting on the
SWT Cocoa port), they could actually be resolved without the need for any
GEF workarounds. I have also started to investigate the need for the existing
Cocoa related workarounds and I already reverted one for GEF 3.7 (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=303659).
I am pretty sure that we all are aware that Mac OSX Carbon is Unsupported
for Eclipse 3.7. Should we make a formal statement for GEF and Draw2D?
I know we have hard coded work-arounds for Carbon and Cocoa, maybe we should
check for Cocoa only going forward? Should we throw unsupported exceptions
when we detect Carbon?