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.
Content preview: It wasn't out of coincidence that I chose the Loader example.
Again, linking with that my SO question, this was one of my first issues
when I wanted to try just a proof-of-concept with QML. Want to sw [...]
Content analysis details: (5.2 points, 4.6 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.0 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2)
[40.92.9.104 listed in wl.mailspike.net]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider (ruilvo[at]hotmail.com)
1.0 MISSING_HEADERS Missing To: header
0.0 HTML_MESSAGE BODY: HTML included in message
2.4 MALFORMED_FREEMAIL Bad headers on message from free email
service
1.0 FORGED_SPF_HELO No description available.
-0.0 NICE_REPLY_A Looks like a legit reply (A)
0.4 KHOP_HELO_FCRDNS Relay HELO differs from its IP's reverse DNS
2.3 FORGED_MUA_MOZILLA Forged mail pretending to be from Mozilla
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.
--- Begin Message ---
It wasn't out of coincidence that I chose the Loader example. Again,
linking with that my SO question, this was one of my first issues when I
wanted to try just a proof-of-concept with QML. Want to swap bits of the
UI dynamically? In C++ inherit from an interface (QWidget, for example),
and use pointer polymorphism, done.
I have hardware devices that I'd like to support that use the same API
but are self-describing. This means that for example, I might need 1, 3,
or 0 sliders for some parameters. In Widgets I just make a vector of
sliders and shove them in a vertical form layout, done.
Maybe Nuno is right, and I'm just stuck in my programmer mindset. But
yeah, these are the kinds of "issues" that I see by having to use a
declarative language with its own JS engine to glue my c++ code.
Honestly, by this route, I think people don't just use CEF or something
because they don't want to write the server-side boilerplate.
Rui
Em 22/04/2021 16:25, Konstantin Shegunov escreveu:
On Thu, Apr 22, 2021 at 6:10 PM Rui Oliveira <rui...@hotmail.com
<mailto:rui...@hotmail.com>> 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
there is... But seems that people do love QML a lot (again, shouts
out to KDE).
Funny that you mentione the `Loader`, which is sort of no-op item from
the C++/desktop dev perspective. What I mean by that is that the
`Loader` is the archetype of the 'QML engine is really a glorified
object factory', which I mentioned. The only reason it is there is to
delay the creation of a QtQuick item. This would've been rather
trivial to do in a C++ environment, you just create and add the object
to the scene whenever it's needed, no need to wrap this in a
`QObject`, but not so trivial to do if you want to leverage it in a
'declarative' (or rather JS) context. Note that the component doesn't
go away too, because at some point you may want to unload said scene
item, which instead of just deleting, being the obvious choice, you
set the relevant property to the loader, which detaches it from the scene.
Opinions, I guess.
I don't see anything wrong with that, as long as we have a civil
discussion (not a troll fest) about it.
--- End Message ---
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
