On Donnerstag, 28. Oktober 2021 10:01:41 CEST Christoph Cullmann (cullmann.io) wrote: > On 2021-10-28 08:32, Helio Chissini de Castro wrote: > > Hi Albert > > > > Can i raise the questions on all valid possible solutions ? > > > > - Maintain qxmlpattern on our side > > - Move to libxslt > > - Move away from Xml > > > > The first one is easy from the point of view of applications, but we > > don't know how much maintenance towards qt6 will be considering. > > > > The second one is a little more complex from the point of view of > > applications, some for buildsystem as well, but then we will use a > > library that is already proven everywhere and don't need to maintain > > and can consider API stable enough. > > > > The third one, more unlikely but valid, is to understand why we are > > using XmlPatterns and if we can't replace it with something more > > modern for the "6" interaction of frameworks/plasma. Is some new > > development and will introduce a lot of new things to thought, but > > then, still a valid possibility. > > Hi, > > it think it is more depending on what the application/frameworks does > with the QXmlPatterns. > > e.g. syntax-highlighting does only optional validation of the XML files > with it. > I will move that in KF6 to libxerces, I do already know how to implement > that > as I did the same at work to move away from QXmlPatterns. > > e.g. if applications use xpath stuff, they could use pugixml. > > If they want to have XSLT transformation Albert's mentioned libxslt > might be a good solution. > > But to decide that I would assume one needs to inspect the uses.
Exactly. From what I remember from KDAV for example is it's only using a few simple queries during otherwise regular XML parsing, which probably could be replaced by manual code instead. And most of this can be done now already, no need to wait for the final Qt6 port. Regards, Volker
signature.asc
Description: This is a digitally signed message part.
