Community
Participate
Working Groups
IMHO, the solution to bug #4460 is to copy all of the java.awt shape classes into org.eclipse.swt.graphics, reproducing all of the functionality that those classes provide. It would be ideal if the SWT shape classes were compatible with the Java2D classes, but I understand there may be reluctance to introduce dependencies on the java.awt classes. Perhaps the org.eclipse.swt.graphics shape classes could, like java.awt.Point and so on, extend the java.awt.geom shape classes. This would serve to allow better integration with Java2D, with introducing a dependency on the java.awt *widget* layer. The java.awt.geom classes are purely model layer, and device-independent. The SWT classes can then adapt those model classes to SWT's device concept.
Your best chance of making this happen, is to 1) spec something 2) spend *several* rounds of review with the SWT committers bashing this into the shape it *must* have in order to be consistant with the rest of the SWT API 3) implement this spec 4) contribute it to eclipse.org At this point, assuming that there is no undue overhead, and there are implementations on all (or at least most) of the supported platforms, you would have some chance of getting it included in SWT.
Also further comments in bug 4460.
Moving from Later.
Not a priority.
SSQ, I don't think we are going to do this, especially now that we have interop with AWT/Swing working. Please close as WONTFIX if you agree.
Closing.
