[Interest] Fwd: Which "Widget" technology to use when starting a new desktop app

[Tim O'Neil]

This. (What Bob said, but I would carry it to another level.)

Its a toolbox. Use the tool for the job. Often its Qt, but I once worked on
a team that was mandated to create a UI that would work on Windows, OSX,
Gnome, and KDE. And the client wanted minimal third party and external
tools. The solution? HTML5 with an embedded web server in STL. Built a
package for each platform and Joe's your mother. (There was some external
tool installing but we kept that completely under the covers.)

"Why use Ada when we can use Lisp? Well, why Lisp if we have python? Why
use python when you can use Perl? Ok, why perl when you have bash? We'll
write our app in bash."


On Thu, Jan 5, 2017 at 7:29 AM, Bob Hood <bhood2 at comcast.net> wrote:

> On 1/5/2017 8:03 AM, Jason H wrote:
>
>> The mantra is to use QML.
>>
>
> I just wrote a wonderful utility using Qt 5.6.2 and Widgets for the
> desktop, and there's no hint of QML in it.  It functions beautifully, is
> easily maintainable, and even has full animations.
>
> I don't think the mantra is QML.  The mantra is: Look at your need, your
> goal, and choose the Qt technology that best fits it. If that's QML, fine.
> If that's Widgets, fine.  Unless Qt reps step up here and support your
> statement (which will have ramifications for me and, I'm sure, many
> others), summarily stating to somebody that they should use QML as the
> primary tech for a new desktop app is, I think, dogmatic, at best, and
> continues to fuel the anxiety that Qt is pouring all the love into a
> QML/mobile focus.
>
> Just my $0.02.
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20170105/3df510ed/attachment.html>