diff options
Diffstat (limited to 'doc/xml-sax-features-walkthrough.doc')
-rw-r--r-- | doc/xml-sax-features-walkthrough.doc | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/xml-sax-features-walkthrough.doc b/doc/xml-sax-features-walkthrough.doc index ee054a63c..28b54b052 100644 --- a/doc/xml-sax-features-walkthrough.doc +++ b/doc/xml-sax-features-walkthrough.doc @@ -147,7 +147,7 @@ Finally we parse the document with the reader's default feature settings. Now we prepare for the parsing of the same XML input source with different reader settings. The output will be presented in -a second \l QListView, \e namespacePrefix. As it is the second +a second \l TQListView, \e namespacePrefix. As it is the second member of the \e container grid it will appear in the middle of the upper grid row. @@ -212,11 +212,11 @@ Let's have a brief look at the API of our handler class We derive it from the \l TQXmlDefaultHandler class that implements a handler that simply does nothing. -\printuntil QListView +\printuntil TQListView This makes it easy for us to implement only the functionality we in fact need. In our case this is the constructor that -takes a \l QListView as an argument, +takes a \l TQListView as an argument, \printline startElement \printuntil TQXmlAttributes @@ -244,7 +244,7 @@ structure we must however keep track of all elements that haven't been closed yet. To do this we use a LIFO stack -of QListItems. An element will be added to the stack when +of TQListItems. An element will be added to the stack when its start tag appears and removed as soon as its end tag is parsed. @@ -261,7 +261,7 @@ relevant functions. \quotefile xml/tagreader-with-features/structureparser.cpp \skipto include -\printuntil ntqlistview.h +\printuntil tqlistview.h \printline StructureParser \printuntil { @@ -272,7 +272,7 @@ its argument. \printline setListView \printuntil } -All we have to do here is to prepare the argument \l QListView +All we have to do here is to prepare the argument \l TQListView before usage. This we do with the \link #setListView() setListView() \endlink function. @@ -316,18 +316,18 @@ we're simply not interested in the local name of the element. \printline element Whenever an element occurs we want to show it in the listview. -Therefore we define a \l QListViewItem variable. +Therefore we define a \l TQListViewItem variable. \printline stack.isEmpty() \printline stack.top() As long as the element \e stack isn't empty the current element is a child of the topmost (last unclosed) element on the stack. Thus we -create a new \l QListViewItem as a child of TQPtrStack::stack.top() with +create a new \l TQListViewItem as a child of TQPtrStack::stack.top() with the new element's qualified name in the first column and the according namespace URI (or nothing) in the second one. -The QListViewItem is usally inserted as the first child. This means that we +The TQListViewItem is usally inserted as the first child. This means that we would get the elements in reverse order. So we first search for the last child of the TQPtrStack::stack.top() element and insert it after this element. @@ -339,7 +339,7 @@ the document root. \printline } The root element we have to handle separately because it is -the first element to go onto the \l QListViewItem stack. +the first element to go onto the \l TQListViewItem stack. Its listview item is therefore a direct child of the \e table listview itself. @@ -349,7 +349,7 @@ Now we put the element's listview item on top of the stack. \printline setOpen -By default a QListView presents all of its nodes closed. +By default a TQListView presents all of its nodes closed. The user may then click on the \e + icon to see the child entries. |