It's years that Creating TreeTables in Swing articles are there even before JDK 1.2, when Swing/JFC was not a core library yet. But I'm just in wonder why anybody in Sun doesn't care to integrate and add such support directly into the core while SWT has already added from the day one. Is it that hard? While it's just a trivial addition from JDK/JRE size/volume point of view, it will have a great effect from component enrichment point of view...
It's a real crap!! I'm not gonna add the TreeTable source codes or the binary form (as library) to every project making use of this component!
Should we wait another 1.5 year or so to see this integrated in the core (JDK 1.6??)? Or we still have the chance to see this feature on JDK 1.5?
Armond
Posted by armond at March 13, 2004 02:32 PMJDK 1.5 is in feature freeze and has been since the first beta. Tree tables won't be in 1.5 but maybe if people try hard it would go into 1.5.1 (but I doubt it, Sun doesn't seem to care about Swing anymore).
Posted by: Keith Lea at May 5, 2004 12:37 AMWell, the philosophy behind the Swing framework is totally different both from developer and end-user point of view. AWT components are exactly the native heavyweight ones exist on the platform you're using, thus not possible to change their L&F as the OS itself draws them. And because of the same reason, faster than Swing components.
As a side note, I would like to mention the SWT components. They're more like the AWT components as they have native implementation on most of the major platforms (thus you have the speed!). As well you can somehow have a skin on them like Swing components and far more flexible than AWT (which are very limited for customization).