'Re: QtQuick: Why is it relevant'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: kde-devel
Subject: Re: QtQuick: Why is it relevant
From: Shantanu Tushar Jha <shantanu () kde ! org>
Date: 2015-03-06 3:54:15
Message-ID: CABQ4Km-vGKW2SBydYXVqtz=3vsCjp16eDGLXUqCggJP0Kkvhug () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hi,

Adding to what Aleix said, the approach to problems being different might
also lead to confusion and frustration in the beginning if you have used
QWidgets extensively. In such cases, reading the examples (there are loads
of them) is very useful.

-- 
Shantanu Tushar    (UTC +0530)
http://www.shantanutushar.com

On Fri, Mar 6, 2015 at 7:40 AM, Aleix Pol <aleixpol@kde.org> wrote:

> On Fri, Mar 6, 2015 at 1:13 AM, Olivier CHURLAUD <olivier@churlaud.com>
> wrote:
> > Hi,
> >
> > I saw that one of the great feature of Qt was QtQuick, and that KDE
> chose to
> > use this a lot. I went lately from fully written widgets to
> QtDesigner....
> >
> > What are the real advantages of QtQuick over the old fashion Qt (I don't
> > know how to call it)? Are there drawbacks? (The real question is Why
> should
> > I write my app with QtQuick instead of old fashion Qt?)
>
> From my point of view, a reason to use QtQuick over QtWidgets is that
> you can essentially do more things. QtWidgets is designed to integrate
> properly on desktop environments, that wasn't even part of the plan in
> QtQuick not so long ago (also not the case anymore).
> So I wouldn't go for QtWidgets if you want it to be touch-friendly, if
> you want any animations or if you want to think about how information
> will be presented specifically. On the other hand, there's a set of
> use-cases that QtWidgets covers very well, then it's fine to use it
> just as well.
>
> >
> > Another question is: are there resources (on KDE or somewhere else) to
> > see/learn the power of QtQuick? Be cause when I read this for instance
> This pops to mind, I haven't read it personally. I usually use the
> official Qt documentation.
> http://qmlbook.github.io/
>
> >
> https://techbase.kde.org/Development/Tutorials/Plasma4/QML/GettingStarted
> it
> > doesnt seems to be well designed for handling contents comming from a
> > database (or very dynamic content)
>
> The way to integrate these big chunks of contents is through models.
> Keep in mind that the views in QtQuick and QtQuick Controls are very
> different than those in QtWidgets, so the ways you'd approach the
> problems are slightly different.
>
> HTH,
> Aleix
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>

[Attachment #5 (text/html)]

<div dir="ltr">Hi, Adding to what Aleix said, the approach to problems being \
different might also lead to confusion and frustration in the beginning if you have \
used QWidgets extensively. In such cases, reading the examples (there are loads of \
them) is very useful. -- <div class="gmail_signature">Shantanu \
Tushar (UTC +0530) <a href="http://www.shantanutushar.com" \
target="_blank">http://www.shantanutushar.com</a></div> <div \
class="gmail_quote">On Fri, Mar 6, 2015 at 7:40 AM, Aleix Pol &lt;<a \
href="mailto:aleixpol@kde.org" target="_blank">aleixpol@kde.org</a>&gt; \
wrote: <blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, \
Mar 6, 2015 at 1:13 AM, Olivier CHURLAUD &lt;<a \
href="mailto:olivier@churlaud.com">olivier@churlaud.com</a>&gt; wrote: &gt; \
Hi, &gt; 
&gt; I saw that one of the great feature of Qt was QtQuick, and that KDE chose to 
&gt; use this a lot. I went lately from fully written widgets to QtDesigner.... 
&gt; 
&gt; What are the real advantages of QtQuick over the old fashion Qt (I don&#39;t 
&gt; know how to call it)? Are there drawbacks? (The real question is Why should 
&gt; I write my app with QtQuick instead of old fashion Qt?) 
 
From my point of view, a reason to use QtQuick over QtWidgets is that 
you can essentially do more things. QtWidgets is designed to integrate 
properly on desktop environments, that wasn&#39;t even part of the plan in 
QtQuick not so long ago (also not the case anymore). 
So I wouldn&#39;t go for QtWidgets if you want it to be touch-friendly, if 
you want any animations or if you want to think about how information 
will be presented specifically. On the other hand, there&#39;s a set of 
use-cases that QtWidgets covers very well, then it&#39;s fine to use it 
just as well. 
 
&gt; 
&gt; Another question is: are there resources (on KDE or somewhere else) to 
&gt; see/learn the power of QtQuick? Be cause when I read this for instance 
This pops to mind, I haven&#39;t read it personally. I usually use the 
official Qt documentation. 
<a href="http://qmlbook.github.io/" target="_blank">http://qmlbook.github.io/</a> 
 
&gt; <a href="https://techbase.kde.org/Development/Tutorials/Plasma4/QML/GettingStarted" \
target="_blank">https://techbase.kde.org/Development/Tutorials/Plasma4/QML/GettingStarted</a> \
it &gt; doesnt seems to be well designed for handling contents comming from a 
&gt; database (or very dynamic content) 
 
The way to integrate these big chunks of contents is through models. 
Keep in mind that the views in QtQuick and QtQuick Controls are very 
different than those in QtWidgets, so the ways you&#39;d approach the 
problems are slightly different. 
 
HTH, 
Aleix 
 
&gt;&gt; Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe &lt;&lt; </blockquote></div> </div>

[Attachment #6 (text/plain)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread] 