On 2013/03/19 1:57 AM, Jake Thomas Petroules wrote:
>
> Not every app should be styled native. Not every app should be styled custom.
> Some should use a combination of both. It all depends on what's appropriate
> for the situation at hand. All I'm asking is that people recognize that we
> need
>
On segunda-feira, 18 de março de 2013 19.57.41, Jake Thomas Petroules wrote:
> On Mar 18, 2013, at 8:26 AM, Mediator Software
wrote:
> > In "the real world", Qt on iOS is being used primarily to port existing
> > QtWidget applications to the iPad, not to write new ones (nor to do
> > anything on a
On Mar 18, 2013, at 8:26 AM, Mediator Software
wrote:
> In "the real world", Qt on iOS is being used primarily to port existing
> QtWidget
> applications to the iPad, not to write new ones (nor to do anything on any
> other
> iOS platforms). There is a single customer using QML on iOS, once
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
Me again. I thought I'd announce that I've pushed the first QIosStyle commit to
Gerrit: https://codereview.qt-project.org/#change,51167 I will be doing all
work on the class here in the public eye until it is done and ready to be
merged (hopefully before 5.2 at the latest, 5.1 if we're lucky). I
On Mar 13, 2013, at 10:07 PM, Jake Thomas Petroules
mailto:jake.petrou...@petroules.com>>
wrote:
On Mar 13, 2013, at 1:43 PM, Bache-Wiig Jens
mailto:jens.bache-w...@digia.com>> wrote:
Exactly. Being able to do pixel perfect layouts within the Qt Quick designer is
one of the arguments against
On Mar 13, 2013, at 10:07 PM, Jake Thomas Petroules
wrote:
> So, the only thing left to say is that I hope the issue is not whether
> QiOSStyle is welcome in QtGui at all, but simply whether it can be
> technically achieved and whether there is someone to do the work. If it's the
> latter, t
Op 13-3-2013 18:43, Bache-Wiig Jens schreef:
Exactly. Being able to do pixel perfect layouts within the Qt Quick
designer is one of the arguments against an IOS QStyle implementation.
I would like to be able to see and run my apps _exactly_ as they would
look on the device, without having to
On 13 Mar 2013, at 10:07 PM, Jake Thomas Petroules wrote:
>
> As Morten said, "The way to prove us wrong is of course to step up and
> implement (and maintain) such a style.". Therefore, I will implement and
> maintain QiOSStyle. Of course any help would be appreciated as well.
I agree with th
On Mar 13, 2013, at 1:43 PM, Bache-Wiig Jens wrote:
> Exactly. Being able to do pixel perfect layouts within the Qt Quick designer
> is one of the arguments against an IOS QStyle implementation. I would like to
> be able to see and run my apps _exactly_ as they would look on the device,
> with
_
De: Bache-Wiig Jens
Para: joao morgado
Cc: Gustavsen Richard ; development
Enviadas: Quarta-feira, 13 de Março de 2013 17:43
Assunto: Re: [Development] Qt for iOS - iOSStyle
On Mar 13, 2013, at 5:07 PM, joao morgado
wrote:
To Richard:
>What your saying makes perfect sense to me, and
On Mar 13, 2013, at 5:07 PM, joao morgado
mailto:joaodeusmorg...@yahoo.com>>
wrote:
To Richard:
What your saying makes perfect sense to me, and whatever solution your team
comes up with, for iOS style, I'm sure it will be handsome, (it's Qt we're
talking after all :) ).
Just some toughts f
Enviadas: Quarta-feira, 13 de Março de 2013 14:32
Assunto: Re: [Development] Qt for iOS - iOSStyle
On Mar 13, 2013, at 12:58 PM, Frank Hemer
wrote:
> On Wednesday 13 March 2013 04:46:43 joao morgado wrote:
>> I really don't understand why QtWidgets are not suitable for mo
On quarta-feira, 13 de março de 2013 00.51.05, André Pönitz wrote:
> I'll try hard to abstain from anything resembling irony or sarcasm.
> I just want to carry on this theoretical discussion based on purely
> hypothetical facts.
>
> I'd ask you kindly to either read all, or nothing.
Hi André
With
On Mar 13, 2013, at 12:58 PM, Frank Hemer
wrote:
> On Wednesday 13 March 2013 04:46:43 joao morgado wrote:
>> I really don't understand why QtWidgets are not suitable for mobile
>> plataforms. What is the technicall reason ? Following the Qt "code once
>> deploy everywhere" I have apps with pra
On Wednesday 13 March 2013 04:46:43 joao morgado wrote:
> I really don't understand why QtWidgets are not suitable for mobile
> plataforms. What is the technicall reason ? Following the Qt "code once
> deploy everywhere" I have apps with pratically the same code for desktop,
> symbian and Blackberr
% native.
João de Deus
De: Thiago Macieira
Para: development@qt-project.org
Enviadas: Segunda-feira, 11 de Março de 2013 15:37
Assunto: Re: [Development] Qt for iOS - iOSStyle
On segunda-feira, 11 de março de 2013 07.41.02, Jake Thomas Petroules wrote:
> J
On Mon, Mar 11, 2013 at 05:59:01PM -0700, Thiago Macieira wrote:
> On segunda-feira, 11 de março de 2013 23.02.02, André Pönitz wrote:
> > Why shouldn't it be possible to have a clearly layered stack with
> > proper interfaces?
>
> Maybe "possible" is not the right point. The point is whether it i
I'm already working on some preliminary testing for QIosStyle. I don't know how
long it'll be before I have something on Gerrit but it will come.
--
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petrou...@petroules.com
On Mar 12, 2013, at 7:52 AM,
>
> Another good example of iOS app that does not quite follow the native UI is
> LinkedIn. I really like it, and I agree with you when you say some design
> alternatives can actually look even better than the stock native style based
> ones. But I am assuming this is not the point in this discuss
I agree 100% with Jens. That is all.
tor arne
On 3/12/13 8:56 , Bache-Wiig Jens wrote:
>
[snip]
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Tue, Mar 12, 2013 at 07:56:33AM +, Bache-Wiig Jens wrote:
>
> On Mar 11, 2013, at 12:41 PM, Jake Thomas Petroules
> wrote:
>
> > By the way, I don't know if you saw my comments on your "Qt for iOS
> > Preview" blog post, but...
> >
> > You stated that because there is no HITheme-like A
On Mar 11, 2013, at 12:41 PM, Jake Thomas Petroules
wrote:
> By the way, I don't know if you saw my comments on your "Qt for iOS Preview"
> blog post, but...
>
> You stated that because there is no HITheme-like API on iOS, that creating
> QiOSStyle would be "not possible".
>
> However, we c
On segunda-feira, 11 de março de 2013 23.02.02, André Pönitz wrote:
> Why shouldn't it be possible to have a clearly layered stack with
> proper interfaces?
Maybe "possible" is not the right point. The point is whether it is feasible
with the time and manpower available.
Defining a proper interfa
On Mar 11, 2013, at 5:36 PM, Raul Metsma wrote:
> here is one other solution
> http://docs.appcelerator.com/titanium/latest/
> javascript and native looking widgets under ios
Perhaps we could look into this.
On Mar 11, 2013, at 11:37 AM, Thiago Macieira wrote:
> On segunda-feira, 11 de març
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:
> > > > J
here is one other solution
http://docs.appcelerator.com/titanium/latest/
javascript and native looking widgets under ios
Raul
On Mar 11, 2013, at 10:58 PM, Rafael Roquetto wrote:
> On Mon, Mar 11, 2013 at 01:40:18PM -0700, Thiago Macieira wrote:
>> On segunda-feira, 11 de março de 2013 16.54.31
On Mon, Mar 11, 2013 at 01:40:18PM -0700, Thiago Macieira wrote:
> On segunda-feira, 11 de março de 2013 16.54.31, Rafael Roquetto wrote:
> > Why not? I agree that QtQuick is usually the way to go for implementing
> > mobile UI, but that doesn't exclude QtWidgets for any reasons a developer
> > may
On segunda-feira, 11 de março de 2013 16.54.31, Rafael Roquetto wrote:
> Why not? I agree that QtQuick is usually the way to go for implementing
> mobile UI, but that doesn't exclude QtWidgets for any reasons a developer
> may wish to use it. When we did the BlackBerry port, we did implement a
> Bl
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
> > >
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 les
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 les
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.
By the way, I don't know if you saw my comments on your "Qt for iOS Preview"
blog post, but...
You stated that because there is no HITheme-like API on iOS, that creating
QiOSStyle would be "not possible".
However, we can render any UIView into a buffer using [UIView drawInRect:]
which we shoul
34 matches
Mail list logo
