> From: Dmitry Volosnykh
> Sent: lundi 18 juin 2018 13:40
>
> FYI, there's QTBUG-29095 and QTBUG-25723 that feel like somewhat related to
> the problem under discussion.
I guess QTBUG-25723 is the kind of problem that Thiago solved for QCborValue
For the use case described in QTBUG-29095, I thi
Friday, June 15, 2018 at 3:46 PM
> > From: "Tor Arne Vestbø"
> > To: "Arnaud Clère"
> > Cc: "Thiago Macieira" , "
> development@qt-project.org"
> > Subject: Re: [Development] RFC: unified data model API in QtCore => thin
>
data changes to the tree to listeners (clients).
> Sent: Friday, June 15, 2018 at 3:46 PM
> From: "Tor Arne Vestbø"
> To: "Arnaud Clère"
> Cc: "Thiago Macieira" ,
> "development@qt-project.org"
> Subject: Re: [Development] RFC: unifi
> On 15 Jun 2018, at 13:31, Arnaud Clère wrote:
>
[snip]
> Most user-defined bind methods would be very simple and the type system would
> guarantee that data is well-formed (no sequence or record left open...):
>
>struct Person {
>QString m_firstName, m_lastName;
>int m_
-Original Message-
From: Thiago Macieira
Sent: jeudi 14 juin 2018 02:08
> This email is to start that discussion and answer these questions:
> a) should we have this API?
> b) if so, what would this API look like?
> c) if not, should we unify at least JSON and CBOR?
> c) either w
