> Low verbosity (as little code necessary to write a functional and reliable UI as possible) and fast learning curve are the most important things.
Qt and Xojo are both real contenders on these points. I would argue that Xojo has a faster learning curve if you already know BASIC but is perhaps much less expressive if you need any sort of complex computer science algorithms or data structures which is where C++ really shines.
Qt's learning curve is "pretty quick" but it of course comes with having to know a decent amount of C++, and possibly javascript, to utilize effectively.
> I just heard you don't really have to use any language other than the Qt's internal ones any more.
Yup absolutely. If it were me and I were building a UI, I would seriously consider Qt's framework. I don't particularly like Qt's framekwork (it still holds a lot of baggage from pre-C++11 days) but I must admit that it's fairly extensive, certainly cross-platform across desktop and mobile operating systems, and has a fairly quick learning curve to use.
Qt and Xojo are both real contenders on these points. I would argue that Xojo has a faster learning curve if you already know BASIC but is perhaps much less expressive if you need any sort of complex computer science algorithms or data structures which is where C++ really shines.
Qt's learning curve is "pretty quick" but it of course comes with having to know a decent amount of C++, and possibly javascript, to utilize effectively.
> I just heard you don't really have to use any language other than the Qt's internal ones any more.
Yup absolutely. If it were me and I were building a UI, I would seriously consider Qt's framework. I don't particularly like Qt's framekwork (it still holds a lot of baggage from pre-C++11 days) but I must admit that it's fairly extensive, certainly cross-platform across desktop and mobile operating systems, and has a fairly quick learning curve to use.