> 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_
On Thursday, 14 June 2018 23:55:33 PDT Olivier Goffart wrote:
> QDomDocument is, in fact, not deprecated.
Fair enough. But the QtXml module as a whole is Done.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
__
-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
On 2018-06-14 02:08, Thiago Macieira wrote:
[...]
For example, the next data model over would be XML. And we are indeed missing
a DOM structure for it since we deprecated QDomDocument. Can anyone see a data
structure that works for both JSON/CBOR and generic XML? More importantly, one
that is wor
There exists a need to store, load, and transmit strucured data in almost any application. Te topic at hand is the consideration of a generic format. Sure, you could create a relational database, but if you're nto trying to minimize writes and adapt your application to SQL, it's waste of effort. QD
On Thursday, 14 June 2018 06:47:56 PDT Jean-Michaël Celerier wrote:
> > So YAML makes a lot of sense.
>
> https://github.com/yaml/YAML2/wiki/People-Raging-About-YAML
> https://users.rust-lang.org/t/why-does-cargo-use-toml/3577/15
>
> I would like to understand what all this discussion is about. W
> So YAML makes a lot of sense.
https://github.com/yaml/YAML2/wiki/People-Raging-About-YAML
https://users.rust-lang.org/t/why-does-cargo-use-toml/3577/15
I would like to understand what all this discussion is about. What is the
goal for Qt ?
a) allow developers using Qt to have a simple, human-r
On Wednesday, 13 June 2018 23:46:54 PDT Lars Knoll wrote:
> I’d leave XML out of this. It is difficult to integrate, as it has so many
> special features (entities, CDATA and lot of other things) making it a
> rather complex specification. But there are a couple of other formats that
> might fit a
> On 14 Jun 2018, at 02:08, Thiago Macieira wrote:
>
> Out of the serialisation discussion at QtCS 2018, we have a call for action
> to
> discuss the possibility of *not* adding QCborValue in Qt 5.12 and instead add
> a generic, data model API that could be used for JSON, CBOR and future use
Out of the serialisation discussion at QtCS 2018, we have a call for action to
discuss the possibility of *not* adding QCborValue in Qt 5.12 and instead add
a generic, data model API that could be used for JSON, CBOR and future uses.
The reason was that we do not need the duplication of very sim
13 matches
Mail list logo
