Jason wrote on Wednesday, 7 March 2012 6:01 AM
> My own experiments in QML have leave me to believe that aside from it's
> limitations (there are many) that most everything "visual" and not
classically
> widget-oriented is made substantially easier.
> If it's 'hard" in QML you're probably doing it
rong, unless it's a QML
limitation.
- Original Message -
From: BRM
To: Interests Qt
Cc:
Sent: Tuesday, March 6, 2012 12:26 PM
Subject: Re: [Interest] To QML or not to QML...
> From: Preet
>On Mon, Mar 5, 2012 at 12:54 PM, Jason H wrote:
>> It is my understanding that the maj
what I can tell on the
development list;
but I haven't paid too much attention to the QML side of things.
>>In terms of your coding, his largely comes down to the import
>> statements that are used.
>> From: BRM
>> To: Interests Qt
>> Sent: Monday, March 5, 20
Hello!
On Mon, Mar 5, 2012 at 7:39 PM, BRM wrote:
>
> As I have not yet touched QML, and there are many on this list who have, what
> you recommend?
> Would it be worth trying to do this in QML - either #2 or #3 - or should I
> just stick to #1?
>
You could try and use pure QML (e.g. have QML
__
> From: BRM
> To: Interests Qt
> Sent: Monday, March 5, 2012 12:39 PM
> Subject: [Interest] To QML or not to QML...
>
> I'm working on an application that presently uses Qt 4.7 for a front-end to
> a larger system. One of its main tasks is t
: BRM
To: Interests Qt
Sent: Monday, March 5, 2012 12:39 PM
Subject: [Interest] To QML or not to QML...
I'm working on an application that presently uses Qt 4.7 for a front-end to a
larger system. One of its main tasks is to display data in the system which
requires rendering up to aro
I'm working on an application that presently uses Qt 4.7 for a front-end to a
larger system. One of its main tasks is to display data in the system which
requires rendering up to around a thousand or so points and overlaying a
template of the ideal against the actual. Presently it does all the w
