Comments on: XSL-T and Qt http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/ A well-defined blog. Thu, 24 Sep 2009 10:58:13 +0000 http://wordpress.com/ hourly 1 By: Mark http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5562 Mark Mon, 18 May 2009 20:44:43 +0000 http://englich.wordpress.com/?p=49#comment-5562 Hello Englich, I am creating an authoring tool and I would also like to transform memory bound dom trees rather than xml files. I will be transforming a subsection of an QDomDocument for display and editing, transforming it back into the original schema, and replacing the original subsection. All of this will be done in memory and if I can avoid writing to disk I would prefer it. I am sure I will have an implementation complete by 4.6, but I look forward to new tools to address my use case. I love refactoring that simplifies my design. Thanks a bunch, Mark Hello Englich,

I am creating an authoring tool and I would also like to transform memory bound dom trees rather than xml files. I will be transforming a subsection of an QDomDocument for display and editing, transforming it back into the original schema, and replacing the original subsection. All of this will be done in memory and if I can avoid writing to disk I would prefer it.

I am sure I will have an implementation complete by 4.6, but I look forward to new tools to address my use case. I love refactoring that simplifies my design.

Thanks a bunch,
Mark

]]> By: charlie http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5525 charlie Tue, 06 Jan 2009 20:44:11 +0000 http://englich.wordpress.com/?p=49#comment-5525 Just read the news. Thanks very much for your work. I will test out QT-4.5 beta 1 xmlpatterns as soon as possible. Xmlpatterns is the greatest thing to happen in the Linux world for the year 2009 as it represents the pennicle of information technology. My only wish is that more web developers know about XSL and have the intelligence and patience to use it. With the added simplicity of XSLT 2 perhaps more developers will be persuaded to use XSL someday. Just read the news. Thanks very much for your work. I will test out QT-4.5 beta 1 xmlpatterns as soon as possible. Xmlpatterns is the greatest thing to happen in the Linux world for the year 2009 as it represents the pennicle of information technology.

My only wish is that more web developers know about XSL and have the intelligence and patience to use it. With the added simplicity of XSLT 2 perhaps more developers will be persuaded to use XSL someday.

]]> By: englich http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5499 englich Thu, 23 Oct 2008 13:34:55 +0000 http://englich.wordpress.com/?p=49#comment-5499 celso: The code in Qt is just a basic C++ Qt API like all other, so whenever bindings are updated to include those APIs, I guess it will include that functionality as well. celso:

The code in Qt is just a basic C++ Qt API like all other, so whenever bindings are updated to include those APIs, I guess it will include that functionality as well.

]]> By: celso http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5497 celso Thu, 23 Oct 2008 13:10:44 +0000 http://englich.wordpress.com/?p=49#comment-5497 Do you have this code in python (pyqt)? Do you have this code in python (pyqt)?

]]> By: Guido Seifert http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5491 Guido Seifert Mon, 20 Oct 2008 09:38:26 +0000 http://englich.wordpress.com/?p=49#comment-5491 Hi Frans, XQuery is great when you need to read data from certain nodes in an xml document. XQuery is often compared with SQL for databases. Unfortuantely in this comparison it implements only the 'SELECT' statement, but not the 'UPDATE' or 'INSERT' statements. AFAIK something like that is in planning stage (XQuery Update Facility 1.0). To have this new addition to XQuery in Qt would be great. The question is, what is the better or easier way to do: Implementing a not yet finalized standard, or implementing a feature, which traverses a QDomTree via XQuery, returns one or more QDomNodes, and thus allows to update the underlying QDomTree via the QDom-API. Hi Frans,
XQuery is great when you need to read data from certain nodes in an xml document. XQuery is often compared with SQL for databases. Unfortuantely in this comparison it implements only the ‘SELECT’ statement, but not the ‘UPDATE’ or ‘INSERT’ statements. AFAIK something like that is in planning stage (XQuery Update Facility 1.0). To have this new addition to XQuery in Qt would be great. The question is, what is the better or easier way to do: Implementing a not yet finalized standard, or implementing a feature, which traverses a QDomTree via XQuery, returns one or more QDomNodes, and thus allows to update the underlying QDomTree via the QDom-API.

]]> By: englich http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5490 englich Mon, 20 Oct 2008 09:03:05 +0000 http://englich.wordpress.com/?p=49#comment-5490 Guido: Glad that you liked it :) We currently don't have glue code between QDom and QtXmlPatterns because of legacy reasons: QDom has bugs that we can't fix due to historical reasons, and our plan is instead to supply new and better solutions(for instance, we're pondering the idea of a new tree API). But it makes indeed conceptually sense to be able to use XQuery/XSL-T on top of QDomNode. What your application's working flow that creates the need for this feature? For instance, would it be possible to do all processing in XQuery/XSL-T, or why is the reason to that the data needs to be in a QDom instance? Guido:
Glad that you liked it :)

