Thanks for your post Ricky.
> Swing is already more than capable of using a Win32 window itself:
>...
> As of Java 6, on Windows components are rendered using the native OS'
> renderer (true at least for Windows and GTK, afaik), and Java has
> supported native windows (as above) for years and years.
I guess the description of my task was not complete enough to convey a
precise idea of where this is supposed to lead:
Eventual combination of Windows native and Java Swing UI elements in
the same Window that a Windows native app started.
My mini-project is not about performance issues with Java UIs.
I'm venturing into this land of UI/JNI madness to evaluate in how far
it is possible to integrate multiple distinct Java and Win C++ UI-bound
programs under one UI hood, without having to rewrite or re-implement
any significant portions of the existing code.
> SWT provides access to native components more directly.
As for SWT, I am aware of what SWT is and how it goes about rendering,
utilizing native counterparts for its widgets. From what I know though,
it does not combine Swing (well it actually does not touch Swing at
all, right?) and native UI elements in a window.
> Your research sounds like a wheel reinvention.
Well I hope you still think this way after the clarification of what
I'm set out to look into and can provide me with pointers to material
dealing with similar issues.
Andrew Thompson - 05 Sep 2006 11:00 GMT
....
> Well I hope you ..
(do not)
>..still think this way after the clarification of what
> I'm set out to look into and can provide me with pointers to material
> dealing with similar issues.
The only way that sentence made sense was to presume
you forgot to add the words 'do not'..
(BTW - I cannot give any better information than the
group of people who have already decided to contribute
posts to this thread, they seem a lot more knowledgable
about this area than me.)
Andrew T.
Mustafa K. Isik - 05 Sep 2006 11:16 GMT
> ....
> > Well I hope you ..
[quoted text clipped - 7 lines]
> The only way that sentence made sense was to presume
> you forgot to add the words 'do not'..
I did actually mean what I wrote :)
Presuming Ricky is right and I am working on something that has already
been solved, I would be very happy to benefit from prior work and
proceed with other matters. Btw, this "research" project of mine is not
supposed to yield material for a software engineering paper, it is a
very practical problem that I'd like to see solved rather sooner than
later :)
ricky.clarkson@gmail.com - 05 Sep 2006 11:30 GMT
A possibly-interesting use of SWT is as a Swing implementation -
http://swingwt.sf.net
I think that it would be hard to come up with something general that
can mash together a Swing user interface and a native one; for a start
there would be layout issues.
Swing also does not even play very nicely with AWT components.
Maybe a good starting point would be to take one C/C++ app that you
have the source for, and one Java app that you have the source for, and
merge them. Time yourself, and then evaluate the usefulness.
Of course, you should start with a hello world mash, then move to what
I said above.
A more interesting approach might be to convert Java GUI code to C++,
or vice-versa, or both to another representation, e.g., .NET.
Whatever you decide on, good luck. You'll need it. It's ugly in dem
der GUI toolkits.
> > ....
> > > Well I hope you ..
[quoted text clipped - 16 lines]
> very practical problem that I'd like to see solved rather sooner than
> later :)