[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-swt-dev] Swing Integration
|
> If there is integration in the plans, a request (from me at
> least) would be
> that it simply replaces all of the Jxxx classes, so that all you
> need to do
> to port is prepend the SWTSwing Jar - overriding the Java Swing
> classes. So
> the already written applications would suddenly have SWT displays.
One point -- it's not legal to replace the javax.swing.J* classes with
another implementation, per the JRE/JDK license.
One could create a new package with the same class names, and require apps
change their import statements.
I've been looking hard into Swing integration similarly to what you're
asking about. I've been approaching it from using an alternate AWT Toolkit
that uses SWT as peers, which would mean Swing could just be used as is
(though I'd like to replace the J* classes so they'd actually use the native
SWT components and look right in eclipse).
The problem I'm having is being able to pass something
like -Dawt.toolkit=com.javadude.SWTToolkit and have plugins use it.
I've asked a couple of times already, but I'll try again:
Q: Does anyone know how to set the awt.toolkit property so all eclipse
plugins will see it?
-- Scott
==============================================================
Scott Stanchfield scott@xxxxxxxxxxxx http://javadude.com
Lead author of "Effective VisualAge for Java, Version 3"
http://javadude.com/evaj
VisualAge for Java Tips and Tricks http://javadude.com/vaj
AWT & Swing FAQ Manager, jGuru.com
Visit for Java Enlightenment! http://www.jguru.com
==============================================================
