And I want to add that Qt C++ platform independency works better than SWT, for example SWT can do combo-box with both checkbox and image on windows but can't do the same on linux - image is not visible. And few more issues can be found in XMind on windows/linux. While Jambi can do it on all platforms in the same way.
On Wed, Apr 22, 2009 at 2:38 PM, Tom Schindl <[email protected]> wrote: > Hi, > > They do both the same my making JNI calls to native C++ libraries > whereas on QTJambi the platform independency is done at the C++ level by > their QT-libs whereas in SWT this is done partly at the SWT/Java level. > > Another interesting difference is that QTJambi uses the Java Grabage > collector so you don't need to dispose things but simply let them go out > of scope you'll have to dispose things in SWT. > > Tom > > Luca Ferrari schrieb: >> Hi all, >> I wonder how the jambi works and how it compares to swt (sorry if the >> question >> is trivial). I mean, qt are written in c++, and maybe jambi makes the same >> swt >> does: it uses jni to call c++ native libraries. Is it true or jambi exploits >> a >> kind of swing approach, where components are emulated on a peer set of native >> components? >> Any pointer to a discussion/explanation of the above? >> >> Thanks, >> Luca >> _______________________________________________ >> Qt-jambi-interest mailing list >> [email protected] >> http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > > _______________________________________________ > Qt-jambi-interest mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
