Kinda wondering why you just don't use QVariant and a QDataStream? You're just encoding as text, and if you need to use images, there's no current encoding (AFAIK) for pixel data in CBOR, so you can't interop with anything else anyway...
I found CBOR limiting and not worth it. I was very interested in the promise/premise of CBOR, but I went QVariant+QDS and was glad I did.
Just my $0.02.
Sent: Saturday, December 01, 2018 at 6:54 AM
From: "Konstantin Shegunov" <[email protected]>
To: "Interests Qt" <[email protected]>
Subject: [Interest] QCborValue and Qt types
From: "Konstantin Shegunov" <[email protected]>
To: "Interests Qt" <[email protected]>
Subject: [Interest] QCborValue and Qt types
Hello,
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interestI'm evaluating Qt's (5.12) cbor implementation for a network transmission protocol. I saw that few Qt types were tagged already (I imagine as a proof of concept/preview). Are there plans to extend these to include more types (e.g. QImage) or should I just stick to writing them as binary buffers?
As a follow-up what is the suggested way to pass *custom* types to QCbor*, are they to be streamed through QVariant?
Thanks in advance!
Kind regards.
Thanks in advance!
Kind regards.
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interest
