Linked by Eugenia Loli on Fri 7th Dec 2007 06:25 UTC, submitted by poundsmack
Qt Jambi ships as a single Java library, or JAR (Java Archive) file, plus a handful of tools, including an interface layout and design tool, and an Eclipse plug-in. Trolltech uses its vaunted Qt C++ library as the GUI engine and puts Java wrappers around it. This approach uses the JNI (Java Native Interface) to call the necessary functions from Java. More here.
Thread beginning with comment 289432
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[13]: Unconvinced
by mikeurbandz on Fri 7th Dec 2007 21:49 UTC in reply to "RE[12]: Unconvinced"
mikeurbandz
Member since:
2007-10-29

> a lot better lately with Java 6. However it still
> seems like it's an addon, rather than
> built-in functionality.

It is an addon right now. It's scheduled to become part of the the Java core at some future date. But right now, it's a SwingLabs project. SwingLabs is always a good thing to watch. It's sort of an open source community driven playground for new desktop development features that have a chance of becoming part of the Java core once they mature enough. There's a lot of nice components and such you can get from from SwingLabs, things like tree tables, find/search components, etc.

As far as Java applications feeling sluggish, more often than not, that can be blamed on the programmer of the application not understanding the Swing threading model, or other things (not understanding that Strings are immutable for example, so they use a String instead of a StringBuffer (which is mutable) in a loop, and then end up creating and destroying thousands of objects for example).

> I'll have to look into those. If they don't
> impact the exe size too badly it would be great
> to try them out.

Well, they do impact the exe size significantly, because they bundle the interpretor within the exe. But then again, if you are currently statically linking Qt, your exe files are probably huge anyway.

Another thing to be aware of, is that py2exe doesn't actually produce native code. It just bundles the Python source inside an exe with an interpretor that runs in. In other words, if keeping your source is a secret, it's a problem. Cause anyone who knows how to take an exe apart can get at the original python source.

Reply Parent Score: 1

RE[14]: Unconvinced
by leos on Fri 7th Dec 2007 22:01 in reply to "RE[13]: Unconvinced"
leos Member since:
2005-09-21

Well, they do impact the exe size significantly, because they bundle the interpretor within the exe. But then again, if you are currently statically linking Qt, your exe files are probably huge anyway.


Yeah that's more or less unavoidable. My install files tend to be on the order of 3 to 4mb for Qt apps on Windows.

It just bundles the Python source inside an exe with an interpretor that runs in. In other words, if keeping your source is a secret, it's a problem.


Yeah that's not a problem for me. For vertical markets that kind of stuff is usually less important (I've even done contracts with the open source version of Qt. Commercial does not necessarily mean closed source). Same with anti-piracy measures. It's not worth my time to put a lot of effort into that.

Reply Parent Score: 2