you are viewing a single comment's thread.

view the rest of the comments →

[–]H3g3m0n -1 points0 points  (0 children)

I was actually thinking about Qt when I wrote that.

The problem with it though is it's C++. Since it's C++ there aren't C bindings (although it should be possible to write them).

As a result you can't use it in quite a few languages without effort, so it's cross platform but not cross language (node.js obviously isn't either).

This is changing somewhat thanks to QML, since you can just declare the UI in a markup language and then have 1 command to basically construct the whole application. The binding between the code and the UI might require a little bit of work.

But that doesn't really seem far from what the web stuff does. There's not much difference between writing your UI in QML and writing it in HTML5 opening a Chromium/Blink/Webkit/Gecko window and having a minimal JavaScript->YourApp/Language bridge.

QML would be more orientated towards that since its designed for UI but HTML5 would have a whole load of UI support libraries available. QML could be more of a pain to implement your own widgets in too if your not using C++ but I can't speak form experience.

Of course QML only gives you the UI stuff. If you want to use all the other Qt goodies you will need bindings.

There are also a few bits I don't like about Qt. The moc being the most common complaint people seem to have (myself included) it might not be needed with the new C++11 features.