Is it a good idea for me to use Qt Jambi in Java as a toolkit?
I see that Qt Jambi is hard to learn, and Swing is easier than Qt Jambi, but I think that Qt Jambi is more powerful.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it a good idea for me to use Qt Jambi in Java as a toolkit?
I see that Qt Jambi is hard to learn, and Swing is easier than Qt Jambi, but I think that Qt Jambi is more powerful.
Two years ago, I started a Java Desktop Application and used Swing as a GUI framweork. Up to that point, I had experience with C++/MFC (shudder) and C++/Qt (very nice).
After trying to get along with Swing for a while (including reading lots of tutorials and even a book) I came to the following conclusion:
Swing is much more difficult and clumsy than Qt for three reasons:
I then threw away the Swing GUI, switched to Qt Jambi and was really impressed by it. One weekend later I had a nice Qt GUI and lived happily ever after.