On Wednesday, 17 January 2018 13:25:53 PST Thiago Macieira wrote:
> Another idea is to update the network-chat example to use CBOR instead of
> its plaintext protocol. In this one, I could use the stream reader and
> writer. This example is a perfect candidate to have a CoAP version in the
> future
Hello
I finished writing the documentation for the two basic classes for CBOR. You
can find them in reviews
https://codereview.qt-project.org/107465
https://codereview.qt-project.org/107466
Please review. I will take a couple more days writing the docs for
QCbor{Value,Map,Array} and then I'll u
On Tuesday, 16 January 2018 10:28:27 PST Uwe Rathmann wrote:
> On Tue, 16 Jan 2018 18:38:48 +0100, Kevin Kofler wrote:
> > So just use QString(), or define your own static instance of it if you
> > really want to microoptimize it that much.
>
> No it is simply that the first version of Qwt was for
On Monday, 15 January 2018 23:40:03 PST Maurice Kalinowski wrote:
> Personally, I do not see those two items (missing DTLS, release TP)
> conflicting. The only "problem" which might exist, if DTLS takes too long
> to implement and CoAP would stay for a very long time in TP mode.
I don't see a way
Please note that I have an issue: https://bugreports.qt.io/browse/QTBUG-44804 about notifications. Though I titled it wrong with "sending" which should be "receiving".
I did successfully integrate Firebase on Android and iOS. I'm not sure what help you need, but I can give parts of my existing
Hi there,
Thanks for asking:
>Ari: can you give (or point us to, if it's already written up) an
>over-view of what's supported, on which platforms, and how far the API,
>seen by Qt code using it, is independent of choice of back-end ?
>How far is it dependent on the Kaltiot service ? What is t
