[Qt-interest] Qt5 and XML DOM
Jason H
scorp1us at yahoo.com
Thu May 12 00:01:32 CEST 2011
I used XPath with Qt before it existed (XmlPatterns). How did I do that?
Recursive QDomNode navigation. With write capability.
XPath is cool, and would be cool if it could write in Qt, but that's only a
subset of what you can do when you can have the expression return a
QDomNodeList. (Or as I prefer QList<QDomNode>)
Which gets me to my next point, Qt needs to have the QDomNode stuff support Qt's
foreach(){}
And finally, there needs to be some abstract representation of structured data
that can be mapped in and out of XML space, like a QObject hierarchy. We could
then convert from any structured data to any other structured data: XML, JSON,
Python, binary file formats. We can then read in any format and write in any
format. But once read, we can manipulate it in what ever way we want. All those
formats are just serializations of structured data.
________________________________
From: Sylvain Pointeau <sylvain.pointeau at gmail.com>
To: qt-interest <qt-interest at trolltech.com>
Sent: Wed, May 11, 2011 5:02:21 PM
Subject: Re: [Qt-interest] Qt5 and XML DOM
On Wed, May 11, 2011 at 10:16 PM, BRM <bm_witness at yahoo.com> wrote:
I've used both libXML2 and Qt QDom - I much prefer QDom. I use to build and
parse custom XML messages for a distributed system's communication protocol.
QDom is very straight forwards and a lot less overhead. The libXML2
implementation required a lot more code to do the same thing, and I was very
glad to mostly deprecate it. (I still keep it around for some non-Qt
applications.)
>
>
I mainly use xpath (read/write values) and xslt/exslt in libxml2, there is no
equivalent in Qt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20110511/4bce53ed/attachment.html
More information about the Qt-interest-old
mailing list