Re: [Interest] Qt 5.6 Qt labs controls porting to QtQuick2 controls

[Ramakanth Kesireddy]

Thanks for your response.

Though there is no Qt documentation, can it be ported from Qt labs controls
to QtQuick2 controls and vice-versa?

Best Regards,
Ramakanth

On Tue, 6 Apr, 2021, 12:38 Mitch Curtis,  wrote:

> > -Original Message-
> > From: Interest  On Behalf Of Ramakanth
> > Kesireddy
> > Sent: Thursday, 1 April 2021 3:10 AM
> > To: Qt Interest 
> > Subject: [Interest] Qt 5.6 Qt labs controls porting to QtQuick2 controls
> >
> > Hi,
> >
> > As we used Qt 5.6 Qt labs controls 1.0 in our Qml application and would
> like to
> > port to QtQuick2 controls in Qt 5.15, could you please let me know if
> there is
> > a Qt documentation to port the labs controls to QtQuick2 controls and
> > compatibility or known issues if any?
> >
> > Please suggest in this regard.
> >
> > Best Regards,
> > Ramakanth
> >
>
> We have porting documentation for Qt Quick Controls 1 to 2, but not from
> Labs Controls to Qt Quick Controls 2.
>
> The closest thing would be to check the change log for each minor version
> up to the version you want to use:
>
> https://code.qt.io/cgit/qt/qtquickcontrols2.git/tree/dist
>
> The "Important Behavior Changes" section is the most relevant here.
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [EXTERNAL] Re: Send Data to JavaScript

