[Interest] Bounties?

[maitai]

If an app needs to be qml for mobile and qwidgets for PCs, then the 
whole concept of portability is broken.

As far as we are concerned, we used QWidgets for mobile deployment too, 
without too much troubles. At least it's the same code (with a few 
#ifdef, ok) for all platforms.

We have our share of bug-reports being let's say postponed forever as it 
seems, but that's life and most often there is a way to turn-around the 
problem, or to fix the issue in qt directly.

Just my 2cts,
Philippe Lelong

Le 12-03-2015 10:31, Bo Thorsen a écrit :
> Den 12-03-2015 kl. 10:15 skrev md at rpzdesign.com:
>> Bo:
>> 
>> I am quite shocked.
>> 
>> Is 5.4.1 QML so buggy as to be un-usable for mobile development?
> 
> No, it's not unusable. I said the quality is way lower, that's 
> certainly
> not the same as unusable. In the Qt community we're spoiled with 
> quality
> that's so far above the rest of what's out there, so when QML based
> applications are only as good as the rest, then it's bad compared to 
> the
> rest of Qt.
> 
>> Is the 5.4.1 mysql support so unstable as to be un-usable?
> 
> ?? I have used this for several customer projects without any problems.
> Why would you ask this?
> 
>> Are you saying that widgets is STILL the way to go for mobile in 
>> 5.4.x+?
> 
> No. For mobile I would only use QML. For embedded applications, it's a
> harder question and depends on the target application.
> 
> I'm right now working on a desktop application implemented in QML. To
> implement this in QML was a mistake that's now impossible to correct. 
> It
> would have been better with widgets.
> 
> The only part of QML (or Qt) that's IMHO unusable is the desktop 
> components.
> 
>> Does Viking software survive in 5.4.x + only via Enterprise support?
> 
> No. Viking Software is a Qt consulting company. I have 18 years of Qt
> coding experience. Support is not required :)
> 
>> Are the reported bugs really not getting fixed in any timely fashion?
> 
> Some are, some are not. That's the way it is with open source projects.
> If you need a bug fixed, get support from Qt Company or fix it yourself
> or hire one of us consultants to do it.
> 
> Bo.
> 
> 
>> On 3/12/2015 1:36 AM, Bo Thorsen wrote:
>>> Den 11-03-2015 kl. 21:36 skrev Bernhard:
>>>> I did not say that we *cannot* continue with Qt. What I say is that 
>>>> it gets
>>>> more painful and difficult.
>>>> For our current projects there are no options anyway.
>>>> 
>>>> But there may be projects in the future at other companies where I 
>>>> will get
>>>> asked again "What would do you think about Qt?". And I will need to 
>>>> say:
>>>> "Years ago I had the impression that quantity and quality are at an 
>>>> optimal
>>>> balance but this changed in my opinion". What a pity. However if 
>>>> enterprise
>>>> support actually improves this then at least for mid-size and bigger
>>>> companies this not a problem.
>>>> 
>>>> I started using Qt with 4.0.0 and pretty much fell in love with 
>>>> it... seems
>>>> my cutie is letting itself go ;-)
>>> 
>>> I know how you feel. And I started with 0.4 :)
>>> 
>>> However, since 5.3 it's improved a lot. QML is still buggy to a point
>>> where it's quality is way lower than the rest of the system. But Qt
>>> itself (for widget based applications) in 5.3 and 5.4 is IMHO almost 
>>> as
>>> good as 4.8. IIRC, I think it was around version 4.3 or 4.4 before I
>>> started to really push Qt 4 to my customers. Qt 5 is following in 
>>> much
>>> the same curve, although the changes from 4 to 5 were less disruptive
>>> than from 3 to 4 so the comparison might not be fair.
>>> 
>>> I think Qt Company is doing a good job of improving the 5 series one
>>> release after another.
>>> 
>>> Bo Thorsen,
>>> Director, Viking Software.
>>> 
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>> 
> 
> Bo Thorsen,
> Director, Viking Software.