I know that JDNC project have our treetable swing component. But my question is...
Already would not be in the hour of the Swing to have native support for a treetable component?
SWT performance is just unacceptable when compared to Swing, I am afraid.
not in general - it depends mainly on the underlaying toolkit, so if Sun would implement AWT on top of GTK2 we would see almost identical (or even worse) performance.
Since SWT does not more or less than wrapping calls to a native toolkit SWT has almost no impact on performance ;)
Especially the big inconsistency itself and the least-common-determinator implementation is quite a big problem.
No one addressed the original poster's topic!
> I know that JDNC project have our treetable swing
> component. But my question is...
> Already would not be in the hour of the Swing to have
> native support for a treetable component?
It is good to have folks like you around!
The major benefit we gained with a lightweight library is the ability to insert new componentry into the library -- we don't have to depend on native support for widgets to see them appear.
However, I would not at all stand behind incorporating any of the implementations that I've seen, which are really just trees inside of tables. This is a specious component. It needs to be composed from scracth and have a sensible API and model. Perhaps you know of another.
I was searching around for treetable also. Sun has it's own example http://java.sun.com/products/jfc/tsc/articles/treetable1
I agree with steevcoco that add another library may not be wise. hope there are more example on this later on.
I think it's a big mistake to ignore AWT for such a long time. With every minor change in the gui of a supported os, swing needs an update (after serveral month).
Look at SWT ... shame on you ...
Well I take a look at AWT and see all those problems this crappy toolkit cause, many wasted developer hours since of inconstistencies and bugs. And that with such a simple toolkit as AWT!
Since Tiger (1.5) AWT is even implemented almost as lightweight as Swing on Unix-platforms because SUN did not want to waste any time writing another native implementation and it works better than the Motif based predecessor.
Furthermore I take a look at SWT and what do I see:
- terrible performance on Linux/GTK2
- so and so performance + Threading problems on OSX
- inconstistencies across all platforms
- windows features hard-wired in the API (like the FLAT-Syte property for creating widgets in windows-web lookandfeel)
- bugs, bugs, bugs ... most of them are only fixed if they cause problems for eclipse.
I don't know wether this is the way you like it but for me it is definitivly not. On windows its not that bad choice (I guess you're one of those users not really experienced in cross platform development), but as soon as you need it for different systems it starts to be horrible.
Furthermore it has some really brain-dead limitation to support all native toolkits supported today,
Thats it, just my opinion.
Message was edited by: linuxhippy
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.