We currently don’t have glue code between QDom and QtXmlPatterns because of legacy reasons: QDom has bugs that we can’t fix due to historical reasons, and our plan is instead to supply new and better solutions(for instance, we’re pondering the idea of a new tree API). But it makes indeed conceptually sense to be able to use XQuery/XSL-T on top of QDomNode.

What your application’s working flow that creates the need for this feature? For instance, would it be possible to do all processing in XQuery/XSL-T, or why is the reason to that the data needs to be in a QDom instance?

]]> By: Guido Seifert http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5489 Guido Seifert Fri, 17 Oct 2008 23:13:17 +0000 http://englich.wordpress.com/?p=49#comment-5489 I like the whole QtXmlPatterns stuff. Though I must say until after the "XQuery & Qt: Strong Tools for your XML Challenges" session during devDays in Munich it somehow escaped my attention. I was probably too used to use the QtXml module. Now I wonder if it would be possible to 'join' QtXml and QtXmlPatterns. Especially interesting would be the possibility to pass a QDomDocument to a QXmlQuery and get a QDomNode or a list of QDomNodes as result. I like the whole QtXmlPatterns stuff. Though I must say until after the “XQuery & Qt: Strong Tools for your XML Challenges” session during devDays in Munich it somehow escaped my attention. I was probably too used to use the QtXml module. Now I wonder if it would be possible to ‘join’ QtXml and QtXmlPatterns. Especially interesting would be the possibility to pass a QDomDocument to a QXmlQuery and get a QDomNode or a list of QDomNodes as result.

]]> By: englich http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5486 englich Mon, 15 Sep 2008 08:26:10 +0000 http://englich.wordpress.com/?p=49#comment-5486 Patrik: Yes, you'll want to call QXmlQuery::setFocus(), to supply your input document. Feel free to jump onto the qt-interest mailinglist; it's great for asking technical questions on Qt. Patrik:

Yes, you’ll want to call QXmlQuery::setFocus(), to supply your input document.

Feel free to jump onto the qt-interest mailinglist; it’s great for asking technical questions on Qt.

]]> By: Patrik http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5485 Patrik Sun, 14 Sep 2008 22:32:48 +0000 http://englich.wordpress.com/?p=49#comment-5485 Great tanks... on your sample: QXmlQuery myQuery(QXmlQuery::XSLT20); myQuery.bindVariable("myParam", QVariant("myValue"); myQuery.setQuery("style.xsl"); QFile out("outFile.xml"); out.open(QIODevice::WriteOnly); You dont take a xml data? or data is on xsl.. if i take data from mysql i write a xml tree and one "template" xsl and union this dwo file to outFile and how prepend xml data? other setQuery? I use gnome libxslt to union data two file + params in last 6 year.. But i like to use QXmlQuery::XSLT20 to make cristal report similar db query print. Great tanks…
on your sample:

QXmlQuery myQuery(QXmlQuery::XSLT20);
myQuery.bindVariable(“myParam”, QVariant(“myValue”);
myQuery.setQuery(“style.xsl”);
QFile out(“outFile.xml”);
out.open(QIODevice::WriteOnly);

You dont take a xml data? or data is on xsl..
if i take data from mysql i write a xml tree and one “template” xsl and union this dwo file to outFile and how prepend xml data? other setQuery?
I use gnome libxslt to union data two file + params in last 6 year.. But i like to use QXmlQuery::XSLT20 to make cristal report similar db query print.

]]> By: englich http://englich.wordpress.com/2008/09/10/xsl-t-and-qt/#comment-5484 englich Sun, 14 Sep 2008 17:14:56 +0000 http://englich.wordpress.com/?p=49#comment-5484 @Patrik: You'll need to: 1. Subclass QAbstractMessageHandler 2. Call QXmlQuery::setMessageHandler(&yourMessageHandler); @John: I know :) I actually went for the approach of rewriting XSL-T into XQuery code, but I've started to doubt it more and more as I've been progressing.. My plan is to write a paper on my implementation approach, but it will have to wait at least a couple of months. @Patrik:

You’ll need to:
1. Subclass QAbstractMessageHandler
2. Call QXmlQuery::setMessageHandler(&yourMessageHandler);

@John:
I know :) I actually went for the approach of rewriting XSL-T into XQuery code, but I’ve started to doubt it more and more as I’ve been progressing.. My plan is to write a paper on my implementation approach, but it will have to wait at least a couple of months.

]]>