[Qt-interest] Qt for the iPad?

[Jason H]

Well, I do think that is somewhat of a saving grace. That is, there is little standardization on the iPhone/Pad interfaces. They are designed for touch, which is completely different than mouse, and multi-touch at that. My use of Qt in tablets (old school, laptops with flip screens) showed me that. (You need to set Global Strut Size, at a minimum). 

The more I think about it the more important I think it is to get Qt onto Android/iPhone/Pad devices. If this is the growth sector of computing (and it looks like it is... aka "computers in the bedroom") The only concern I would have is would these few OS platforms just be a flash in the pan, before we transition to full OSs on them? I think it is doubtful because full-blown OSs don't take into battery management and location-awareness to the same degree that these portable OSs have to. Will Qt miss the boat? 

Thiago, you don't have to say anything.I know, numbers vs resources... ;-) 






----- Original Message ----
From: Andrew Hodgkinson <ahodgkinson at endurancetech.co.uk>
To: qt-interest (E-mail) <qt-interest at trolltech.com>
Sent: Wed, April 7, 2010 6:50:03 AM
Subject: Re: [Qt-interest] Qt for the iPad?

On 05/04/2010 22:19, Richard S. Wright Jr. wrote:

> [...] keep a very good separation
> between application logic, and the user interface. Personally, I
> really don't want my iPhone/iPad app to look like an OS X app or an
> Android App, or a Windows CE app, and I don't even think the user
> should "use" them the same [...] Okay, before I get flamed.

On the contrary... I think people who are reasonably or deeply familiar 
with Mac OS X are more acutely aware than most of the issues with 
cross-platform "one size fits all" GUIs. Cross-platform application 
"business logic" can be really useful, but truly successful cross 
platform GUIs are rare. On Windows and Linux, you can kind of get away 
with it because inconsistency is rife and there are few 'unusual' GUI 
features/standards present. On Mac OS, less so. There are issues of 
proper integration with the services menu, AppleScript support if your 
application warrants it and numerous GUI features which have no direct 
analogue in Windows or Linux, such as slide-out drawers, HUDs, icon 
badges, document proxy icons in title bars and many more.

On the iPad, it's likely that the most interesting and successful 
applications will make specific use of device features within the target 
market - its mobility, e-reader like form factor, location awareness, 
that kind of thing. You may well find your application translates poorly 
or not at all to the Desktop; it really only works on a tablet-like 
device, not even doing well on a small mobile phone. So again, we end up 
with the interesting idea of the back-end logic being cross-platform, but 
less interest in the GUI components being cross platform too. As far as 
I'm concerned, an iPad's resources are far too constrained to have to put 
up with a huge chunk of Qt code desperately attempting to mimic the look 
and feel of the native Cocoa GUI components which are already there.

So - an intelligent effort to spot the valuable bits of Qt to port across 
multiple tablet targets: Great idea. Porting the whole lot to iPad and 
trying to make the GUI look and feel native? Ugh :-)

-- 
Andrew Hodgkinson, Endurance Technology
Land line: 01223 369 408, mobile: 07855 866 780
Registered Office: 5 Marine Drive West, Bognor Regis, W. Sussex, PO21 2QA
_______________________________________________
Qt-interest mailing list
Qt-interest at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-interest