Page 2 of 2 FirstFirst 12
Results 21 to 24 of 24

Thread: We'll need a QT Jambi section!

  1. #21
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    33,359
    Thanks
    3
    Thanked 5,015 Times in 4,792 Posts
    Qt products
    Qt3 Qt4 Qt5 Qt/Embedded
    Platforms
    Unix/X11 Windows Android Maemo/MeeGo
    Wiki edits
    10

    Default Re: We'll need a QT Jambi section!

    Quote Originally Posted by miketech View Post
    And I favor Java over Python
    Poor you Maybe you'll walk out of darkness one day.

    Ok, I know the API of Qt, but there are many things in Qt I don't need again, because I have them already in Java.
    Java is only a language and provides only the basics. Correct me if I'm wrong but things like SWING are not part of the language specification but rather an external component (a framework, like Qt is).

    In C++ it makes sence, because the standard doesn't offer many technologies. But in Java I already have sockets, threads, xml parsing ...
    Many things will work better/faster than using "native" (look above) Java components, as a big part of them is compiled into binary and not interpreted. Apart from that, you can easily port C++/Qt code into QtJambi code and have a working Java-based application. Try "easily" porting SWING based code to C++.

  2. #22

    Default Re: We'll need a QT Jambi section!

    Quote Originally Posted by wysota View Post
    Poor you Maybe you'll walk out of darkness one day.
    Personally I like strongly typed programming languages. And if I wanna use a scripting language I favor ruby over python

    Java is only a language and provides only the basics. Correct me if I'm wrong but things like SWING are not part of the language specification but rather an external component (a framework, like Qt is).



    Many things will work better/faster than using "native" (look above) Java components, as a big part of them is compiled into binary and not interpreted. Apart from that, you can easily port C++/Qt code into QtJambi code and have a working Java-based application. Try "easily" porting SWING based code to C++.

    Hm, java isn't interpreted.

    Imho it is only a matter of choice. Let's see what the future brings.

    Greetings

    Mike

  3. #23
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    33,359
    Thanks
    3
    Thanked 5,015 Times in 4,792 Posts
    Qt products
    Qt3 Qt4 Qt5 Qt/Embedded
    Platforms
    Unix/X11 Windows Android Maemo/MeeGo
    Wiki edits
    10

    Default Re: We'll need a QT Jambi section!

    Quote Originally Posted by miketech View Post
    Hm, java isn't interpreted.
    Oh, really? That's something new... What CPU family do you use? AFAIK no current processor familiy runs java code natively - they all need a virtual machine... But hey, that's great news, if that's true maybe java applications will move from TurtleSpeed mode to CheetahSpeed mode soon!

    Sorry for being ironic

  4. #24
    Join Date
    Mar 2006
    Location
    Mountain View, California
    Posts
    489
    Thanks
    3
    Thanked 74 Times in 54 Posts
    Qt products
    Qt3 Qt4 Qt/Embedded
    Platforms
    MacOS X Unix/X11 Windows

    Default Re: We'll need a QT Jambi section!

    Quote Originally Posted by miketech View Post
    Hm, java isn't interpreted.
    Neither is it native code. It's compiled into byte code which must be run a virtual machine. Even with the JIT compiler, most of the program is still byte codes being interpreted in the virtual machine. You simply can't get the performance with Java that you can with native code.

Similar Threads

  1. Highlighting selected section on QDateTimeEdit
    By Yorma in forum Qt Programming
    Replies: 4
    Last Post: 3rd May 2013, 12:03
  2. QListView and column moving
    By gadnio in forum Qt Programming
    Replies: 10
    Last Post: 5th January 2006, 17:13

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide.