[Development] Proposal for an efficient and robust (de)serialization mechanism working with Qt-supported data
bogdan.vatra at kdab.com
Fri Aug 30 16:00:42 CEST 2019
It will be great if we can find a way to use it any (de)serialization
mechanism (e.g. proto buff, flat buffers, etc.) not only with only one (qt
În ziua de vineri, 30 august 2019, la 16:42:54 EEST, Simon Hausmann a scris:
> Hi Arnaud,
> I think that perhaps this is also a topic worth discussing at the Qt
> Contributor Summit, if you can attend. During a face-to-face discussion we
> may be able to find a good understanding more efficiently of what exactly
> it is that we need in Qt.
> I'm interesting in discussing how we can get away from QDataStream towards
> something more schema oriented. Perhaps that involves an intermediate
> abstraction similar to what you're proposal.
> From: Development <development-bounces at qt-project.org> on behalf of Arnaud
> Clere <arnaud.clere at minmaxmedical.com> Sent: Friday, August 30, 2019 15:37
> To: Edward Welbourne <edward.welbourne at qt.io>
> Cc: development at qt-project.org <development at qt-project.org>
> Subject: Re: [Development] Proposal for an efficient and robust
> (de)serialization mechanism working with Qt-supported data
> Thank you,
> I will then submit a patch with the core of QBind and ask for reviewers.
> -----Original Message-----
> From: Edward Welbourne <edward.welbourne at qt.io>
> Sent: jeudi 29 août 2019 17:39
> To: Arnaud Clere <arnaud.clere at minmaxmedical.com>
> Subject: Re: Proposal for an efficient and robust (de)serialization
> mechanism working with Qt-supported data
> Hi Arnaud,
> > I only received feedback from users in private, so I guess this is not
> > the right mailing list to ask for feedback on new features.
> The development@ list is entirely apt as a place for this discussion.
> It's just that we're all rather busy (we just passed a feature freeze for a
> release we'll be polishing for the near future) and the Qt community
> generally works by "if no-one objects, go for it". FWIW (not much, as this
> is outside my field of expertise) what you describe sounded interesting and
> worth turning into a code review on https://codereview.qt-project.org/
> Development mailing list
> Development at qt-project.org
More information about the Development