[Qt-interest] Qt future ...

[Jason H]

#1: Adobe AIR.
Distant second: Java.

Then there all re re-tooled approaches of thin native clients/thick servers, but 
that paradigm is not often used by traditional fat client developers. It is fine 
for the mode/view but the controller part can be problematic. Usually it gets 
split between client/server, and the parts are completely different 
technologies.




----- Original Message ----
From: Paul Miller <paul at fxtech.com>
To: qt-interest at qt.nokia.com
Sent: Thu, April 28, 2011 8:49:06 AM
Subject: Re: [Qt-interest] Qt future ...

On 4/28/2011 7:24 AM, Duane wrote:
> On 4/27/2011 6:48 AM, Thiago Macieira wrote:
>> Em Wednesday, 27 de April de 2011, às 12:29:02, QtNext escreveu:
>>> I don't wants to restart the big thread from March after the bad news
>>> ...  But just wants to know if some good news (Thiago says that we don't
>>> know all about that ...) are coming for Qt :
>>
>> I'm not going to discuss this with an anonymous person.
>
> Most of us have the same questions and aren't anonymous.  We have
> several new products in the planning stage and the question came up
> yesterday whether we should continue with Qt.  We would certainly prefer
> to do so but some indication of future support would be useful.

Seriously, what is the alternative? If you're writing for one platform 
then maybe it's easier but if you have to write for more than one 
platform I don't see a viable alternative.
_______________________________________________
Qt-interest mailing list
Qt-interest at qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-interest