[Giuseppe D'Angelo via Interest]

Il 14/04/21 16:15, Jérôme Godbout ha scritto:
Yeah that would be a pain, but if it work you can try to reduce the 
QVariant usage to a minimum from that point.


 1. QVariantMap
 2. QMap
 3. QMap
 4. QMap
 5. QMap>
 6. QMap>

See up to where you can reach before it fail, it will tell you which 
data type is not working for the type mapping. If they all succeed, then 
something might be wrong with the QList or QStringList if you 
prefer. Maybe the exposed type doesn’t handle the typedef properly when 
nested.




A mandatory note: a QVariant can hold _any_ data type (even 
application-defined ones). That doesn't mean you can send a QVariant 
over to JS and expect to magically manipulate its contents from over 
there. Only QVariants with _specific_ contents work.


(For comparison, in QML, all the ones with unsupported content become a 
`var` blob, that you can only copy around and eventually pass back to 
C++; but they're unusable from QML itself).


So although you can store a QMap in a QVariant, 
that doesn't mean it magically works because of the wrapping.


If the docs are not conclusive about which datatypes work and under 
which conditions, do the simple tests suggested above (exposing 
progressively more and more "complicated" types); that should quickly 
help figuring out what is actually supported and what not.


HTH,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [EXTERNAL] Re: Send Data to JavaScript

[Jérôme Godbout]

Yeah that would be a pain, but if it work you can try to reduce the QVariant 
usage to a minimum from that point.


  1.  QVariantMap
  2.  QMap
  3.  QMap
  4.  QMap
  5.  QMap>
  6.  QMap>
See up to where you can reach before it fail, it will tell you which data type 
is not working for the type mapping. If they all succeed, then something might 
be wrong with the QList or QStringList if you prefer. Maybe the 
exposed type doesn’t handle the typedef properly when nested.

Jérôme Godbout, B. Ing.

Software / Firmware Team Lead
O: (418) 682-3636 ext.: 114
C: (581) 777-0050
godbo...@dimonoff.com
[signature_960691443]
dimonoff.com
1015 Avenue Wilfrid-Pelletier,
Québec, QC G1W 0C4, 4e étage


From: Interest  on behalf of John Schneiderman 

Date: Wednesday, April 14, 2021 at 2:56 AM
To: qt qt 
Subject: Re: [Interest] [EXTERNAL] Re: Send Data to JavaScript
On 12.04.2021 20:48, Jérôme Godbout wrote:
Have you tried with a QVariantMap for your Q_PROPERTY instead? Will be dull to 
convert from QVAriant to list and string for each values, but will probably 
work.
I've not tried using that, but looking at it, wouldn't it mean that I'd 
have to convert it each time to get the QStringList?


--

John Schneiderman

Senior Software Engineer

CDPR Squad

GOG.com
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Futur of Qt Webengine in Qt 6

[Frank Hemer]

On Mittwoch, 14. April 2021 13:11:23 CEST Allan Sandfeld Jensen wrote:
> On Mittwoch, 14. April 2021 13:00:01 CEST Frank Hemer wrote:
> > On Montag, 12. April 2021 17:35:43 CEST Allan Sandfeld Jensen wrote:
> > > On Montag, 12. April 2021 13:20:36 CEST Frank Hemer wrote:
> > > > Hi all,
> > > > 
> > > > i wonder what are the plans for Qt Webengine in Qt 6.
> > > > 
> > > > While webkit has been removed and replaced by webengine, there is
> > > > still
> > > > no
> > > > replacement supported by the mingw compiler yet.
> > > > As a commercial customer it was disappointing enought this happened
> > > > within
> > > > a minor release but even more to be told (by commercial support) that
> > > > there currently is no replacement available - and no schedule for a
> > > > replacement.
> > > > 
> > > > Does this mean we have to go back in time using com interfaces or are
> > > > there
> > > > other plans on this?
> > > 
> > > The plans for Qt WebEngine in Qt 6 does not include support for mingw.
> > > But
> > > like Qt 5 we do support building with clang-cl, if you only need to
> > > avoid
> > > MSVC.
> > 
> > Hmm - regarding qt5, webengine-platform-notes tells me vs2017 version 15.8
> > or later is required.
> > So i can't go w/o msvc, can i?
> 
> Clang-cl uses the msvc standard library, but not the compiler itself.
> Perhaps we need to update the platform-notes.

Hi Allan,

thx a lot - this indeed was missing.

Best regards
Frank



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Futur of Qt Webengine in Qt 6

[Allan Sandfeld Jensen]

On Mittwoch, 14. April 2021 13:00:01 CEST Frank Hemer wrote:
> On Montag, 12. April 2021 17:35:43 CEST Allan Sandfeld Jensen wrote:
> > On Montag, 12. April 2021 13:20:36 CEST Frank Hemer wrote:
> > > Hi all,
> > > 
> > > i wonder what are the plans for Qt Webengine in Qt 6.
> > > 
> > > While webkit has been removed and replaced by webengine, there is still
> > > no
> > > replacement supported by the mingw compiler yet.
> > > As a commercial customer it was disappointing enought this happened
> > > within
> > > a minor release but even more to be told (by commercial support) that
> > > there currently is no replacement available - and no schedule for a
> > > replacement.
> > > 
> > > Does this mean we have to go back in time using com interfaces or are
> > > there
> > > other plans on this?
> > 
> > The plans for Qt WebEngine in Qt 6 does not include support for mingw. But
> > like Qt 5 we do support building with clang-cl, if you only need to avoid
> > MSVC.
> 
> Hmm - regarding qt5, webengine-platform-notes tells me vs2017 version 15.8
> or later is required.
> So i can't go w/o msvc, can i?
> 
Clang-cl uses the msvc standard library, but not the compiler itself. Perhaps 
we need to update the platform-notes.

'Allan


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Futur of Qt Webengine in Qt 6

[Frank Hemer]

On Montag, 12. April 2021 17:35:43 CEST Allan Sandfeld Jensen wrote:
> On Montag, 12. April 2021 13:20:36 CEST Frank Hemer wrote:
> > Hi all,
> > 
> > i wonder what are the plans for Qt Webengine in Qt 6.
> > 
> > While webkit has been removed and replaced by webengine, there is still no
> > replacement supported by the mingw compiler yet.
> > As a commercial customer it was disappointing enought this happened within
> > a minor release but even more to be told (by commercial support) that
> > there currently is no replacement available - and no schedule for a
> > replacement.
> > 
> > Does this mean we have to go back in time using com interfaces or are
> > there
> > other plans on this?
> 
> The plans for Qt WebEngine in Qt 6 does not include support for mingw. But
> like Qt 5 we do support building with clang-cl, if you only need to avoid
> MSVC.

Hmm - regarding qt5, webengine-platform-notes tells me vs2017 version 15.8 or 
later is required.
So i can't go w/o msvc, can i?

Best regards
Frank



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [EXTERNAL] Re: Send Data to JavaScript

[John Schneiderman]

On 12.04.2021 20:48, Jérôme Godbout wrote:


Have you tried with a QVariantMap for your Q_PROPERTY instead? Will be 
dull to convert from QVAriant to list and string for each values, but 
will probably work.


    I've not tried using that, but looking at it, wouldn't it mean 
that 
I'd have to convert it each time to get the QStringList?


--
John Schneiderman
Senior Software Engineer
CDPR Squad
GOG.com



OpenPGP_0xB23C7A7C8E96CE3B.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [EXTERNAL] Re: Send Data to JavaScript

[John Schneiderman]

On 12.04.2021 16:12, Giuseppe D'Angelo via Interest wrote:
But a similar consideration applies: do you have any documentation 
telling you how datatypes in C++ are mapped to datatypes in JS -- and 
thus if your QMap is supposed to be supported, 
or if instead you need to "massage" it a bit? 
    The only thing that I've been able to find is the mapping for JSON 
and QVariant. And it shows that QMap, QString, and QStringList all can 
be mapped into a QVariant.


--
John Schneiderman
Senior Software Engineer
CDPR Squad
GOG.com



OpenPGP_0xB23C7A7C8E96CE3B.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest