[Patch] Use Qt XML to decode config.xml files

Vincent Torri vincent.torri at gmail.com
Tue Apr 5 02:38:31 PDT 2011


On Tue, Apr 5, 2011 at 11:01 AM, Michael Sprauer <Michael at sprauer.net>wrote:

> On Mon, 04 Apr 2011 12:03:19 -0700, Thiago Macieira <thiago at kde.org>
> wrote:
>
>> On Monday, 4 de April de 2011 15:00:28 Simon McVittie wrote:
>>
>>> * since QtXML and QtDBus are released together, using Qt to parse XML
>>> gives
>>>  us a circular dependency: Qt contains QtDBus needs libdbus which needs
>>> QtXML which is part of Qt
>>>
>>
>> That means that, if you want to use this backend, you have to compile Qt
>> without D-Bus, then compile D-Bus, then compile Qt again with D-Bus.
>>
>> In terms of time spent compiling, you're probably better off by
>> getting expat
>> set up... but hey, if this helps you, sure, go ahead.
>>
>> In any case, I'd recommend using QXmlStreamReader from QtCore instead of
>> the
>> DOM classes from QtXml. They're faster, more compliant and more strict,
>> and
>> have better error recovery.
>>
>
> Thank you for all your comments and suggestions.
> For what I understand there are two ways to go:
>
> First:
> Integrate the xml parsing bits from expat into dbus lib.
> Like suggested here: https://bugs.freedesktop.org/show_bug.cgi?id=35958#c1
>
> Second:
> Integrate dbus into Qt as an third-party package.
>
> I'd prefer the second. Do you think this is possible/would make any sens?
> Is it worth working on it?
>
> My goal is to have an DBUS running with less effort on the windows side.
> And I
> like to use id with Qt.
> So what way to go?
>

I personnaly want to run dbus on Windows, but without QT. If QT is just
optionnal, no problem for me.

But seriously, I'm wondering why so many xml parsers are needed. If expat is
sufficient, why adding other parsers ?  I even think that libxml2 support
should be dropped. Less code to maintain, less headaches.

regards

Vincent torri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20110405/af54f6a8/attachment.htm>


More information about the dbus mailing list