25.09.2016, 06:51, "Thiago Macieira" :
> On domingo, 25 de setembro de 2016 01:38:12 PDT Konstantin Tokarev wrote:
>> Hopefully there are lots of JSON-like (as well as non-JSON-like) binary
>> formats that have already been implemented for C++
>
> Like I said in the other email, CBOR.
>
> https
On sábado, 24 de setembro de 2016 20:39:48 PDT Thiago Macieira wrote:
> Network IPv4IPv6x
The x is a typo. There's no such thing as IPv6x different from IPv6 that you
may not have yet heard of.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
On domingo, 25 de setembro de 2016 01:38:12 PDT Konstantin Tokarev wrote:
> Hopefully there are lots of JSON-like (as well as non-JSON-like) binary
> formats that have already been implemented for C++
Like I said in the other email, CBOR.
https://github.com/01org/tinycbor
This library compiles t
On sábado, 24 de setembro de 2016 23:50:33 PDT Giuseppe D'Angelo wrote:
> > The decision is like this: it starts equal to the last release's number.
> > If
> > you modify one of the operator<<, you bump the number.
>
> But "you" who? The release manager at release time? Whoever submits a
> change
On domingo, 25 de setembro de 2016 14:31:48 PDT Ch'Gans wrote:
> "Gigantic"? That's sounds very much speculative... They run HTTP
> servers over TCP/IP on arduino (just a random example).
>
> Yes JSON will add some overhead, as Thiago pointed out, CBOR [1] can
> be an alternative.
If you're goin
On 25 September 2016 at 10:38, Giuseppe D'Angelo
wrote:
> Hi,
>
> Il 24/09/2016 02:50, Ch'Gans ha scritto:
>> Adding my 2 cents, I haven't use QDataStream stream much, yet i'm very
>> well aware of this restriction. I think the documentation is very
>> explicit about this. And that might be the re
25.09.2016, 00:39, "Giuseppe D'Angelo" :
> Hi,
>
> Il 24/09/2016 02:50, Ch'Gans ha scritto:
>> Adding my 2 cents, I haven't use QDataStream stream much, yet i'm very
>> well aware of this restriction. I think the documentation is very
>> explicit about this. And that might be the reason i have
Il 24/09/2016 02:22, Thiago Macieira ha scritto:
> On sexta-feira, 23 de setembro de 2016 19:05:28 PDT Giuseppe D'Angelo wrote:
>> Il 23/09/2016 17:14, Thiago Macieira ha scritto:
>>> The expectation is that you read QDataStream with QDataStream. You don't
>>> need to know what it writes, only that
Hi,
Il 24/09/2016 02:50, Ch'Gans ha scritto:
> Adding my 2 cents, I haven't use QDataStream stream much, yet i'm very
> well aware of this restriction. I think the documentation is very
> explicit about this. And that might be the reason i haven't use it
> much.
I'm actually arguing that there's
On sábado, 24 de setembro de 2016 12:50:10 PDT Ch'Gans wrote:
> If the other side of the pipe is arduino, maybe try to use JSON (very
> easy to use on Qt side), and i'm sure arduino as some library for
> this.
If JSON is an option, you should use CBOR.
--
Thiago Macieira - thiago.macieira (AT) i
On 24 September 2016 at 05:05, Giuseppe D'Angelo
wrote:
> Il 23/09/2016 17:14, Thiago Macieira ha scritto:
>> The expectation is that you read QDataStream with QDataStream. You don't need
>> to know what it writes, only that it can read what it writes.
>
> Where has this expectation *ever* been st
On sexta-feira, 23 de setembro de 2016 19:05:28 PDT Giuseppe D'Angelo wrote:
> Il 23/09/2016 17:14, Thiago Macieira ha scritto:
> > The expectation is that you read QDataStream with QDataStream. You don't
> > need to know what it writes, only that it can read what it writes.
>
> Where has this exp
On sábado, 24 de setembro de 2016 00:47:16 PDT Reinhardt Behm wrote:
> > Which is great until it's writing to another device that does not
> > implement
> > Qt, because it's an Arduino or similar. I don't think it's an unusual
> > scenario that you're using QDataStream to exchange data to a device
On sexta-feira, 23 de setembro de 2016 17:41:30 PDT Jason H wrote:
> > > commits to find out what changed? I wouldn't even know where to start.
> >
> > The expectation is that you read QDataStream with QDataStream. You don't
> > need to know what it writes, only that it can read what it writes.
>
Il 23/09/2016 17:14, Thiago Macieira ha scritto:
> The expectation is that you read QDataStream with QDataStream. You don't need
> to know what it writes, only that it can read what it writes.
Where has this expectation *ever* been stated? The very fact that we
document the wire format is so that
On Friday 23 September 2016 11:51:40 Mike Chinander wrote:
> On Fri, Sep 23, 2016 at 11:47 AM, Reinhardt Behm wrote:
> > Or the have two devices are both based on Qt, but different versions.
>
> Isn't this precisely the situation that QDataStream::setVersion() is for?
Yes, and I used it.
The poi
On Fri, Sep 23, 2016 at 11:47 AM, Reinhardt Behm wrote:
> Or the have two devices are both based on Qt, but different versions.
Isn't this precisely the situation that QDataStream::setVersion() is for?
___
Interest mailing list
Interest@qt-project.org
On Friday 23 September 2016 17:41:30 Jason H wrote:
> > Sent: Friday, September 23, 2016 at 11:14 AM
> > From: "Thiago Macieira"
> > To: interest@qt-project.org
> > Subject: Re: [Interest] Current QDataStream format documentation?
> >
> > On sexta-fe
23.09.2016, 18:41, "Jason H" :
>> Sent: Friday, September 23, 2016 at 11:14 AM
>> From: "Thiago Macieira"
>> To: interest@qt-project.org
>> Subject: Re: [Interest] Current QDataStream format documentation?
>>
>> On sexta-
> Sent: Friday, September 23, 2016 at 11:14 AM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Current QDataStream format documentation?
>
> On sexta-feira, 23 de setembro de 2016 17:05:26 PDT Jason H wrote:
> > > Sent: Thu
On sexta-feira, 23 de setembro de 2016 17:05:26 PDT Jason H wrote:
> > Sent: Thursday, September 22, 2016 at 10:12 PM
> > From: "Thiago Macieira"
> > To: interest@qt-project.org
> > Subject: Re: [Interest] Current QDataStream format documentation?
> >
&g
> Sent: Thursday, September 22, 2016 at 10:12 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Current QDataStream format documentation?
>
> On sexta-feira, 23 de setembro de 2016 03:01:40 PDT Jason H wrote:
> > T
On sexta-feira, 23 de setembro de 2016 03:01:40 PDT Jason H wrote:
> The documentation should be current. Maintaining documentation is part os
> selling the toolkit.
The maintainer of QDataStream (me) disagrees. I don't like the versioning
support in the first place, since it's an all-or-nothing.
> On quinta-feira, 22 de setembro de 2016 20:10:32 PDT Jason H wrote:
> > > On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote:
> > > > So I'm still looking for protocol 17 documentation. I need to provide
> > > > this
> > > > documentation to an outside implementer.
> > >
> > > It
On 22 September 2016 at 23:11, Jason H wrote:
> Nevermind. The trick does work. I have no idea what I did wrong.
> http://doc.qt.io/qt-5/datastreamformat.html
>
> "qt5 serialization" is what I had to search for. The 5.x page never came up
> in the Google results, only 4.8. I think we need to add
2016-09-22 21:12 GMT+02:00 Thiago Macieira :
> On quinta-feira, 22 de setembro de 2016 20:10:32 PDT Jason H wrote:
>> > On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote:
>> > > So I'm still looking for protocol 17 documentation. I need to provide
>> > > this
>> > > documentation t
On quinta-feira, 22 de setembro de 2016 20:10:32 PDT Jason H wrote:
> > On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote:
> > > So I'm still looking for protocol 17 documentation. I need to provide
> > > this
> > > documentation to an outside implementer.
> >
> > It doesn't exist
On quinta-feira, 22 de setembro de 2016 19:03:29 PDT Giuseppe D'Angelo wrote:
> On Thu, Sep 22, 2016 at 7:00 PM, Thiago Macieira
>
> wrote:
> > We don't update the QTextStream format documentation.
>
> Do you mean QDataStream?
>
> Anyhow, well, that's the problem. We should do it, at review tim
> On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote:
> > So I'm still looking for protocol 17 documentation. I need to provide this
> > documentation to an outside implementer.
>
> It doesn't exist. You'll have to write it.
I'm not the one who made the changes, so I don't know w
On Thu, Sep 22, 2016 at 7:00 PM, Thiago Macieira
wrote:
> We don't update the QTextStream format documentation.
Do you mean QDataStream?
Anyhow, well, that's the problem. We should do it, at review time (if
we're touching streaming operators into QDataStream, update the
corresponding doc), and a
On Thu, Sep 22, 2016 at 6:52 PM, Thiago Macieira
wrote:
> It doesn't exist. You'll have to write it.
This is actually pointing out a problem in the review process and in
the release process, which we should solve.
My 2 c,
--
Giuseppe D'Angelo
___
Inte
On quinta-feira, 22 de setembro de 2016 18:56:31 PDT Giuseppe D'Angelo wrote:
> On Thu, Sep 22, 2016 at 6:52 PM, Thiago Macieira
>
> wrote:
> > It doesn't exist. You'll have to write it.
>
> This is actually pointing out a problem in the review process and in
> the release process, which we shou
On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote:
> So I'm still looking for protocol 17 documentation. I need to provide this
> documentation to an outside implementer.
It doesn't exist. You'll have to write it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Ar
> 22.09.2016, 18:11, "Jason H" :
> > Nevermind. The trick does work. I have no idea what I did wrong.
> > http://doc.qt.io/qt-5/datastreamformat.html
> >
> > "qt5 serialization" is what I had to search for. The 5.x page never came up
> > in the Google results, only 4.8. I think we need to add so
22.09.2016, 18:11, "Jason H" :
> Nevermind. The trick does work. I have no idea what I did wrong.
> http://doc.qt.io/qt-5/datastreamformat.html
>
> "qt5 serialization" is what I had to search for. The 5.x page never came up
> in the Google results, only 4.8. I think we need to add something to
ore recent documentation?
> Sent: Thursday, September 22, 2016 at 11:11 AM
> From: "Jason H"
> To: "Jason H"
> Cc: interest
> Subject: Re: [Interest] Current QDataStream format documentation?
>
> Nevermind. The trick does work. I have no idea what I did wr
Nevermind. The trick does work. I have no idea what I did wrong.
http://doc.qt.io/qt-5/datastreamformat.html
"qt5 serialization" is what I had to search for. The 5.x page never came up in
the Google results, only 4.8. I think we need to add something to the Qt.io
site that allows you to select
37 matches
Mail list logo
