This may be suitable for your plugin, but it's hardly a workaround
for the SWT bug itself. You're talking about launching a separate
JVM and using RMI to communicate between the SWT and Swing apps.
You'll still have two apps, two menu bars, etc. and you won't have
the ability to embed Swing in SWT that you get on other platforms for
free. This plagues a lot of graphical tools for the Eclipse platform,
and it sure would be nice to know if Apple engineers are working on
this.
In any case, good luck with your project! Let us know how you make out.
- Erik Mattheis
email@hidden
On Aug 20, 2005, at 12:12 PM, Jose Cornado wrote:
So? Did I say: I am going to use the debugging api? :-}
I am just pointing out a possible way how eclipse's bug 67384 can
be worked around.
The eclipse-debugging-a-jframe is a valid general case of the dual
process idea that I had. BTW, it is not original because it has
been in front of everybody all the time.
I just wanted to see if somebody else did something similar to get
around bug 67384.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
