[Development] Qt for iOS - iOSStyle

André Pönitz andre.poenitz at mathematik.tu-chemnitz.de
Mon Mar 11 23:02:02 CET 2013

On Mon, Mar 11, 2013 at 01:38:28PM -0700, Thiago Macieira wrote:
> On segunda-feira, 11 de março de 2013 19.45.48, André Pönitz wrote:
> > On Mon, Mar 11, 2013 at 08:37:19AM -0700, Thiago Macieira wrote:
> > > On segunda-feira, 11 de março de 2013 07.41.02, Jake Thomas Petroules 
> wrote:
> > > > Jens claimed on the blog that the native look and feel matters less in
> > > > the
> > > > mobile world because each app is fullscreen. I agree that it matters
> > > > less,
> > > > but I disagree that it matters little enough for us to ignore it. I'd
> > > > much
> > > > rather use real iOS-looking controls than simply slap on Fusion.
> > > 
> > > The whole point is that you shouldn't use QtWidgets at all on mobile
> > > platforms. Just don't.
> > 
> > The point is that the current alternative is far from perfect as well.
> Indeed, but the current solution is not an option either. QtWidgets will not 
> get the full look and feel of iOS. It was not meant to do animations and the 
> effects required by their L&F.
> So we have no solution at this point. And I'd argue that QtWidgets will not 
> ever be good enough, whereas the Qt Quick solution can be.
> > Combined with the insight that the "old" widgets don't cut it in the
> > animated touch space and there's no resources to maintain two stacks
> > one might have expected a single, fully compilable stack with optional
> > script bindings on top as primary goal.
> If that's possible, sure.

Why shouldn't it be possible to have a clearly layered stack with
proper interfaces?

> But it's possibly even easier to write a single 
> Qt Quick-based solution, with no C++ API.
> Given the lack of manpower, that's an alternative to consider.

I am not sure I understand what this alternative would consist of.

A solution that pushes common activities that can be done at compile
time to every user's run time is not an approach that scales well
outside the "Mobile App" comfort zone the current incarnation of Qt
Quick is addressing. It does not scale down to "real" embedded, and
it does not scale up to the usual bunch of engineering applications
Qt was serving well in the past.


More information about the Development mailing list