From de2dadb8af67f9d425c3a8d2353a7d5b07588915 Mon Sep 17 00:00:00 2001 From: Nico Vertriest Date: Tue, 26 Jan 2016 14:38:00 +0100 Subject: Doc: removed links to QObject XML Model Example MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Uses Qt Webkit which is not part of 5.6 Task-number: QTBUG-43810 Change-Id: I89d74eb9555f04f90f930fa52a834997b5f1e99d Reviewed-by: Martin Smith Reviewed-by: Topi Reiniö --- examples/xmlpatterns/filetree/doc/src/filetree.qdoc | 16 +++++++--------- src/xmlpatterns/doc/src/xml-patterns.qdoc | 2 +- 2 files changed, 8 insertions(+), 10 deletions(-) diff --git a/examples/xmlpatterns/filetree/doc/src/filetree.qdoc b/examples/xmlpatterns/filetree/doc/src/filetree.qdoc index cf485ae..796861d 100644 --- a/examples/xmlpatterns/filetree/doc/src/filetree.qdoc +++ b/examples/xmlpatterns/filetree/doc/src/filetree.qdoc @@ -118,15 +118,13 @@ file system. At this point it is instructive to note that although the node model class for this example (\c{FileTree}) actually builds and contains the custom node model, building the custom node model - isn't always required. The node model class for the \l{QObject XML - Model Example} {QObject node model example} does not build its node - model but instead uses an already existing QObject tree as its node - model and just implements the callback interface for that already - existing data structure. In this file system example, however, - although we have an already existing data structure, i.e. the file - system, that data structure is not in memory and is not in a form we - can use. So we must build an analog of the file system in memory - from instances of QFileInfo, and we use that analog as the custom + isn't always required. For example, it is possible to use an already + existing QObject tree as a node model and just implement the callback + interface for that already existing data structure. In this file system + example, however, although we have an already existing data structure, + i.e. the file system, that data structure is not in memory and is not + in a form we can use. So we must build an analog of the file system in + memory from instances of QFileInfo, and we use that analog as the custom node model. The two sets of flags, \c{m_filterAllowAll} and \c{m_sortFlags}, diff --git a/src/xmlpatterns/doc/src/xml-patterns.qdoc b/src/xmlpatterns/doc/src/xml-patterns.qdoc index ae1ed3b..407e2d1 100644 --- a/src/xmlpatterns/doc/src/xml-patterns.qdoc +++ b/src/xmlpatterns/doc/src/xml-patterns.qdoc @@ -538,7 +538,7 @@ \li The set of D-Bus interfaces available in a system - \li A QObject hierarchy, as seen in the \l{QObject XML Model Example}. + \li A QObject hierarchy. \endlist -- cgit v1.2.1