On 22.04.21 12:14, Roland Hughes wrote:
>
> On 4/22/2021 3:47 AM, Rui Oliveira wrote:
>> QML/Quick, for me, seems to need a lot of work for the desktop. Also, it
>> seems it's make for "flat", low density UIs. Yesterday I was presented
>> with this:https://ossia.io/ . Look how good it looks
>> (ht
On Thu, 22 Apr 2021 at 23:38, Eric Fedosejevs wrote:
> I do not disbelieve you, but I live in the world of trust but verify
>
> I have been searching for years for an example of a substantial QML based
> desktop productivity application without success. I want to know that it is
> both possi
On 4/22/2021 2:06 PM, Rui Oliveira wrote:
In my particular case (and it's not unique to me at all), I have a
series of devices that I'd like to support, which have completely
different and unrelated controls. This might be my "stuck mindset"
talking, but I've seen this problem solved as I explai
Olá João!
Doing logic with QML? hehe I can hear the voice of Jesper Pedersen from
KDAB saying "your business logic stays in C++"
(https://www.youtube.com/watch?v=JxyTkXLbcV4 pretty good series, actually).
I'm just kidding, Qt itself has examples in Qt Creator making a game
without any C++ lo
Olá Rui
Just to share my experience with Qt widgets and QML. I had a simple desktop
calculator app with Widgets and OpenGL graphics. I had a c++ mindset and was ok
doing that. When QML come around it was a bit strange and I had to leave my
confort zone. Eventually QML syntax become so pleasent
I agree absolutely with these observations, in principle.
But this seems to be "easy" when we're talking about an application
displaying data, with a fixed set of controls. Flashback to all the QML
tutorials using model/view + delegates.
In my particular case (and it's not unique to me at all
On Thu, Apr 22, 2021 at 7:19 PM Giuseppe D'Angelo via Interest <
interest@qt-project.org> wrote:
> You should create a C++ layer (call it a "presentation" layer) that sits
> between your (possibly non-Qt) business logic and the UI. That layer
> contains stuff like item models, QObjects that expose
On 4/22/21 8:15 AM, eric.fedosej...@gmail.com wrote:
From: Interest On Behalf Of Volker Hilsheimer
Sent: Thursday, April 22, 2021 8:24 AM
We currently have no specific plans to make QWidget render through RHI, and
neither the video nor my earlier emails suggest that this is on the roadmap. It
On 22/04/2021 17:06, Rui Oliveira wrote:
Q_INVOKABLE, Q_PROPERTY, etc... The Qt stuff crawls into what would
otherwise be just business logic because you need to access something.
I've linked this before:
https://stackoverflow.com/questions/66618613/qml-c-classes-with-bring-your-own-component
On 22/04/2021 15:57, Jérôme Godbout wrote:
I wonder if it would be possible to totally declare the QtQuick scene
from C++ without any Qml files actually, with Qt6 you got C++ binding
and the Qml is compiled to C++ anyway. Maybe I miss something but it
could be possible to actually only write C+
Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
C
I do not disbelieve you, but I live in the world of trust but verify. I
have an aging widgets application and I am trying to decide what to replace
widgets with as they undergo their slow ignoble LTS-free death.
I have been searching for years for an example of a substantial QML based
desktop prod
On Thu, Apr 22, 2021 at 6:10 PM Rui Oliveira wrote:
> Basically we're coupling the whole backend to the GUI framework.
>
You always have some coupling between the logic and the GUI, no matter what
you use, but I do get the gist.
> I'd prefer to write C++ than to learn Loaders and whatever else t
On Wed, Apr 21, 2021 at 05:42:50PM +0200, Jason H wrote:
>You probably won't -- it's too new. Unless you call automotive
>Infotainment consoles success stories.
>The lack of proper QtQuick Controls (v2) held it back for a while.
>
>Personally, I think the exsting QtQuick eleme
> Sent: Thursday, April 22, 2021 at 4:50 AM
> From: "Volker Hilsheimer"
> To: "Bernhard Lindner"
> Cc: "interest@qt-project.org"
> Subject: Re: [Interest] Guide me through the Qt offerings for GUIs
>
> > On 21 Apr 2021, at 22:39, Bernhard Lindner
> > wrote:
> >
> >
> >> Personally, I think
"Anything that's non-trivial ends up with (a) huge boilerplate wrapper(s)."
Q_INVOKABLE, Q_PROPERTY, etc... The Qt stuff crawls into what would
otherwise be just business logic because you need to access something.
I've linked this before:
https://stackoverflow.com/questions/66618613/qml-c-cl
On Thu, Apr 22, 2021 at 11:56 AM Volker Hilsheimer
wrote:
> * declarative vs imperative APIs
>
> Many widget classes don’t have a declarative-friendly API. Plenty of
> widget properties have side effects on other properties, so the order in
> which properties are set matters. That doesn’t work we
> On Wednesday, 21 April 2021 10:39:01 PDT Giuseppe D'Angelo via Interest wrote:
> > But no $X. I'm still not sure what $PROJ means.
>
> The way the example was given, the string "$PROJ" will be written literally to
> the Makefile. Make will then interpret it as $(P)ROJ, which is likely not what
>
On Thu, Apr 22, 2021 at 4:59 PM Jérôme Godbout wrote:
> I wonder if it would be possible to totally declare the QtQuick scene from
> C++ without any Qml files actually, with Qt6 you got C++ binding and the
> Qml is compiled to C++ anyway. Maybe I miss something but it could be
> possible to actua
I totally forgot about those! I follow them and voted them on JIRA.
Also, I'm literally the last comment in there asking for an ETA.
"Reporter: Lars Knoll"
Well, seems that someone must have missed the memo! (just kidding!)
Rui
Em 22/04/2021 14:17, Giuseppe D'Angelo via Interest escreveu:
On
> On 2021 Apr 22, at 10:47, Rui Oliveira wrote:
> What doesn't make sense, to me at least, is how QQC*1* seemed to have had a
> better feature set for the desktop than QQC*2*.
The focus was on high-performance embedded use cases at first. Now we are
working again on making QQC2 better for des
I wonder if it would be possible to totally declare the QtQuick scene from C++
without any Qml files actually, with Qt6 you got C++ binding and the Qml is
compiled to C++ anyway. Maybe I miss something but it could be possible to
actually only write C++ to create the actual scene?!
I would not
Thanks Volker, that was insightful answer. I would love more answer like that!
From: Interest on behalf of Volker Hilsheimer
Date: Thursday, April 22, 2021 at 4:52 AM
To: Bernhard Lindner
Cc: interest@qt-project.org
Subject: Re: [Interest] Guide me through the Qt offerings for GUIs
> On 21 Ap
it's not a problem of QML, it's just because no any UI/UX guys touched it
at all
On Thu, Apr 22, 2021 at 3:15 PM wrote:
> > From: Interest On Behalf Of Vlad
> Stelmahovsky
> > this Slack client clone created using C++/QML (Desktop app, built for
> Linux/Windows/macOs)
> >
> https://user-images.
On 22/04/2021 14:55, Rui Oliveira wrote:
I know Giuseppe D’Angelo isn't a TQtC employee, but I trust KDABs stuff
in general.
https://www.qtdesktopdays.com/wp-content/uploads/2020/09/keynote.pdf
Slide 19 "Accelerate widget rendering & compositing through RHI", or I
didn't understand something?
> From: Interest On Behalf Of Vlad
> Stelmahovsky
> this Slack client clone created using C++/QML (Desktop app, built for
> Linux/Windows/macOs)
> https://user-images.githubusercontent.com/11473810/55072233-d58ce380-508a-11e9-9e6a-b6b80fc83dd6.png?raw=true
Thank you for an actual example of a d
I know Giuseppe D’Angelo isn't a TQtC employee, but I trust KDABs stuff
in general.
https://www.qtdesktopdays.com/wp-content/uploads/2020/09/keynote.pdf
Slide 19 "Accelerate widget rendering & compositing through RHI", or I
didn't understand something?
Rui
Em 22/04/2021 13:24, Volker Hilshe
We currently have no specific plans to make QWidget render through RHI, and
neither the video nor my earlier emails suggest that this is on the roadmap. It
generally makes very little sense to draw with a pen into a freshly wiped out
Vulkan surface 60 times per second.
Cheers,
Volker
> On 22
That's nowhere near work of art. It's pretty much what the other poster
was describing, a flat UI.
On 4/22/21 4:35 AM, Vlad Stelmahovsky wrote:
this Slack client clone created using C++/QML (Desktop app, built for
Linux/Windows/macOs)
https://user-images.githubusercontent.com/11473810/55072233-
This makes me raise the question: then how will you do the RHI backend
for Widgets then, if they are so "incompatible"?
Rui
Em 22/04/2021 09:50, Volker Hilsheimer escreveu:
On 21 Apr 2021, at 22:39, Bernhard Lindner wrote:
Personally, I think the exsting QtQuick element should be scrapped
On 22/04/2021 13:01, Bernhard Lindner wrote:
You explained why the widgets concept is not compatible with the Quick concept.
Can you
also explain why it was not possible to implement Quick as an additional,
mostly widget-
independent C++ layer and then wrap it declaratively?
Do you mean, also
> Widgets are heavy, often very complex objects. They often come with all bells
> and
> whistles. QPushButton always has the data structure to support
> QPushButton::setMenu,
> even if probably <1% of buttons out there ever use that feature. That’s ok on
> desktop
> machines, it’s not ok on emb
On 4/22/2021 3:47 AM, Rui Oliveira wrote:
QML/Quick, for me, seems to need a lot of work for the desktop. Also, it
seems it's make for "flat", low density UIs. Yesterday I was presented
with this:https://ossia.io/ . Look how good it looks
(https://ossia.io/assets/score.png)! Holy damn, an that'
"QML is just a hand polished turd. There is no polite way to put it.”
"Qt made a desperate ploy to attract script kiddies in the iDiot phone market
with QML.”
"The problem is, by and large, script kiddies don’t know anything. They tend to
be “self-taught” with far more emphasis on “self” than “
On 4/22/2021 3:47 AM, Bernhard Lindner wrote:
Judging from the influx in the CopperSpice world, a lot of companies with
projects large
and small are biting the bullet.
How did you come to this result? Are there any hard numbers, links, reports,
etc. that you
can share?
Hard? Don't know. The
this Slack client clone created using C++/QML (Desktop app, built for
Linux/Windows/macOs)
https://user-images.githubusercontent.com/11473810/55072233-d58ce380-508a-11e9-9e6a-b6b80fc83dd6.png?raw=true
if you dont know how, doesnt meant is not possible
On Thu, Apr 22, 2021 at 11:00 AM Roland Hugh
On 4/22/2021 3:47 AM, Nuno Santos wrote:
Boas Rui,
On 21 Apr 2021, at 18:24, Rui Oliveira wrote:
I did notice your product line before, when you first answered me.
I like the look! Would you like to tell a bit about your experience in moving
to Qt Quick? What were your main barriers?
As
> On 21 Apr 2021, at 22:39, Bernhard Lindner
> wrote:
>
>
>> Personally, I think the exsting QtQuick element should be scrapped and just
>> focus on QML
>> versions of the existing Widget functionality. I love the QML syntax, hate
>> that it's not
>> just a layer on top of widgets.
>
> +100
Well, I think this needs some historial context. Remember Nokia and how
they wanted Qt to be the /de facto/ SDK for their mobile SO? QWidgets +
phones? Not that great of a deal... Now update that story to Android or
whatever, and Widgets aren't an answer for mobile development. It makes
sense Q
39 matches
Mail list logo
