summaryrefslogtreecommitdiffstats
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/declarative/advtutorial.qdoc34
-rw-r--r--doc/src/declarative/animation.qdoc46
-rw-r--r--doc/src/declarative/basicelements.qdoc18
-rw-r--r--doc/src/declarative/basictypes.qdoc22
-rw-r--r--doc/src/declarative/behaviors-and-states.qdoc4
-rw-r--r--doc/src/declarative/codingconventions.qdoc16
-rw-r--r--doc/src/declarative/declarativeui.qdoc120
-rw-r--r--doc/src/declarative/dynamicobjects.qdoc18
-rw-r--r--doc/src/declarative/elements.qdoc170
-rw-r--r--doc/src/declarative/example-slideswitch.qdoc16
-rw-r--r--doc/src/declarative/examples.qdoc124
-rw-r--r--doc/src/declarative/extending-tutorial.qdoc46
-rw-r--r--doc/src/declarative/extending.qdoc16
-rw-r--r--doc/src/declarative/focus.qdoc14
-rw-r--r--doc/src/declarative/globalobject.qdoc94
-rw-r--r--doc/src/declarative/integrating.qdoc6
-rw-r--r--doc/src/declarative/javascriptblocks.qdoc16
-rw-r--r--doc/src/declarative/modules.qdoc36
-rw-r--r--doc/src/declarative/mouseevents.qdoc22
-rw-r--r--doc/src/declarative/network.qdoc12
-rw-r--r--doc/src/declarative/positioners.qdoc8
-rw-r--r--doc/src/declarative/qdeclarativedocument.qdoc14
-rw-r--r--doc/src/declarative/qdeclarativei18n.qdoc4
-rw-r--r--doc/src/declarative/qdeclarativeintro.qdoc4
-rw-r--r--doc/src/declarative/qdeclarativemodels.qdoc30
-rw-r--r--doc/src/declarative/qdeclarativeperformance.qdoc8
-rw-r--r--doc/src/declarative/qdeclarativesecurity.qdoc12
-rw-r--r--doc/src/declarative/qdeclarativestates.qdoc40
-rw-r--r--doc/src/declarative/qmlruntime.qdoc4
-rw-r--r--doc/src/declarative/qmlsyntax.qdoc4
-rw-r--r--doc/src/declarative/qmltexthandling.qdoc12
-rw-r--r--doc/src/declarative/qmlviewer.qdoc16
-rw-r--r--doc/src/declarative/qmlviews.qdoc8
-rw-r--r--doc/src/declarative/qmlwebkit.qdoc2
-rw-r--r--doc/src/declarative/qtbinding.qdoc152
-rw-r--r--doc/src/declarative/qtprogrammers.qdoc22
-rw-r--r--doc/src/declarative/qtquick-intro.qdoc16
-rw-r--r--doc/src/declarative/tutorial.qdoc6
-rw-r--r--doc/src/declarative/whatsnew.qdoc72
-rw-r--r--doc/src/examples/qml-examples.qdoc126
-rw-r--r--doc/src/examples/qml-extending.qdoc80
-rw-r--r--doc/src/getting-started/gettingstartedqml.qdoc20
-rw-r--r--doc/src/howtos/qmlbestpractices/qmlbestpractices-coding.qdoc4
43 files changed, 757 insertions, 757 deletions
diff --git a/doc/src/declarative/advtutorial.qdoc b/doc/src/declarative/advtutorial.qdoc
index 9624a37d..e50ec300 100644
--- a/doc/src/declarative/advtutorial.qdoc
+++ b/doc/src/declarative/advtutorial.qdoc
@@ -52,10 +52,10 @@ control QML elements.
Tutorial chapters:
\list 1
-\o \l {declarative/tutorials/samegame/samegame1}{Creating the Game Canvas and Blocks}
-\o \l {declarative/tutorials/samegame/samegame2}{Populating the Game Canvas}
-\o \l {declarative/tutorials/samegame/samegame3}{Implementing the Game Logic}
-\o \l {declarative/tutorials/samegame/samegame4}{Finishing Touches}
+\li \l {declarative/tutorials/samegame/samegame1}{Creating the Game Canvas and Blocks}
+\li \l {declarative/tutorials/samegame/samegame2}{Populating the Game Canvas}
+\li \l {declarative/tutorials/samegame/samegame3}{Implementing the Game Logic}
+\li \l {declarative/tutorials/samegame/samegame4}{Finishing Touches}
\endlist
All the code in this tutorial can be found in Qt's \c examples/declarative/tutorials/samegame
@@ -165,18 +165,18 @@ and moves the new block to its position on the game canvas. This involves severa
\list
-\o \l {QML:Qt::createComponent()}{Qt.createComponent()} is called to
+\li \l {QML:Qt::createComponent()}{Qt.createComponent()} is called to
generate an element from \c Block.qml. If the component is ready,
we can call \c createObject() to create an instance of the \c Block
item.
-\o If \c createObject() returned null (i.e. if there was an error
+\li If \c createObject() returned null (i.e. if there was an error
while loading the object), print the error information.
-\o Place the block in its position on the board and set its width and
+\li Place the block in its position on the board and set its width and
height. Also, store it in the blocks array for future reference.
-\o Finally, print error information to the console if the component
+\li Finally, print error information to the console if the component
could not be loaded for some reason (for example, if the file is
missing).
@@ -224,11 +224,11 @@ until it is won or lost.
To do this, we have added the following functions to \c samegame.js:
\list
-\o \c{handleClick(x,y)}
-\o \c{floodFill(xIdx,yIdx,type)}
-\o \c{shuffleDown()}
-\o \c{victoryCheck()}
-\o \c{floodMoveCheck(xIdx, yIdx, type)}
+\li \c{handleClick(x,y)}
+\li \c{floodFill(xIdx,yIdx,type)}
+\li \c{shuffleDown()}
+\li \c{victoryCheck()}
+\li \c{floodMoveCheck(xIdx, yIdx, type)}
\endlist
As this is a tutorial about QML, not game design, we will only discuss \c handleClick() and \c victoryCheck() below since they interface directly with the QML elements. Note that although the game logic here is written in JavaScript, it could have been written in C++ and then exposed to QML.
@@ -454,10 +454,10 @@ makes it very easy to fetch and display XML based data such as RSS in a QML appl
By following this tutorial you've seen how you can write a fully functional application in QML:
\list
-\o Build your application with \l {{QML Elements}}{QML elements}
-\o Add application logic \l{Integrating JavaScript}{with JavaScript code}
-\o Add animations with \l {Behavior}{Behaviors} and \l{QML States}{states}
-\o Store persistent application data using, for example, the \l{Offline Storage API} or \l XMLHttpRequest
+\li Build your application with \l {{QML Elements}}{QML elements}
+\li Add application logic \l{Integrating JavaScript}{with JavaScript code}
+\li Add animations with \l {Behavior}{Behaviors} and \l{QML States}{states}
+\li Store persistent application data using, for example, the \l{Offline Storage API} or \l XMLHttpRequest
\endlist
There is so much more to learn about QML that we haven't been able to cover in this tutorial. Check out all the
diff --git a/doc/src/declarative/animation.qdoc b/doc/src/declarative/animation.qdoc
index 0485717b..e9bf695a 100644
--- a/doc/src/declarative/animation.qdoc
+++ b/doc/src/declarative/animation.qdoc
@@ -36,27 +36,27 @@
\keyword qml-animation-elements
\section1 Animation and Transitions Elements
\list
-\o \l {Transition} - Animates transitions during state changes
-\o \l {SequentialAnimation} - Runs animations sequentially
-\o \l {ParallelAnimation} - Runs animations in parallel
-\o \l {Behavior} - Specifies a default animation for property changes
-\o \l {PropertyAction} - Sets immediate property changes during animation
-\o \l {PauseAnimation} - Introduces a pause in an animation
-\o \l {SmoothedAnimation} - Allows a property to smoothly track a value
-\o \l {SpringAnimation} - Allows a property to track a value in a spring-like motion
-\o \l {ScriptAction} - Runs scripts during an animation
+\li \l {Transition} - Animates transitions during state changes
+\li \l {SequentialAnimation} - Runs animations sequentially
+\li \l {ParallelAnimation} - Runs animations in parallel
+\li \l {Behavior} - Specifies a default animation for property changes
+\li \l {PropertyAction} - Sets immediate property changes during animation
+\li \l {PauseAnimation} - Introduces a pause in an animation
+\li \l {SmoothedAnimation} - Allows a property to smoothly track a value
+\li \l {SpringAnimation} - Allows a property to track a value in a spring-like motion
+\li \l {ScriptAction} - Runs scripts during an animation
\endlist
\keyword qml-property-animation-elements
Elements that animate properties based on data types
\list
-\o \l {PropertyAnimation} - Animates property changes
-\o \l {NumberAnimation} - Animates properties of type qreal
-\o \l {Vector3dAnimation} - Animates properties of type QVector3d
-\o \l {ColorAnimation} - Animates color changes
-\o \l {RotationAnimation} - Animates rotations
-\o \l {ParentAnimation} - Animates parent changes
-\o \l {AnchorAnimation} - Animates anchor changes
+\li \l {PropertyAnimation} - Animates property changes
+\li \l {NumberAnimation} - Animates properties of type qreal
+\li \l {Vector3dAnimation} - Animates properties of type QVector3d
+\li \l {ColorAnimation} - Animates color changes
+\li \l {RotationAnimation} - Animates rotations
+\li \l {ParentAnimation} - Animates parent changes
+\li \l {AnchorAnimation} - Animates anchor changes
\endlist
In QML, animations are created by applying animation elements to property
@@ -204,22 +204,22 @@ of the different easing types.
In addition, QML provides several other elements useful for animation:
\list
-\o PauseAnimation: enables pauses during animations
-\o ScriptAction: allows JavaScript to be executed during an animation, and can
+\li PauseAnimation: enables pauses during animations
+\li ScriptAction: allows JavaScript to be executed during an animation, and can
be used together with StateChangeScript to reused existing scripts
-\o PropertyAction: changes a property \e immediately during an animation,
+\li PropertyAction: changes a property \e immediately during an animation,
without animating the property change
\endlist
These are specialized animation elements that animate different property types
\list
-\o SmoothedAnimation: a specialized NumberAnimation that provides smooth
+\li SmoothedAnimation: a specialized NumberAnimation that provides smooth
changes in animation when the target value changes
-\o SpringAnimation: provides a spring-like animation with specialized
+\li SpringAnimation: provides a spring-like animation with specialized
attributes such as \l {SpringAnimation::}{mass},
\l{SpringAnimation::}{damping} and \l{SpringAnimation::}{epsilon}
-\o ParentAnimation: used for animating a parent change (see ParentChange)
-\o AnchorAnimation: used for animating an anchor change (see AnchorChanges)
+\li ParentAnimation: used for animating a parent change (see ParentChange)
+\li AnchorAnimation: used for animating an anchor change (see AnchorChanges)
\endlist
*/
diff --git a/doc/src/declarative/basicelements.qdoc b/doc/src/declarative/basicelements.qdoc
index 890efe29..a45bf2f3 100644
--- a/doc/src/declarative/basicelements.qdoc
+++ b/doc/src/declarative/basicelements.qdoc
@@ -40,15 +40,15 @@ scene.
\section1 Basic Elements
This is a list of some of the elements readily available for users.
\list
-\o \l {Item}
-\o \l {Rectangle}
-\o \l {Image}
-\o \l {Text}
-\o \l {TextInput}
-\o \l {TextEdit}
-\o \l {FocusScope}
-\o \l {Component}
-\o \l {MouseArea}
+\li \l {Item}
+\li \l {Rectangle}
+\li \l {Image}
+\li \l {Text}
+\li \l {TextInput}
+\li \l {TextEdit}
+\li \l {FocusScope}
+\li \l {Component}
+\li \l {MouseArea}
\endlist
For a complete list of QML elements, please visit the \l {QML Elements} page.
diff --git a/doc/src/declarative/basictypes.qdoc b/doc/src/declarative/basictypes.qdoc
index 34ddd92c..82bf5a68 100644
--- a/doc/src/declarative/basictypes.qdoc
+++ b/doc/src/declarative/basictypes.qdoc
@@ -324,12 +324,12 @@
A font type has the properties of a QFont. The properties are:
\list
- \o \c string font.family
- \o \c bool font.bold
- \o \c bool font.italic
- \o \c bool font.underline
- \o \c real font.pointSize
- \o \c int font.pixelSize
+ \li \c string font.family
+ \li \c bool font.bold
+ \li \c bool font.italic
+ \li \c bool font.underline
+ \li \c real font.pointSize
+ \li \c int font.pixelSize
\endlist
Example:
@@ -350,9 +350,9 @@
are:
\list
- \o \c slot action.trigger - invoke the action
- \o \c bool action.enabled - true if the action is enabled
- \o \c string action.text - the text associated with the action
+ \li \c slot action.trigger - invoke the action
+ \li \c bool action.enabled - true if the action is enabled
+ \li \c string action.text - the text associated with the action
\endlist
Actions are used like this:
@@ -442,8 +442,8 @@
The \c variant type can also hold:
\list
- \o An array of \l {QML Basic Types}{basic type} values
- \o A map of key-value pairs with \l {QML Basic Types}{basic-type} values
+ \li An array of \l {QML Basic Types}{basic type} values
+ \li A map of key-value pairs with \l {QML Basic Types}{basic-type} values
\endlist
For example, below is an \c items array and an \c attributes map. Their
diff --git a/doc/src/declarative/behaviors-and-states.qdoc b/doc/src/declarative/behaviors-and-states.qdoc
index 7b6ed1dd..9de42302 100644
--- a/doc/src/declarative/behaviors-and-states.qdoc
+++ b/doc/src/declarative/behaviors-and-states.qdoc
@@ -77,8 +77,8 @@ problem occurs because we have used a Behavior to animate the change in color, a
To state the problem more formally, using States and Behaviors together can cause unexpected behavior when:
\list
-\o a Behavior is used to animate a property change, specifically when moving from an explicitly defined state back to the implicit base state; and
-\o this Behavior can be interrupted to (re-)enter an explicitly defined state.
+\li a Behavior is used to animate a property change, specifically when moving from an explicitly defined state back to the implicit base state; and
+\li this Behavior can be interrupted to (re-)enter an explicitly defined state.
\endlist
The problem occurs because of the way the base state is defined for QML: as the "snapshot" state of the application just prior to entering an explicitly defined state. In this case, if we are in the process of animating from green back
diff --git a/doc/src/declarative/codingconventions.qdoc b/doc/src/declarative/codingconventions.qdoc
index a3338434..335f91f1 100644
--- a/doc/src/declarative/codingconventions.qdoc
+++ b/doc/src/declarative/codingconventions.qdoc
@@ -40,14 +40,14 @@ If you need an introduction to the language, please read \l {Introduction to the
Through our documentation and examples, QML objects are always structured in the following order:
\list
-\o id
-\o property declarations
-\o signal declarations
-\o JavaScript functions
-\o object properties
-\o child objects
-\o states
-\o transitions
+\li id
+\li property declarations
+\li signal declarations
+\li JavaScript functions
+\li object properties
+\li child objects
+\li states
+\li transitions
\endlist
For better readability, we separate these different parts with an empty line.
diff --git a/doc/src/declarative/declarativeui.qdoc b/doc/src/declarative/declarativeui.qdoc
index dea971a2..780e63c4 100644
--- a/doc/src/declarative/declarativeui.qdoc
+++ b/doc/src/declarative/declarativeui.qdoc
@@ -46,94 +46,94 @@ Qt applications.
\section1 Getting Started
\list
-\o \l{Introduction to Qt Quick}
-\o \l{QML for Qt Programmers}{QML Programming for Qt Programmers}
-\o \l{Getting Started Programming with QML}
+\li \l{Introduction to Qt Quick}
+\li \l{QML for Qt Programmers}{QML Programming for Qt Programmers}
+\li \l{Getting Started Programming with QML}
-\o \l{What's new in Qt Quick}{What's New in the Qt Quick Release}
-\o \l{QML Examples and Demos}
+\li \l{What's new in Qt Quick}{What's New in the Qt Quick Release}
+\li \l{QML Examples and Demos}
\endlist
\section1 QML Features
\list
-\o \l{QML Basic Elements}{Basic Elements}
-\o \l{QML Basic Types}{Data Types}
-\o \l{Property Binding}
-\o \l{Using QML Positioner and Repeater Items}{Component Layouts}
-\o \l{Anchor-based Layout in QML}{Layouts using Anchors}
-\o \l{QML Mouse Events}{Mouse Events}
-\o \l{QML Text Handling and Validators}{Text Handling and Validators}
-\o \l{Keyboard Focus in QML}{Keyboard Focus}
-\o \l{QML Signal and Handler Event System}{Signal and Handler Event System}
-\o \l{Importing Reusable Components}
-\o \l{QML States}{States}
-\o \l{QML Animation and Transitions}{Animation and Transitions}
-\o \l{QML Data Models}{Structuring Data with Models}
-\o \l{Presenting Data with Views}
-\o \l{Extending QML Functionalities using C++}
-\o \l{Using QML Bindings in C++ Applications}
-\o \l{Integrating QML Code with Existing Qt UI Code}
-\o \l{Dynamic Object Management in QML}{Dynamic Object Management}
-\o \l{Network Transparency}{Loading Resources in QML}
-\o \l{QML Internationalization}{Internationalization}
+\li \l{QML Basic Elements}{Basic Elements}
+\li \l{QML Basic Types}{Data Types}
+\li \l{Property Binding}
+\li \l{Using QML Positioner and Repeater Items}{Component Layouts}
+\li \l{Anchor-based Layout in QML}{Layouts using Anchors}
+\li \l{QML Mouse Events}{Mouse Events}
+\li \l{QML Text Handling and Validators}{Text Handling and Validators}
+\li \l{Keyboard Focus in QML}{Keyboard Focus}
+\li \l{QML Signal and Handler Event System}{Signal and Handler Event System}
+\li \l{Importing Reusable Components}
+\li \l{QML States}{States}
+\li \l{QML Animation and Transitions}{Animation and Transitions}
+\li \l{QML Data Models}{Structuring Data with Models}
+\li \l{Presenting Data with Views}
+\li \l{Extending QML Functionalities using C++}
+\li \l{Using QML Bindings in C++ Applications}
+\li \l{Integrating QML Code with Existing Qt UI Code}
+\li \l{Dynamic Object Management in QML}{Dynamic Object Management}
+\li \l{Network Transparency}{Loading Resources in QML}
+\li \l{QML Internationalization}{Internationalization}
\endlist
\section1 QML Add-Ons
\list
-\o \l{Qt Quick Components for Symbian 1.1}{Qt Quick Components for Symbian} - a native component set for the Symbian^3 platform
-\o \l{QtWebKit QML Module}
-\o \l{http://doc.qt.nokia.com/qtmobility-1.1.0/qml-plugins.html}{Mobility QML Plugins}
-\o \l {http://doc.qt.nokia.com/qt-components-symbian-1.1/index.html}{Qt Quick Components}
+\li \l{Qt Quick Components for Symbian 1.1}{Qt Quick Components for Symbian} - a native component set for the Symbian^3 platform
+\li \l{QtWebKit QML Module}
+\li \l{http://doc.qt.nokia.com/qtmobility-1.1.0/qml-plugins.html}{Mobility QML Plugins}
+\li \l {http://doc.qt.nokia.com/qt-components-symbian-1.1/index.html}{Qt Quick Components}
\endlist
\section1 Qt Quick Tools
\list
-\o \l{Debugging QML}
-\o \l{external: Developing Qt Quick Applications with Creator}{Developing with Qt Creator}
-\o \l{QML Viewer}
+\li \l{Debugging QML}
+\li \l{external: Developing Qt Quick Applications with Creator}{Developing with Qt Creator}
+\li \l{QML Viewer}
\endlist
\section1 Reference
\list
-\o \l{Introduction to the QML language}{QML Syntax}
-\o \l{QML Elements}
-\o \l{Qt Declarative Module}
-\o \l{QML Basic Types}{QML Data Types}
-\o \l{QML Coding Conventions}
-\o \l{external: Qt Creator Manual}{Qt Creator Manual}
-\o \l{Programming with Qt}
-\o \l{http://doc.qt.nokia.com/qtmobility-1.1.0/index.html}{Qt Mobility Documentation}
+\li \l{Introduction to the QML language}{QML Syntax}
+\li \l{QML Elements}
+\li \l{Qt Declarative Module}
+\li \l{QML Basic Types}{QML Data Types}
+\li \l{QML Coding Conventions}
+\li \l{external: Qt Creator Manual}{Qt Creator Manual}
+\li \l{Programming with Qt}
+\li \l{http://doc.qt.nokia.com/qtmobility-1.1.0/index.html}{Qt Mobility Documentation}
\endlist
\section1 Architecture
\list
-\o \l{Qt Declarative UI Runtime}
-\o \l{Integrating JavaScript}
-\o \l{QML Scope}
-\o \l{QML Modules}
-\o \l{QML Documents}
-\o \l{QML Global Object}
-\o \l{QML Internationalization}
-\o \l{QML Right-to-left User Interfaces}
-\o \l{QML Security}
-\o \l{Qt Declarative Module}
+\li \l{Qt Declarative UI Runtime}
+\li \l{Integrating JavaScript}
+\li \l{QML Scope}
+\li \l{QML Modules}
+\li \l{QML Documents}
+\li \l{QML Global Object}
+\li \l{QML Internationalization}
+\li \l{QML Right-to-left User Interfaces}
+\li \l{QML Security}
+\li \l{Qt Declarative Module}
\endlist
\section1 Examples
\list
-\o \l{QML Tutorial}{"Hello World" Tutorial}
-\o \l{Getting Started Programming with QML}
-\o \l{QML Advanced Tutorial}{Tutorial: "Same Game"}
-\o \l{Tutorial: Writing QML extensions with C++}
-\o \l{QML Examples and Demos}
+\li \l{QML Tutorial}{"Hello World" Tutorial}
+\li \l{Getting Started Programming with QML}
+\li \l{QML Advanced Tutorial}{Tutorial: "Same Game"}
+\li \l{Tutorial: Writing QML extensions with C++}
+\li \l{QML Examples and Demos}
-\o Forum Nokia:
+\li Forum Nokia:
\l{http://wiki.forum.nokia.com/index.php/Qt_Quick_examples_for_porting}{Qt Quick
examples for porting}
\endlist
@@ -141,19 +141,19 @@ examples for porting}
\section1 Best Practices
\list
-\o \l{QML Best Practices: Coding Conventions}{Coding Tips}
-\o \l{QML Performance}{Performance Tips}
+\li \l{QML Best Practices: Coding Conventions}{Coding Tips}
+\li \l{QML Performance}{Performance Tips}
\endlist
\section1 License Information
\list
-\o \l{Qt Quick Licensing Information}
+\li \l{Qt Quick Licensing Information}
\endlist
\section1 Online Examples
\list
-\o Forum Nokia:
+\li Forum Nokia:
\l{http://wiki.forum.nokia.com/index.php/Qt_Quick_examples_for_porting}{Qt Quick
examples for porting}
\endlist
diff --git a/doc/src/declarative/dynamicobjects.qdoc b/doc/src/declarative/dynamicobjects.qdoc
index fdb610c6..681ef304 100644
--- a/doc/src/declarative/dynamicobjects.qdoc
+++ b/doc/src/declarative/dynamicobjects.qdoc
@@ -69,10 +69,10 @@ a \l Component object from this URL.
Once you have a \l Component, you can call its \l {Component::createObject()}{createObject()} method to create an instance of
the component. This function can take one or two arguments:
\list
-\o The first is the parent for the new item. Since graphical items will not appear on the scene without a parent, it is
+\li The first is the parent for the new item. Since graphical items will not appear on the scene without a parent, it is
recommended that you set the parent this way. However, if you wish to set the parent later you can safely pass \c null to
this function.
-\o The second is optional and is a map of property-value items that define initial any property values for the item.
+\li The second is optional and is a map of property-value items that define initial any property values for the item.
Property values specified by this argument are applied to the object before its creation is finalized, avoiding
binding errors that may occur if particular properties must be initialized to enable other property bindings.
when certain properties have been bound to before they have been set by the code. Additionally, there are small
@@ -145,11 +145,11 @@ the bindings in the dynamic item will no longer work.
The actual creation context depends on how an item is created:
\list
-\o If \l {QML:Qt::createComponent()}{Qt.createComponent()} is used, the creation context
+\li If \l {QML:Qt::createComponent()}{Qt.createComponent()} is used, the creation context
is the QDeclarativeContext in which this method is called
-\o If \l{QML:Qt::createQmlObject()}{Qt.createQmlObject()}
+\li If \l{QML:Qt::createQmlObject()}{Qt.createQmlObject()}
if called, the creation context is the context of the parent item passed to this method
-\o If a \c {Component{}} item is defined and \l {Component::createObject()}{createObject()}
+\li If a \c {Component{}} item is defined and \l {Component::createObject()}{createObject()}
is called on that item, the creation context is the context in which the \c Component is defined
\endlist
@@ -178,12 +178,12 @@ component. Each instance runs a NumberAnimation, and when the animation has fini
\table
\row
-\o \c application.qml
-\o \c SelfDestroyingRect.qml
+\li \c application.qml
+\li \c SelfDestroyingRect.qml
\row
-\o \snippet doc/src/snippets/declarative/dynamicObjects-destroy.qml 0
-\o \snippet doc/src/snippets/declarative/SelfDestroyingRect.qml 0
+\li \snippet doc/src/snippets/declarative/dynamicObjects-destroy.qml 0
+\li \snippet doc/src/snippets/declarative/SelfDestroyingRect.qml 0
\endtable
diff --git a/doc/src/declarative/elements.qdoc b/doc/src/declarative/elements.qdoc
index f5915141..48f943b7 100644
--- a/doc/src/declarative/elements.qdoc
+++ b/doc/src/declarative/elements.qdoc
@@ -43,149 +43,149 @@ To see the QML elements listed by functional area, see the
\section1 Basic QML Elements
\list
-\o \l {Item} - Basic item element inherited by QML elements
-\o \l {Component} - Encapsulates QML elements during importing
-\o \l {QML:QtObject} {QtObject} - Basic element containing only the \c {objectName} property
+\li \l {Item} - Basic item element inherited by QML elements
+\li \l {Component} - Encapsulates QML elements during importing
+\li \l {QML:QtObject} {QtObject} - Basic element containing only the \c {objectName} property
\endlist
\section1 Graphics
\list
-\o \l {Rectangle} - A rectangle element
-\o \l {Image} - For incorporating bitmaps into a scene
-\o \l {BorderImage} - Allows the use of images as borders
-\o \l {AnimatedImage} - For playing animations stored in a series of frames
-\o \l {Gradient} - For defining a color gradient
-\o \l {GradientStop} - Used to define a color within a \l {Gradient}
-\o \l {SystemPalette} - Provides access to the Qt palettes
+\li \l {Rectangle} - A rectangle element
+\li \l {Image} - For incorporating bitmaps into a scene
+\li \l {BorderImage} - Allows the use of images as borders
+\li \l {AnimatedImage} - For playing animations stored in a series of frames
+\li \l {Gradient} - For defining a color gradient
+\li \l {GradientStop} - Used to define a color within a \l {Gradient}
+\li \l {SystemPalette} - Provides access to the Qt palettes
\endlist
\section1 Text Handling
\list
-\o \l {Text} - For inserting formatted text into a scene
-\o \l {TextInput} - Captures user key input
-\o \l {TextEdit} - Displays multiple lines of editable formatted text
-\o \l {IntValidator} - Validates values as integers
-\o \l {DoubleValidator} - Validates real values
-\o \l {RegExpValidator} - Validator for string regular expressions
-\o \l {FontLoader} - Loads fonts by name or URL
+\li \l {Text} - For inserting formatted text into a scene
+\li \l {TextInput} - Captures user key input
+\li \l {TextEdit} - Displays multiple lines of editable formatted text
+\li \l {IntValidator} - Validates values as integers
+\li \l {DoubleValidator} - Validates real values
+\li \l {RegExpValidator} - Validator for string regular expressions
+\li \l {FontLoader} - Loads fonts by name or URL
\endlist
\section1 Mouse and Interaction Area
\list
-\o \l {MouseArea} - Sets up an area for mouse interaction
-\o \l {Keys} - Provides components with attached properties to handle key input.
-\o \l {FocusScope} - Element that mediate keyboard focus changes
-\o \l {Flickable} - Provides a surface that can be "flicked"
-\o \l {Flipable} - Provides a surface that produces "flipping" effects
-\o \l {PinchArea} - Enables simple pinch gesture handling
+\li \l {MouseArea} - Sets up an area for mouse interaction
+\li \l {Keys} - Provides components with attached properties to handle key input.
+\li \l {FocusScope} - Element that mediate keyboard focus changes
+\li \l {Flickable} - Provides a surface that can be "flicked"
+\li \l {Flipable} - Provides a surface that produces "flipping" effects
+\li \l {PinchArea} - Enables simple pinch gesture handling
\endlist
\section1 Positioners and Repeater
\list
-\o \l {Column} - Arranges its children vertically
-\o \l {Row} - Arranges its children horizontally
-\o \l {Grid} - Positions its children in a grid
-\o \l {Flow} - Positions its children with wrapping support
-\o \l {Repeater} - Uses a model to create multiple components
+\li \l {Column} - Arranges its children vertically
+\li \l {Row} - Arranges its children horizontally
+\li \l {Grid} - Positions its children in a grid
+\li \l {Flow} - Positions its children with wrapping support
+\li \l {Repeater} - Uses a model to create multiple components
\endlist
\section1 Transformations
\list
-\o \l {Scale} - Assigns item scaling behaviors
-\o \l {Rotation} - Assigns item rotation behaviors
-\o \l {Translate} - Assigns item translation behaviors
+\li \l {Scale} - Assigns item scaling behaviors
+\li \l {Rotation} - Assigns item rotation behaviors
+\li \l {Translate} - Assigns item translation behaviors
\endlist
\section1 States
\list
-\o \l {State} - Defines sets of configurations of objects and properties
-\o \l {PropertyChanges} - Describes property changes within a state
-\o \l {StateGroup} - Contains a set of states and state transitions
-\o \l {StateChangeScript} - Allows script binding in a state
-\o \l {ParentChange} - Re-parent an Item in a state change
-\o \l {AnchorChanges} - Change the anchors of an item in a state
+\li \l {State} - Defines sets of configurations of objects and properties
+\li \l {PropertyChanges} - Describes property changes within a state
+\li \l {StateGroup} - Contains a set of states and state transitions
+\li \l {StateChangeScript} - Allows script binding in a state
+\li \l {ParentChange} - Re-parent an Item in a state change
+\li \l {AnchorChanges} - Change the anchors of an item in a state
\endlist
\section1 Animation and Transitions
\list
-\o \l {Transition} - Animates transitions during state changes
-\o \l {SequentialAnimation} - Runs animations sequentially
-\o \l {ParallelAnimation} - Runs animations in parallel
-\o \l {Behavior} - Specifies a default animation for property changes
-\o \l {PropertyAction} - Sets immediate property changes during animation
-\o \l {PauseAnimation} - Introduces a pause in an animation
-\o \l {SmoothedAnimation} - Allows a property to smoothly track a value
-\o \l {SpringAnimation} - Allows a property to track a value in a spring-like motion
-\o \l {ScriptAction} - Runs scripts during an animation
+\li \l {Transition} - Animates transitions during state changes
+\li \l {SequentialAnimation} - Runs animations sequentially
+\li \l {ParallelAnimation} - Runs animations in parallel
+\li \l {Behavior} - Specifies a default animation for property changes
+\li \l {PropertyAction} - Sets immediate property changes during animation
+\li \l {PauseAnimation} - Introduces a pause in an animation
+\li \l {SmoothedAnimation} - Allows a property to smoothly track a value
+\li \l {SpringAnimation} - Allows a property to track a value in a spring-like motion
+\li \l {ScriptAction} - Runs scripts during an animation
\endlist
Elements that animate properties based on data types
\list
-\o \l {PropertyAnimation} - Animates property changes
-\o \l {NumberAnimation} - Animates properties of type qreal
-\o \l {Vector3dAnimation} - Animates properties of type QVector3d
-\o \l {ColorAnimation} - Animates color changes
-\o \l {RotationAnimation} - Animates rotations
-\o \l {ParentAnimation} - Animates parent changes
-\o \l {AnchorAnimation} - Animates anchor changes
+\li \l {PropertyAnimation} - Animates property changes
+\li \l {NumberAnimation} - Animates properties of type qreal
+\li \l {Vector3dAnimation} - Animates properties of type QVector3d
+\li \l {ColorAnimation} - Animates color changes
+\li \l {RotationAnimation} - Animates rotations
+\li \l {ParentAnimation} - Animates parent changes
+\li \l {AnchorAnimation} - Animates anchor changes
\endlist
\section1 Models and Data Handling
\list
-\o \l {ListModel} - Defines a list of data
-\o \l {ListElement} - Defines a data item in a \l {ListModel}
-\o \l {VisualItemModel} - Contains items that already defines its own visual delegate
-\o \l {VisualDataModel} - Encapsulates a model and a delegate
-\o \l {XmlListModel} - Specifies a model using XPath expressions
-\o \l {XmlRole} - Specifies a role for an \l {XmlListModel}
-\o \l {Binding} - Binds any value to any property
-\o \l {Package} - Collection that enables sharing of items within different views
+\li \l {ListModel} - Defines a list of data
+\li \l {ListElement} - Defines a data item in a \l {ListModel}
+\li \l {VisualItemModel} - Contains items that already defines its own visual delegate
+\li \l {VisualDataModel} - Encapsulates a model and a delegate
+\li \l {XmlListModel} - Specifies a model using XPath expressions
+\li \l {XmlRole} - Specifies a role for an \l {XmlListModel}
+\li \l {Binding} - Binds any value to any property
+\li \l {Package} - Collection that enables sharing of items within different views
\endlist
\section1 Views
\list
-\o \l {ListView} - Provides a list visualization of a model
-\o \l {GridView} - Provides a grid visualization of a model
-\o \l {PathView} - Visualizes a model's contents along a path. See \l {Path Definition}{Path Elements} for more information.
+\li \l {ListView} - Provides a list visualization of a model
+\li \l {GridView} - Provides a grid visualization of a model
+\li \l {PathView} - Visualizes a model's contents along a path. See \l {Path Definition}{Path Elements} for more information.
\endlist
\section1 Path Definition
\list
-\o \l {Path} - Defines a path used by \l {PathView}
-\o \l {PathLine} - Defines a line in \l {Path}
-\o \l {PathQuad} - Defines a quadratic Bezier curve in a \l {Path}
-\o \l {PathCubic} - Defines a cubic Bezier curve in a \l {Path}
-\o \l {PathAttribute} - Allows the setting of attributes along a \l {Path}
-\o \l {PathPercent} - Modifies the item distribution along a \l {Path}
+\li \l {Path} - Defines a path used by \l {PathView}
+\li \l {PathLine} - Defines a line in \l {Path}
+\li \l {PathQuad} - Defines a quadratic Bezier curve in a \l {Path}
+\li \l {PathCubic} - Defines a cubic Bezier curve in a \l {Path}
+\li \l {PathAttribute} - Allows the setting of attributes along a \l {Path}
+\li \l {PathPercent} - Modifies the item distribution along a \l {Path}
\endlist
\section1 Utility
\list
-\o \l {Connections} - Explicitly connects signals and signal handlers
-\o \l {Timer} - Provides timed triggers
-\o \l {QML:Qt} {Qt} - The QML global Qt object provides useful enums and functions from Qt.
-\o \l {WorkerScript} - Enables the use of threads in QML
-\o \l {Loader} - Controls the loading of items or components
-\o \l {LayoutItem} - Allows declarative UI elements inside Qt's Graphics View layouts
+\li \l {Connections} - Explicitly connects signals and signal handlers
+\li \l {Timer} - Provides timed triggers
+\li \l {QML:Qt} {Qt} - The QML global Qt object provides useful enums and functions from Qt.
+\li \l {WorkerScript} - Enables the use of threads in QML
+\li \l {Loader} - Controls the loading of items or components
+\li \l {LayoutItem} - Allows declarative UI elements inside Qt's Graphics View layouts
\endlist
\section1 Graphical Effects
\list
-\o \l {Particles} - Generates and animates particles
-\o \l {ParticleMotionLinear} - Adds linear motion behavior to \l {Particles}
-\o \l {ParticleMotionGravity} - Adds gravitational motion to \l {Particles}
-\o \l {ParticleMotionWander} - Adds varied motions to \l {Particles}
-\o \l {ShaderEffectItem} - Enables the use of OpenGL Shading Language together with QML
-\o \l {ShaderEffectSource} - Encapsulates QML item tree as a source item for \l {ShaderEffectItem}
+\li \l {Particles} - Generates and animates particles
+\li \l {ParticleMotionLinear} - Adds linear motion behavior to \l {Particles}
+\li \l {ParticleMotionGravity} - Adds gravitational motion to \l {Particles}
+\li \l {ParticleMotionWander} - Adds varied motions to \l {Particles}
+\li \l {ShaderEffectItem} - Enables the use of OpenGL Shading Language together with QML
+\li \l {ShaderEffectSource} - Encapsulates QML item tree as a source item for \l {ShaderEffectItem}
\endlist
\section1 Add-On Elements
These elements are not included in the \c{QtQuick 1.0} module. Their respective QML bindings
should first be obtained and installed.
\list
-\o \l{WebView}{QtWebKit QML Module - WebView Element} - For displaying Web contents
-\o \l{http://doc.qt.nokia.com/qtmobility-1.1.0/qml-plugins.html}{Mobility QML Plugins}
-\o \l {http://doc.qt.nokia.com/qt-components-symbian-1.1/index.html}{Qt Quick Components}
+\li \l{WebView}{QtWebKit QML Module - WebView Element} - For displaying Web contents
+\li \l{http://doc.qt.nokia.com/qtmobility-1.1.0/qml-plugins.html}{Mobility QML Plugins}
+\li \l {http://doc.qt.nokia.com/qt-components-symbian-1.1/index.html}{Qt Quick Components}
\endlist
*/
diff --git a/doc/src/declarative/example-slideswitch.qdoc b/doc/src/declarative/example-slideswitch.qdoc
index 86d4090e..26d2b2f7 100644
--- a/doc/src/declarative/example-slideswitch.qdoc
+++ b/doc/src/declarative/example-slideswitch.qdoc
@@ -36,12 +36,12 @@ The code for this example can be found in the \c $QTDIR/examples/declarative/ui-
The elements that compose the switch are:
\list
-\o a \c on property (the interface to interact with the switch),
-\o two images (the background image and the knob),
-\o two mouse regions for user interation (on the background image and on the knob),
-\o two states (a \e on state and a \e off state),
-\o two functions or slots to react to the user interation (\c toggle() and \c dorelease()),
-\o and a transition that describe how to go from one state to the other.
+\li a \c on property (the interface to interact with the switch),
+\li two images (the background image and the knob),
+\li two mouse regions for user interation (on the background image and on the knob),
+\li two states (a \e on state and a \e off state),
+\li two functions or slots to react to the user interation (\c toggle() and \c dorelease()),
+\li and a transition that describe how to go from one state to the other.
\endlist
\section1 Switch.qml
@@ -92,8 +92,8 @@ in the \c dorelease() function that is called in the \c onReleased property.
We define the two states of the switch:
\list
-\o In the \e on state the knob is on the right (\c x position is 78) and the \c on property is \c true.
-\o In the \e off state the knob is on the left (\c x position is 1) and the \c on property is \c false.
+\li In the \e on state the knob is on the right (\c x position is 78) and the \c on property is \c true.
+\li In the \e off state the knob is on the left (\c x position is 1) and the \c on property is \c false.
\endlist
For more information on states see \l{qmlstates}{QML States}.
diff --git a/doc/src/declarative/examples.qdoc b/doc/src/declarative/examples.qdoc
index 80e5d186..966b224f 100644
--- a/doc/src/declarative/examples.qdoc
+++ b/doc/src/declarative/examples.qdoc
@@ -60,43 +60,43 @@ can be used to produce sophisticated interfaces and applications:
\table
\row
-\o
+\li
\l{demos/declarative/calculator}{Calculator}
\image qml-calculator-example-small.png
-\o
+\li
\l{demos/declarative/flickr}{Flickr Mobile}
\image qml-flickr-demo-small.png
-\o
+\li
\l{demos/declarative/minehunt}{Minehunt}
\image qml-minehunt-demo-small.png
\row
-\o
+\li
\l{demos/declarative/photoviewer}{Photo Viewer}
\image qml-photoviewer-demo-small.png
-\o
+\li
\l{demos/declarative/rssnews}{RSS News Reader}
\image qml-rssnews-demo-small.png
-\o
+\li
\l{demos/declarative/samegame}{Same Game}
\image qml-samegame-demo-small.png
\row
-\o
+\li
\l{demos/declarative/snake}{Snake}
\image qml-snake-demo-small.png
-\o
+\li
\l{demos/declarative/twitter}{Twitter}
\image qml-twitter-demo-small.png
-\o
+\li
\l{demos/declarative/webbrowser}{Web Browser}
\image qml-webbrowser-demo-small.png
@@ -116,127 +116,127 @@ The examples can be found in Qt's \c examples/declarative directory.
\section2 Animation
\list
-\o \l{declarative/animation/basics/color-animation}{Color Animation}
-\o \l{declarative/animation/behaviors/behavior-example}{Behaviors}
-\o \l{declarative/animation/easing}{Easing}
-\o \l{declarative/animation/basics/property-animation}{Property Animation}
-\o \l{declarative/animation/states}{States}
-\o \l{declarative/animation/behaviors/wigglytext}{Wiggly Text}
+\li \l{declarative/animation/basics/color-animation}{Color Animation}
+\li \l{declarative/animation/behaviors/behavior-example}{Behaviors}
+\li \l{declarative/animation/easing}{Easing}
+\li \l{declarative/animation/basics/property-animation}{Property Animation}
+\li \l{declarative/animation/states}{States}
+\li \l{declarative/animation/behaviors/wigglytext}{Wiggly Text}
\endlist
\section2 Image Elements
\list
-\o \l{declarative/imageelements/borderimage}{BorderImage}
-\o \l{declarative/imageelements/image}{Image}
+\li \l{declarative/imageelements/borderimage}{BorderImage}
+\li \l{declarative/imageelements/image}{Image}
\endlist
\section2 Text
\list
-\o \l{declarative/text/fonts}{Fonts}
-\o \l{declarative/text/textselection}{Text Selection}
+\li \l{declarative/text/fonts}{Fonts}
+\li \l{declarative/text/textselection}{Text Selection}
\endlist
\section2 Positioners
\list
-\o \l{declarative/positioners}{Example}
+\li \l{declarative/positioners}{Example}
\endlist
\section2 Key Interaction
\list
-\o \l{declarative/keyinteraction/focus}{Focus}
+\li \l{declarative/keyinteraction/focus}{Focus}
\endlist
\section2 Touch Interaction
\list
-\o \l{declarative/touchinteraction/mousearea}{MouseArea}
+\li \l{declarative/touchinteraction/mousearea}{MouseArea}
\endlist
\section2 UI Components
\list
-\o \l{declarative/ui-components/dialcontrol}{Dial control}
-\o \l{declarative/ui-components/flipable}{Flipable}
-\o \l{declarative/ui-components/progressbar}{Progress bar}
-\o \l{declarative/ui-components/scrollbar}{Scroll bar}
-\o \l{declarative/ui-components/searchbox}{Search box}
-\o \l{declarative/ui-components/slideswitch}{Slide switch}
-\o \l{declarative/ui-components/spinner}{Spinner}
-\o \l{declarative/ui-components/tabwidget}{Tab widget}
+\li \l{declarative/ui-components/dialcontrol}{Dial control}
+\li \l{declarative/ui-components/flipable}{Flipable}
+\li \l{declarative/ui-components/progressbar}{Progress bar}
+\li \l{declarative/ui-components/scrollbar}{Scroll bar}
+\li \l{declarative/ui-components/searchbox}{Search box}
+\li \l{declarative/ui-components/slideswitch}{Slide switch}
+\li \l{declarative/ui-components/spinner}{Spinner}
+\li \l{declarative/ui-components/tabwidget}{Tab widget}
\endlist
\section2 Toys
\list
-\o \l{declarative/toys/clocks}{Clocks}
-\o \l{declarative/toys/corkboards}{Corkboards}
-\o \l{declarative/toys/dynamicscene}{Dynamic Scene}
-\o \l{declarative/toys/tic-tac-toe}{Tic Tac Toe}
-\o \l{declarative/toys/tvtennis}{TV Tennis}
+\li \l{declarative/toys/clocks}{Clocks}
+\li \l{declarative/toys/corkboards}{Corkboards}
+\li \l{declarative/toys/dynamicscene}{Dynamic Scene}
+\li \l{declarative/toys/tic-tac-toe}{Tic Tac Toe}
+\li \l{declarative/toys/tvtennis}{TV Tennis}
\endlist
\section2 Models and Views
\list
-\o \l{declarative/modelviews/gridview}{GridView}
-\o \l{Models and Views: ListView Examples}{ListView}
-\o \l{declarative/modelviews/pathview}{PathView}
-\o \l{declarative/modelviews/package}{Package}
-\o \l{declarative/modelviews/parallax}{Parallax}
-\o \l{declarative/modelviews/visualitemmodel}{VisualItemModel}
+\li \l{declarative/modelviews/gridview}{GridView}
+\li \l{Models and Views: ListView Examples}{ListView}
+\li \l{declarative/modelviews/pathview}{PathView}
+\li \l{declarative/modelviews/package}{Package}
+\li \l{declarative/modelviews/parallax}{Parallax}
+\li \l{declarative/modelviews/visualitemmodel}{VisualItemModel}
-\o \l{declarative/modelviews/stringlistmodel}{String ListModel}
-\o \l{declarative/modelviews/objectlistmodel}{Object ListModel}
-\o \l{declarative/modelviews/abstractitemmodel}{AbstractItemModel}
+\li \l{declarative/modelviews/stringlistmodel}{String ListModel}
+\li \l{declarative/modelviews/objectlistmodel}{Object ListModel}
+\li \l{declarative/modelviews/abstractitemmodel}{AbstractItemModel}
-\o \l{Models and Views: WebView Examples}{WebView}
+\li \l{Models and Views: WebView Examples}{WebView}
\endlist
\section2 XML
\list
-\o \l{declarative/xml/xmlhttprequest}{XmlHttpRequest}
+\li \l{declarative/xml/xmlhttprequest}{XmlHttpRequest}
\endlist
\section2 Internationalization (i18n)
\list
-\o \l{declarative/i18n}{Example}
+\li \l{declarative/i18n}{Example}
\endlist
\section2 Right-to-left User Interfaces
\list
-\o \l{declarative/righttoleft/layoutmirroring}{Layout mirroring}
-\o \l{declarative/righttoleft/layoutdirection}{Layout direction}
-\o \l{declarative/righttoleft/textalignment}{Text alignment}
+\li \l{declarative/righttoleft/layoutmirroring}{Layout mirroring}
+\li \l{declarative/righttoleft/layoutdirection}{Layout direction}
+\li \l{declarative/righttoleft/textalignment}{Text alignment}
\endlist
\section2 Threading
\list
-\o \l{declarative/threading/threadedlistmodel}{Threaded ListModel}
-\o \l{declarative/threading/workerscript}{WorkerScript}
+\li \l{declarative/threading/threadedlistmodel}{Threaded ListModel}
+\li \l{declarative/threading/workerscript}{WorkerScript}
\endlist
\section2 Screen Orientation
\list
-\o \l{declarative/screenorientation}{Example}
+\li \l{declarative/screenorientation}{Example}
\endlist
\section2 SQL Local Storage
\list
-\o \l{declarative/sqllocalstorage}{Example}
+\li \l{declarative/sqllocalstorage}{Example}
\endlist
\section2 C++ Extensions
\list
-\o \l{declarative-cppextensions-reference.html}{Reference examples}
-\o \l{declarative/cppextensions/plugins}{Plugins}
-\o \l{declarative-cppextensions-qgraphicslayouts.html}{QGraphicsLayouts}
-\o \l{declarative/cppextensions/qwidgets}{QWidgets}
-\o \l{declarative/cppextensions/imageprovider}{Image provider}
-\o \l{declarative/cppextensions/networkaccessmanagerfactory}{Network access manager factory}
+\li \l{declarative-cppextensions-reference.html}{Reference examples}
+\li \l{declarative/cppextensions/plugins}{Plugins}
+\li \l{declarative-cppextensions-qgraphicslayouts.html}{QGraphicsLayouts}
+\li \l{declarative/cppextensions/qwidgets}{QWidgets}
+\li \l{declarative/cppextensions/imageprovider}{Image provider}
+\li \l{declarative/cppextensions/networkaccessmanagerfactory}{Network access manager factory}
\endlist
\section1 Labs
\list
-\o \l{src/imports/folderlistmodel}{Folder List Model} - a C++ model plugin
-\o \l{declarative/shadereffects}{Shader Effects}
+\li \l{src/imports/folderlistmodel}{Folder List Model} - a C++ model plugin
+\li \l{declarative/shadereffects}{Shader Effects}
\endlist
*/
diff --git a/doc/src/declarative/extending-tutorial.qdoc b/doc/src/declarative/extending-tutorial.qdoc
index 8dac402e..568aecec 100644
--- a/doc/src/declarative/extending-tutorial.qdoc
+++ b/doc/src/declarative/extending-tutorial.qdoc
@@ -43,13 +43,13 @@ examples/declarative/tutorials/extending directory.
Tutorial chapters:
\list 1
-\o \l{declarative/tutorials/extending/chapter1-basics}{Creating a New Type}
-\o \l{declarative/tutorials/extending/chapter2-methods}{Connecting to C++ Methods and Signals}
-\o \l{declarative/tutorials/extending/chapter3-bindings}{Property Binding}
-\o \l{declarative/tutorials/extending/chapter4-customPropertyTypes}{Using Custom Property Types}
-\o \l{declarative/tutorials/extending/chapter5-listproperties}{Using List Property Types}
-\o \l{declarative/tutorials/extending/chapter6-plugins}{Writing an Extension Plugin}
-\o \l{qml-extending-tutorial7.html}{In Summary}
+\li \l{declarative/tutorials/extending/chapter1-basics}{Creating a New Type}
+\li \l{declarative/tutorials/extending/chapter2-methods}{Connecting to C++ Methods and Signals}
+\li \l{declarative/tutorials/extending/chapter3-bindings}{Property Binding}
+\li \l{declarative/tutorials/extending/chapter4-customPropertyTypes}{Using Custom Property Types}
+\li \l{declarative/tutorials/extending/chapter5-listproperties}{Using List Property Types}
+\li \l{declarative/tutorials/extending/chapter6-plugins}{Writing an Extension Plugin}
+\li \l{qml-extending-tutorial7.html}{In Summary}
\endlist
*/
@@ -91,8 +91,8 @@ properties. Since QML makes extensive use of Qt's \l{Meta-Object System}{meta ob
this new class must:
\list
-\o Inherit from QObject
-\o Declare its properties using the Q_PROPERTY macro
+\li Inherit from QObject
+\li Declare its properties using the Q_PROPERTY macro
\endlist
Here is our \c PieChart class, defined in \c piechart.h:
@@ -289,11 +289,11 @@ We can also use various other property types. QML has built-in support for the t
listed in the \l{QML Basic Types} documentation, which includes the following:
\list
-\o bool, unsigned int, int, float, double, qreal
-\o QString, QUrl, QColor
-\o QDate, QTime, QDateTime
-\o QPoint, QPointF, QSize, QSizeF, QRect, QRectF
-\o QVariant
+\li bool, unsigned int, int, float, double, qreal
+\li QString, QUrl, QColor
+\li QDate, QTime, QDateTime
+\li QPoint, QPointF, QSize, QSizeF, QRect, QRectF
+\li QVariant
\endlist
If we want to create a property whose type is not supported by QML by default,
@@ -408,9 +408,9 @@ loading our own C++ application.
To create a plugin library, we need:
\list
-\o A plugin class that registers our QML types
-\o A project file that describes the plugin
-\o A \l{Writing a qmldir file}{qmldir} file that tells the QML engine to load the plugin
+\li A plugin class that registers our QML types
+\li A project file that describes the plugin
+\li A \l{Writing a qmldir file}{qmldir} file that tells the QML engine to load the plugin
\endlist
First, we create a plugin class named \c ChartsPlugin. It subclasses QDeclarativeExtensionPlugin
@@ -459,12 +459,12 @@ be used by \c app.qml without import statements.
In this tutorial, we've shown the basic steps for creating a QML extension:
\list
-\o Define new QML types by subclassing QObject and registering them with qmlRegisterType()
-\o Add callable methods using Q_INVOKABLE or Qt slots, and connect to Qt signals with an \c onSignal syntax
-\o Add property bindings by defining \l{Qt's Property System}{NOTIFY} signals
-\o Define custom property types if the built-in types are not sufficient
-\o Define list property types using QDeclarativeListProperty
-\o Create a plugin library by defining a Qt plugin and writing a \c qmldir file
+\li Define new QML types by subclassing QObject and registering them with qmlRegisterType()
+\li Add callable methods using Q_INVOKABLE or Qt slots, and connect to Qt signals with an \c onSignal syntax
+\li Add property bindings by defining \l{Qt's Property System}{NOTIFY} signals
+\li Define custom property types if the built-in types are not sufficient
+\li Define list property types using QDeclarativeListProperty
+\li Create a plugin library by defining a Qt plugin and writing a \c qmldir file
\endlist
diff --git a/doc/src/declarative/extending.qdoc b/doc/src/declarative/extending.qdoc
index f1db3696..c188a92d 100644
--- a/doc/src/declarative/extending.qdoc
+++ b/doc/src/declarative/extending.qdoc
@@ -90,11 +90,11 @@ properties of the types listed in the \l{QML Basic Types}
document, which includes the following:
\list
-\o bool, unsigned int, int, float, double, qreal
-\o QString, QUrl, QColor
-\o QDate, QTime, QDateTime
-\o QPoint, QPointF, QSize, QSizeF, QRect, QRectF
-\o QVariant
+\li bool, unsigned int, int, float, double, qreal
+\li QString, QUrl, QColor
+\li QDate, QTime, QDateTime
+\li QPoint, QPointF, QSize, QSizeF, QRect, QRectF
+\li QVariant
\endlist
When a property of a supported type is added to a C++ class, in a QML
@@ -432,13 +432,13 @@ It is an element's responsibility to ensure that it does not access or return
pointers to invalid objects. QML makes the following guarentees:
\list
-\o An object assigned to a QObject (or QObject-derived) pointer property will be
+\li An object assigned to a QObject (or QObject-derived) pointer property will be
valid at the time of assignment.
Following assignment, it is the responsibility of the class to subsequently guard
this pointer, either through a class specific method or the generic QPointer class.
-\o An object assigned to a QVariant will be valid at the time of assignment.
+\li An object assigned to a QVariant will be valid at the time of assignment.
When assigning an object to a QVariant property, QML will always use a QMetaType::QObjectStar
typed QVariant. It is the responsibility of the class to guard the pointer. A
@@ -446,7 +446,7 @@ general rule when writing a class that uses QVariant properties is to check the
type of the QVariant when it is set and if the type is not handled by your class,
reset it to an invalid variant.
-\o An object assigned to a QObject (or QObject-derived) list property will be
+\li An object assigned to a QObject (or QObject-derived) list property will be
valid at the time of assignment.
Following assignment, it is the responsibility of the class to subsequently guard
diff --git a/doc/src/declarative/focus.qdoc b/doc/src/declarative/focus.qdoc
index 85900fe3..f8a9a089 100644
--- a/doc/src/declarative/focus.qdoc
+++ b/doc/src/declarative/focus.qdoc
@@ -46,13 +46,13 @@ and to address some of the cases unique to fluid user interfaces, the QML items
When the user presses or releases a key, the following occurs:
\list 1
-\o Qt receives the key action and generates a key event.
-\o If the Qt widget containing the \l QDeclarativeView has focus, the key event
+\li Qt receives the key action and generates a key event.
+\li If the Qt widget containing the \l QDeclarativeView has focus, the key event
is delivered to it. Otherwise, regular Qt key handling continues.
-\o The key event is delivered by the scene to the QML \l Item with
+\li The key event is delivered by the scene to the QML \l Item with
\e {active focus}. If no Item has active focus, the key event is
\l {QEvent::ignore()}{ignored} and regular Qt key handling continues.
-\o If the QML Item with active focus accepts the key event, propagation
+\li If the QML Item with active focus accepts the key event, propagation
stops. Otherwise the event is "bubbled up", by recursively passing it to each
Item's parent until either the event is accepted, or the root Item is reached.
@@ -63,7 +63,7 @@ item and thus subsequently be ignored.
\snippet doc/src/snippets/declarative/focus/rectangle.qml simple key event
\snippet doc/src/snippets/declarative/focus/rectangle.qml simple key event end
-\o If the root \l Item is reached, the key event is \l {QEvent::ignore()}{ignored} and regular Qt key handling continues.
+\li If the root \l Item is reached, the key event is \l {QEvent::ignore()}{ignored} and regular Qt key handling continues.
\endlist
@@ -137,11 +137,11 @@ visual result shown.
Conceptually \e {focus scopes} are quite simple.
\list
-\o Within each focus scope one element may have \c {Item::focus} set to
+\li Within each focus scope one element may have \c {Item::focus} set to
\c true. If more than one \l Item has the \c focus property set, the
last element to set the \c focus will have the focus and the others are unset,
similar to when there are no focus scopes.
-\o When a focus scope receives active focus, the contained element with
+\li When a focus scope receives active focus, the contained element with
\c focus set (if any) also gets the active focus. If this element is
also a \l FocusScope, the proxying behavior continues. Both the
focus scope and the sub-focused item will have \c activeFocus property set.
diff --git a/doc/src/declarative/globalobject.qdoc b/doc/src/declarative/globalobject.qdoc
index c59e2075..9a74519c 100644
--- a/doc/src/declarative/globalobject.qdoc
+++ b/doc/src/declarative/globalobject.qdoc
@@ -48,8 +48,8 @@ data from over a network.
The XMLHttpRequest API implements the same \l {http://www.w3.org/TR/XMLHttpRequest/}{W3C standard}
as many popular web browsers with following exceptions:
\list
-\i QML's XMLHttpRequest does not enforce the same origin policy.
-\i QML's XMLHttpRequest does not support \e synchronous requests.
+\li QML's XMLHttpRequest does not enforce the same origin policy.
+\li QML's XMLHttpRequest does not support \e synchronous requests.
\endlist
Additionally, the \c responseXML XML DOM tree currently supported by QML is a reduced subset
@@ -58,58 +58,58 @@ browser. The following objects and properties are supported by the QML implemen
\table
\header
-\o \bold {Node}
-\o \bold {Document}
-\o \bold {Element}
-\o \bold {Attr}
-\o \bold {CharacterData}
-\o \bold {Text}
+\li \b {Node}
+\li \b {Document}
+\li \b {Element}
+\li \b {Attr}
+\li \b {CharacterData}
+\li \b {Text}
\row
-\o
+\li
\list
-\o nodeName
-\o nodeValue
-\o nodeType
-\o parentNode
-\o childNodes
-\o firstChild
-\o lastChild
-\o previousSibling
-\o nextSibling
-\o attributes
+\li nodeName
+\li nodeValue
+\li nodeType
+\li parentNode
+\li childNodes
+\li firstChild
+\li lastChild
+\li previousSibling
+\li nextSibling
+\li attributes
\endlist
-\o
+\li
\list
-\o xmlVersion
-\o xmlEncoding
-\o xmlStandalone
-\o documentElement
+\li xmlVersion
+\li xmlEncoding
+\li xmlStandalone
+\li documentElement
\endlist
-\o
+\li
\list
-\o tagName
+\li tagName
\endlist
-\o
+\li
\list
-\o name
-\o value
-\o ownerElement
+\li name
+\li value
+\li ownerElement
\endlist
-\o
+\li
\list
-\o data
-\o length
+\li data
+\li length
\endlist
-\o
+\li
\list
-\o isElementContentWhitespace
-\o wholeText
+\li isElementContentWhitespace
+\li wholeText
\endlist
\endtable
@@ -150,12 +150,12 @@ May throw exception with code property SQLException.DATABASE_ERR, or SQLExceptio
When a database is first created, an INI file is also created specifying its characteristics:
\table
-\header \o \bold {Key} \o \bold {Value}
-\row \o Name \o The name of the database passed to \c openDatabase()
-\row \o Version \o The version of the database passed to \c openDatabase()
-\row \o Description \o The description of the database passed to \c openDatabase()
-\row \o EstimatedSize \o The estimated size (in bytes) of the database passed to \c openDatabase()
-\row \o Driver \o Currently "QSQLITE"
+\header \li \b {Key} \li \b {Value}
+\row \li Name \li The name of the database passed to \c openDatabase()
+\row \li Version \li The version of the database passed to \c openDatabase()
+\row \li Description \li The description of the database passed to \c openDatabase()
+\row \li EstimatedSize \li The estimated size (in bytes) of the database passed to \c openDatabase()
+\row \li Driver \li Currently "QSQLITE"
\endtable
This data can be used by application tools.
@@ -190,11 +190,11 @@ This method executes a SQL \e statement, binding the list of \e values to SQL po
It returns a results object, with the following properties:
\table
-\header \o \bold {Type} \o \bold {Property} \o \bold {Value} \o \bold {Applicability}
-\row \o int \o rows.length \o The number of rows in the result \o SELECT
-\row \o var \o rows.item(i) \o Function that returns row \e i of the result \o SELECT
-\row \o int \o rowsAffected \o The number of rows affected by a modification \o UPDATE, DELETE
-\row \o string \o insertId \o The id of the row inserted \o INSERT
+\header \li \b {Type} \li \b {Property} \li \b {Value} \li \b {Applicability}
+\row \li int \li rows.length \li The number of rows in the result \li SELECT
+\row \li var \li rows.item(i) \li Function that returns row \e i of the result \li SELECT
+\row \li int \li rowsAffected \li The number of rows affected by a modification \li UPDATE, DELETE
+\row \li string \li insertId \li The id of the row inserted \li INSERT
\endtable
May throw exception with code property SQLException.DATABASE_ERR, SQLException.SYNTAX_ERR, or SQLException.UNKNOWN_ERR.
diff --git a/doc/src/declarative/integrating.qdoc b/doc/src/declarative/integrating.qdoc
index 66854425..fb4a64fa 100644
--- a/doc/src/declarative/integrating.qdoc
+++ b/doc/src/declarative/integrating.qdoc
@@ -92,9 +92,9 @@ The following QGraphicsView options are recommended for optimal performance
of QML UIs:
\list
-\o QGraphicsView::setOptimizationFlags(QGraphicsView::DontSavePainterState)
-\o QGraphicsView::setViewportUpdateMode(QGraphicsView::BoundingRectViewportUpdate)
-\o QGraphicsScene::setItemIndexMethod(QGraphicsScene::NoIndex)
+\li QGraphicsView::setOptimizationFlags(QGraphicsView::DontSavePainterState)
+\li QGraphicsView::setViewportUpdateMode(QGraphicsView::BoundingRectViewportUpdate)
+\li QGraphicsScene::setItemIndexMethod(QGraphicsScene::NoIndex)
\endlist
\section2 Loading QGraphicsWidget objects in QML
diff --git a/doc/src/declarative/javascriptblocks.qdoc b/doc/src/declarative/javascriptblocks.qdoc
index 6a3b3f4b..9ffa2954 100644
--- a/doc/src/declarative/javascriptblocks.qdoc
+++ b/doc/src/declarative/javascriptblocks.qdoc
@@ -158,10 +158,10 @@ which in turn can call \c factorial() in \c factorial.js, as it has included
\table
\row
-\o {1,2} \snippet doc/src/snippets/declarative/integrating-javascript/includejs/app.qml 0
-\o \snippet doc/src/snippets/declarative/integrating-javascript/includejs/script.js 0
+\li {1,2} \snippet doc/src/snippets/declarative/integrating-javascript/includejs/app.qml 0
+\li \snippet doc/src/snippets/declarative/integrating-javascript/includejs/script.js 0
\row
-\o \snippet doc/src/snippets/declarative/integrating-javascript/includejs/factorial.js 0
+\li \snippet doc/src/snippets/declarative/integrating-javascript/includejs/factorial.js 0
\endtable
Notice that calling \l {QML:Qt::include()}{Qt.include()} imports all functions from
@@ -218,8 +218,8 @@ in \c script.js:
\table
\row
-\o \snippet doc/src/snippets/declarative/integrating-javascript/connectjs.qml 0
-\o \snippet doc/src/snippets/declarative/integrating-javascript/script.js 0
+\li \snippet doc/src/snippets/declarative/integrating-javascript/connectjs.qml 0
+\li \snippet doc/src/snippets/declarative/integrating-javascript/script.js 0
\endtable
The \c jsFunction() will now be called whenever MouseArea's \c clicked signal is emitted.
@@ -233,7 +233,7 @@ See \l{QML Signal and Handler Event System#Connecting Signals to Methods and Sig
QML executes standard JavaScript code, with the following restrictions:
\list
-\o JavaScript code cannot modify the global object.
+\li JavaScript code cannot modify the global object.
In QML, the global object is constant - existing properties cannot be modified or
deleted, and no new properties may be created.
@@ -266,7 +266,7 @@ Any attempt to modify the global object - either implicitly or explicitly - will
cause an exception. If uncaught, this will result in an warning being printed,
that includes the file and line number of the offending code.
-\o Global code is run in a reduced scope
+\li Global code is run in a reduced scope
During startup, if a QML file includes an external JavaScript file with "global"
code, it is executed in a scope that contains only the external file itself and
@@ -291,7 +291,7 @@ This restriction exists as the QML environment is not yet fully established.
To run code after the environment setup has completed, refer to
\l {Running JavaScript at Startup}.
-\o The value of \c this is currently undefined in QML in the majority of contexts
+\li The value of \c this is currently undefined in QML in the majority of contexts
The \c this keyword is supported when binding properties from JavaScript.
In all other situations, the value of
diff --git a/doc/src/declarative/modules.qdoc b/doc/src/declarative/modules.qdoc
index 7ff3a022..92d5e6d3 100644
--- a/doc/src/declarative/modules.qdoc
+++ b/doc/src/declarative/modules.qdoc
@@ -42,10 +42,10 @@ explicitly using the \c import statement to import them as modules. For
example, an \c import statement is required to use:
\list
-\o A component defined in another QML file that is not in the same directory
-\o A component defined in a QML file located on a remote server
-\o A \l{QDeclarativeExtensionPlugin}{QML extension plugin} library (unless the plugin is installed in the same directory)
-\o A JavaScript file (note this must be imported using \l {#namespaces}{named imports})
+\li A component defined in another QML file that is not in the same directory
+\li A component defined in a QML file located on a remote server
+\li A \l{QDeclarativeExtensionPlugin}{QML extension plugin} library (unless the plugin is installed in the same directory)
+\li A JavaScript file (note this must be imported using \l {#namespaces}{named imports})
\endlist
An \c import statement includes the module name, and possibly a version number.
@@ -76,11 +76,11 @@ directory using a relative or absolute path, like this:
\table
\row
-\o Directory structure
-\o Contents of application.qml
+\li Directory structure
+\li Contents of application.qml
\row
-\o
+\li
\code
MyQMLProject
|- MyComponents
@@ -91,7 +91,7 @@ MyQMLProject
|- application.qml
\endcode
-\o
+\li
\qml
import "../MyComponents"
@@ -181,9 +181,9 @@ locations to be searched by the QML engine for a matching module. By default, th
contains:
\list
-\o The directory of the current file
-\o The location specified by QLibraryInfo::ImportsPath
-\o Paths specified by the \c QML_IMPORT_PATH environment variable
+\li The directory of the current file
+\li The location specified by QLibraryInfo::ImportsPath
+\li Paths specified by the \c QML_IMPORT_PATH environment variable
\endlist
Additional import paths can be added through QDeclarativeEngine::addImportPath() or the
@@ -313,9 +313,9 @@ plugin <Name> [<Path>]
typeinfo <File>
\endcode
-\bold {# <Comment>} lines are used for comments. They are ignored by the QML engine.
+\b {# <Comment>} lines are used for comments. They are ignored by the QML engine.
-\bold {<TypeName> [<InitialVersion>] <File>} lines are used to add QML files as types.
+\b {<TypeName> [<InitialVersion>] <File>} lines are used to add QML files as types.
<TypeName> is the type being made available, the optional <InitialVersion> is a version
number, and <File> is the (relative) file name of the QML file defining the type.
@@ -323,7 +323,7 @@ Installed files do not need to import the module of which they are a part, as th
to the other QML files in the module as relative (local) files, but
if the module is imported from a remote location, those files must nevertheless be listed in
the \c qmldir file. Types which you do not wish to export to users of your module
-may be marked with the \c internal keyword: \bold {internal <TypeName> <File>}.
+may be marked with the \c internal keyword: \b {internal <TypeName> <File>}.
The same type can be provided by different files in different versions, in which
case later versions (e.g. 1.2) must precede earlier versions (e.g. 1.0),
@@ -342,7 +342,7 @@ of installed software, since a versioned import \e only imports types for that v
leaving other identifiers available, even if the actual installed version might otherwise
provide those identifiers.
-\bold {plugin <Name> [<Path>]} lines are used to add \l{QDeclarativeExtensionPlugin}{QML C++ plugins} to the module. <Name> is the name of the library. It is usually not the same as the file name
+\b {plugin <Name> [<Path>]} lines are used to add \l{QDeclarativeExtensionPlugin}{QML C++ plugins} to the module. <Name> is the name of the library. It is usually not the same as the file name
of the plugin binary, which is platform dependent; e.g. the library \c MyAppTypes would produce
\c libMyAppTypes.so on Linux and \c MyAppTypes.dll on Windows.
@@ -351,7 +351,7 @@ plugin file, or a relative path from the directory containing the \c qmldir file
containing the plugin file. By default the engine searches for the plugin library in the directory that contains the \c qmldir
file. The plugin search path can be queried with QDeclarativeEngine::pluginPathList() and modified using QDeclarativeEngine::addPluginPath(). When running the \l {QML Viewer}, use the \c -P option to add paths to the plugin search path.
-\bold {typeinfo <File>} lines add \l{Writing a qmltypes file}{type description files} to
+\b {typeinfo <File>} lines add \l{Writing a qmltypes file}{type description files} to
the module that can be read by QML tools such as Qt Creator to get information about the
types defined by the module's plugins. <File> is the (relative) file name of a .qmltypes
file.
@@ -396,9 +396,9 @@ to \c /tmp/imports/My/Module/qmldir to register it.
While the qmldump tool covers most cases, it does not work if:
\list
-\o The plugin uses a \l{QDeclarativeCustomParser}. The component that uses
+\li The plugin uses a \l{QDeclarativeCustomParser}. The component that uses
the custom parser will not get its members documented.
-\o The plugin can not be loaded. In particular if you cross-compiled
+\li The plugin can not be loaded. In particular if you cross-compiled
the plugin for a different architecture, qmldump will not be able to
load it.
\endlist
diff --git a/doc/src/declarative/mouseevents.qdoc b/doc/src/declarative/mouseevents.qdoc
index c267855d..50b321cd 100644
--- a/doc/src/declarative/mouseevents.qdoc
+++ b/doc/src/declarative/mouseevents.qdoc
@@ -38,8 +38,8 @@
\section1 Mouse Elements
\list
-\o \l{MouseArea} Element
-\o \l{MouseEvent} Object
+\li \l{MouseArea} Element
+\li \l{MouseEvent} Object
\endlist
\section1 Mouse Event Handling
@@ -67,15 +67,15 @@ mouse events. The \l MouseArea element documentation describes these
gestures in greater detail:
\list
-\o canceled
-\o clicked
-\o doubleClicked
-\o entered
-\o exited
-\o positionChanged
-\o pressAndHold
-\o pressed
-\o released
+\li canceled
+\li clicked
+\li doubleClicked
+\li entered
+\li exited
+\li positionChanged
+\li pressAndHold
+\li pressed
+\li released
\endlist
These signals have signal handlers that are invoked when the signals are emitted.
diff --git a/doc/src/declarative/network.qdoc b/doc/src/declarative/network.qdoc
index f8a7666d..0ccb3a80 100644
--- a/doc/src/declarative/network.qdoc
+++ b/doc/src/declarative/network.qdoc
@@ -54,8 +54,8 @@ Image {
Network transparency is supported throughout QML, for example:
\list
-\o Fonts - the \c source property of FontLoader is a URL
-\o WebViews - the \c url property of WebView (obviously!)
+\li Fonts - the \c source property of FontLoader is a URL
+\li WebViews - the \c url property of WebView (obviously!)
\endlist
Even QML types themselves can be on the network - if the \l {QML Viewer} is used to load
@@ -148,10 +148,10 @@ The \c import statement is only network transparent if it has an "as" clause.
More specifically:
\list
-\o \c{import "dir"} only works on local file systems
-\o \c{import libraryUri} only works on local file systems
-\o \c{import "dir" as D} works network transparently
-\o \c{import libraryUrl as U} works network transparently
+\li \c{import "dir"} only works on local file systems
+\li \c{import libraryUri} only works on local file systems
+\li \c{import "dir" as D} works network transparently
+\li \c{import libraryUrl as U} works network transparently
\endlist
diff --git a/doc/src/declarative/positioners.qdoc b/doc/src/declarative/positioners.qdoc
index e9b60a3f..199f32f0 100644
--- a/doc/src/declarative/positioners.qdoc
+++ b/doc/src/declarative/positioners.qdoc
@@ -48,10 +48,10 @@ A set of standard positioners are provided in the basic set of Qt Quick
graphical elements:
\list
-\o \l{#Column}{Column} arranges its children in a column
-\o \l{#Row}{Row} arranges its children in a row
-\o \l{#Grid}{Grid} arranges its children in a grid
-\o \l{#Flow}{Flow} arranges its children like words on a page
+\li \l{#Column}{Column} arranges its children in a column
+\li \l{#Row}{Row} arranges its children in a row
+\li \l{#Grid}{Grid} arranges its children in a grid
+\li \l{#Flow}{Flow} arranges its children like words on a page
\endlist
\section2 Column
diff --git a/doc/src/declarative/qdeclarativedocument.qdoc b/doc/src/declarative/qdeclarativedocument.qdoc
index 8cd400ae..993fed7a 100644
--- a/doc/src/declarative/qdeclarativedocument.qdoc
+++ b/doc/src/declarative/qdeclarativedocument.qdoc
@@ -73,12 +73,12 @@ Each instance is created with a different value for its \c text property:
\table
\row
-\o Button.qml
-\o application.qml
+\li Button.qml
+\li application.qml
\row
-\o \snippet doc/src/snippets/declarative/qml-documents/qmldocuments.qml document
-\o
+\li \snippet doc/src/snippets/declarative/qml-documents/qmldocuments.qml document
+\li
\qml
import QtQuick 1.0
@@ -97,7 +97,7 @@ Column {
\endtable
Any snippet of QML code can become a component, just by placing it in the file "<Name>.qml"
-where <Name> is the new element name, and begins with an \bold uppercase letter. Note that
+where <Name> is the new element name, and begins with an \b uppercase letter. Note that
the case of all characters in the <Name> are significant on some filesystems, notably
UNIX filesystems. It is recommended that the case of the filename matches the case of
the component name in QML exactly, regardless of the platform the QML will be deployed to.
@@ -133,9 +133,9 @@ These final two examples are behaviorally identical to the original document.
\table
\row
-\o
+\li
\snippet doc/src/snippets/declarative/qml-documents/inline-component.qml document
-\o
+\li
\snippet doc/src/snippets/declarative/qml-documents/inline-text-component.qml document
\endtable
diff --git a/doc/src/declarative/qdeclarativei18n.qdoc b/doc/src/declarative/qdeclarativei18n.qdoc
index f53502fe..b98cfccc 100644
--- a/doc/src/declarative/qdeclarativei18n.qdoc
+++ b/doc/src/declarative/qdeclarativei18n.qdoc
@@ -48,8 +48,8 @@ QScriptEngine::installTranslatorFunctions().
QML relies on the core internationalization capabilities provided by Qt. These
capabilities are described more fully in:
\list
-\o \l {Internationalization with Qt}
-\o \l {Qt Linguist Manual}
+\li \l {Internationalization with Qt}
+\li \l {Qt Linguist Manual}
\endlist
You can test a translation with the \l {QML Viewer} using the -translation option.
diff --git a/doc/src/declarative/qdeclarativeintro.qdoc b/doc/src/declarative/qdeclarativeintro.qdoc
index 3908c79f..6b41088c 100644
--- a/doc/src/declarative/qdeclarativeintro.qdoc
+++ b/doc/src/declarative/qdeclarativeintro.qdoc
@@ -96,8 +96,8 @@ and \l Image elements would not be available.
Commenting in QML is similar to JavaScript.
\list
-\o Single line comments start with // and finish at the end of the line.
-\o Multiline comments start with /* and finish with *\/
+\li Single line comments start with // and finish at the end of the line.
+\li Multiline comments start with /* and finish with *\/
\endlist
\snippet doc/src/snippets/declarative/comments.qml 0
diff --git a/doc/src/declarative/qdeclarativemodels.qdoc b/doc/src/declarative/qdeclarativemodels.qdoc
index ac184696..ce495a4d 100644
--- a/doc/src/declarative/qdeclarativemodels.qdoc
+++ b/doc/src/declarative/qdeclarativemodels.qdoc
@@ -223,14 +223,14 @@ QAbstractItemModel::setRoleNames(). The default role names set by Qt are:
\table
\header
-\o Qt Role
-\o QML Role Name
+\li Qt Role
+\li QML Role Name
\row
-\o Qt::DisplayRole
-\o display
+\li Qt::DisplayRole
+\li display
\row
-\o Qt::DecorationRole
-\o decoration
+\li Qt::DecorationRole
+\li decoration
\endtable
Here is an application with a QAbstractListModel subclass named \c AnimalModel
@@ -268,10 +268,10 @@ the VisualDataModel element provides several properties and functions for use
with models of type QAbstractItemModel:
\list
-\o \e hasModelChildren role property to determine whether a node has child nodes.
-\o \l VisualDataModel::rootIndex allows the root node to be specifed
-\o \l VisualDataModel::modelIndex() returns a QModelIndex which can be assigned to VisualDataModel::rootIndex
-\o \l VisualDataModel::parentModelIndex() returns a QModelIndex which can be assigned to VisualDataModel::rootIndex
+\li \e hasModelChildren role property to determine whether a node has child nodes.
+\li \l VisualDataModel::rootIndex allows the root node to be specifed
+\li \l VisualDataModel::modelIndex() returns a QModelIndex which can be assigned to VisualDataModel::rootIndex
+\li \l VisualDataModel::parentModelIndex() returns a QModelIndex which can be assigned to VisualDataModel::rootIndex
\endlist
@@ -286,7 +286,7 @@ created directly as elements within QML:
\table
\row
-\o
+\li
\code
class MyModelPlugin : public QDeclarativeExtensionPlugin
{
@@ -301,7 +301,7 @@ public:
Q_EXPORT_PLUGIN2(mymodelplugin, MyModelPlugin);
\endcode
-\o
+\li
\qml
MyModel {
id: myModel
@@ -449,9 +449,9 @@ A set of standard views are provided in the basic set of Qt Quick
graphical elements:
\list
-\o \l{#ListView}{ListView} arranges items in a horizontal or vertical list
-\o \l{#GridView}{GridView} arranges items in a grid within the available space
-\o \l{#PathView}{PathView} arranges items on a path
+\li \l{#ListView}{ListView} arranges items in a horizontal or vertical list
+\li \l{#GridView}{GridView} arranges items in a grid within the available space
+\li \l{#PathView}{PathView} arranges items on a path
\endlist
Unlike these items, \l WebView is not a fully-featured view item, and needs
diff --git a/doc/src/declarative/qdeclarativeperformance.qdoc b/doc/src/declarative/qdeclarativeperformance.qdoc
index 33229740..2fc8b2da 100644
--- a/doc/src/declarative/qdeclarativeperformance.qdoc
+++ b/doc/src/declarative/qdeclarativeperformance.qdoc
@@ -96,11 +96,11 @@ Delegates must be created quickly as the view is flicked. There are two importa
aspects to maintaining a smooth view:
\list
-\o Small delegates - keep the amount of QML to a minimum. Have just enough
+\li Small delegates - keep the amount of QML to a minimum. Have just enough
QML in the delegate to display the necessary information. Any additional functionality
that is only needed when the delegate is clicked, for example, should be created by
a Loader as needed.
-\o Fast data access - ensure the data model is as fast as possible.
+\li Fast data access - ensure the data model is as fast as possible.
\endlist
\section1 Image resources over composition
@@ -127,8 +127,8 @@ QGLWidget as the viewport of your QDeclarativeView.
You may need to try various options to find what works the best for your application.
For embedded X11-based devices one recommended combination is to use the raster graphics
-system with a QGLWidget for the viewport. While this doesn't guarantee the \bold fastest
-performance for all use-cases, it typically has \bold{consistently good} performance for
+system with a QGLWidget for the viewport. While this doesn't guarantee the \b fastest
+performance for all use-cases, it typically has \b{consistently good} performance for
all use-cases. In contrast, only using the raster paint engine may result in very good
performance for parts of your application and very poor performance elsewhere.
diff --git a/doc/src/declarative/qdeclarativesecurity.qdoc b/doc/src/declarative/qdeclarativesecurity.qdoc
index f6246f21..468d627f 100644
--- a/doc/src/declarative/qdeclarativesecurity.qdoc
+++ b/doc/src/declarative/qdeclarativesecurity.qdoc
@@ -60,18 +60,18 @@ perform appropriate checks on untrusted data it loads.
A non-exhaustive list of the ways you could shoot yourself in the foot is:
\list
- \i Using \c import to import QML or JavaScript you do not control. BAD
- \i Using \l Loader to import QML you do not control. BAD
- \i Using \l{XMLHttpRequest}{XMLHttpRequest} to load data you do not control and executing it. BAD
+ \li Using \c import to import QML or JavaScript you do not control. BAD
+ \li Using \l Loader to import QML you do not control. BAD
+ \li Using \l{XMLHttpRequest}{XMLHttpRequest} to load data you do not control and executing it. BAD
\endlist
However, the above does not mean that you have no use for the network transparency of QML.
There are many good and useful things you \e can do:
\list
- \i Create \l Image elements with source URLs of any online images. GOOD
- \i Use XmlListModel to present online content. GOOD
- \i Use \l{XMLHttpRequest}{XMLHttpRequest} to interact with online services. GOOD
+ \li Create \l Image elements with source URLs of any online images. GOOD
+ \li Use XmlListModel to present online content. GOOD
+ \li Use \l{XMLHttpRequest}{XMLHttpRequest} to interact with online services. GOOD
\endlist
The only reason this page is necessary at all is that JavaScript, when run in a \e{web browser},
diff --git a/doc/src/declarative/qdeclarativestates.qdoc b/doc/src/declarative/qdeclarativestates.qdoc
index a4204c5d..ee5e3876 100644
--- a/doc/src/declarative/qdeclarativestates.qdoc
+++ b/doc/src/declarative/qdeclarativestates.qdoc
@@ -36,12 +36,12 @@
\section1 States Elements
\list
-\o \l State
-\o \l PropertyChanges
-\o \l StateGroup
-\o \l StateChangeScript
-\o \l ParentChange
-\o \l AnchorChanges
+\li \l State
+\li \l PropertyChanges
+\li \l StateGroup
+\li \l StateChangeScript
+\li \l ParentChange
+\li \l AnchorChanges
\endlist
Many user interface designs are \e state driven; interfaces have configurations
@@ -55,12 +55,12 @@ In QML, \e states are a set of property configurations defined in a \l State
element. Different configurations could, for example:
\list
-\o Show some UI elements and hide others
-\o Present different available actions to the user
-\o Start, stop, or pause animations
-\o Execute some script required in the new state
-\o Change a property value for a particular item
-\o Show a different view or screen
+\li Show some UI elements and hide others
+\li Present different available actions to the user
+\li Start, stop, or pause animations
+\li Execute some script required in the new state
+\li Change a property value for a particular item
+\li Show a different view or screen
\endlist
All \l {Item}-based objects have a \c state property, and can specify additional
@@ -96,10 +96,10 @@ assigning a different state whenever the signal receives a mouse click.
The State element is not limited to performing modifications on property values.
It can also:
\list
-\o Run some script using \l StateChangeScript
-\o Override an existing signal handler for an object using \l PropertyChanges
-\o Re-parent an \l Item using \l ParentChange
-\o Modify anchor values using \l AnchorChanges
+\li Run some script using \l StateChangeScript
+\li Override an existing signal handler for an object using \l PropertyChanges
+\li Re-parent an \l Item using \l ParentChange
+\li Modify anchor values using \l AnchorChanges
\endlist
\section1 The Default State
@@ -143,13 +143,13 @@ for the engine to fast forward and rewind a state (that is, internally set and u
before it is finally applied. The process is as follows:
\list 1
-\o The state is fast forwarded to determine the complete set of end values.
-\o The state is rewound.
-\o The state is fully applied, with transitions.
+\li The state is fast forwarded to determine the complete set of end values.
+\li The state is rewound.
+\li The state is fully applied, with transitions.
\endlist
In some cases this may cause unintended behavior. For example, a state that changes
-a view's \i model or a Loader's \i sourceComponent will set these properties
+a view's \e model or a Loader's \e sourceComponent will set these properties
multiple times (to apply, rewind, and then reapply), which can be relatively expensive.
State fast forwarding should be considered an implementation detail,
diff --git a/doc/src/declarative/qmlruntime.qdoc b/doc/src/declarative/qmlruntime.qdoc
index 2215a0bf..b9d0ae34 100644
--- a/doc/src/declarative/qmlruntime.qdoc
+++ b/doc/src/declarative/qmlruntime.qdoc
@@ -49,8 +49,8 @@ the application. This is done by writing a Qt C++ application that loads the
QDeclarativeEngine by either:
\list
-\o Loading the QML file through a QDeclarativeView instance, or
-\o Creating a QDeclarativeEngine instance and loading QML files with QDeclarativeComponent
+\li Loading the QML file through a QDeclarativeView instance, or
+\li Creating a QDeclarativeEngine instance and loading QML files with QDeclarativeComponent
\endlist
diff --git a/doc/src/declarative/qmlsyntax.qdoc b/doc/src/declarative/qmlsyntax.qdoc
index 24ac1da6..8914e1c1 100644
--- a/doc/src/declarative/qmlsyntax.qdoc
+++ b/doc/src/declarative/qmlsyntax.qdoc
@@ -129,8 +129,8 @@ information on the \e id property.)
Commenting in QML is similar to JavaScript.
\list
-\o Single line comments start with // and finish at the end of the line.
-\o Multiline comments start with /* and finish with *\/
+\li Single line comments start with // and finish at the end of the line.
+\li Multiline comments start with /* and finish with *\/
\endlist
\snippet doc/src/snippets/declarative/comments.qml 0
diff --git a/doc/src/declarative/qmltexthandling.qdoc b/doc/src/declarative/qmltexthandling.qdoc
index d0df2641..8e805eb3 100644
--- a/doc/src/declarative/qmltexthandling.qdoc
+++ b/doc/src/declarative/qmltexthandling.qdoc
@@ -38,16 +38,16 @@
\section1 Text Elements
\list
-\o \l{Text}
-\o \l{TextInput}
-\o \l{TextEdit}
+\li \l{Text}
+\li \l{TextInput}
+\li \l{TextEdit}
\endlist
\section1 Validators
\list
-\o \l{IntValidator}
-\o \l{DoubleValidator}
-\o \l{RegExpValidator}
+\li \l{IntValidator}
+\li \l{DoubleValidator}
+\li \l{RegExpValidator}
\endlist
\section1 Displaying Text in QML
diff --git a/doc/src/declarative/qmlviewer.qdoc b/doc/src/declarative/qmlviewer.qdoc
index 10cd6edd..3a767711 100644
--- a/doc/src/declarative/qmlviewer.qdoc
+++ b/doc/src/declarative/qmlviewer.qdoc
@@ -171,9 +171,9 @@ information about the application's runtime environment through the following pr
\table
\row
-\o \c runtime.isActiveWindow
+\li \c runtime.isActiveWindow
-\o This property indicates whether the QML Viewer window is the current active
+\li This property indicates whether the QML Viewer window is the current active
window on the system. It is useful for "pausing" an application, particularly
animations, when the QML Viewer loses focus or moves to the background.
@@ -197,19 +197,19 @@ through the \c active property of the \l {QML:Qt::application}{Qt.application} o
\row
-\o \c runtime.orientation
+\li \c runtime.orientation
-\o This property indicates the current orientation of the QML Viewer. On the
+\li This property indicates the current orientation of the QML Viewer. On the
N900 platform and most S60 5.0-based or newer Symbian devices, this property
automatically updates to reflect the device's actual orientation; on other platforms,
this indicates the orientation currently selected in the QML Viewer's
\e {Settings -> Properties} menu. The \c orientation value can be one of the following:
\list
-\o \c Orientation.Portrait
-\o \c Orientation.Landscape
-\o \c Orientation.PortraitInverted (Portrait orientation, upside-down)
-\o \c Orientation.LandscapeInverted (Landscape orientation, upside-down)
+\li \c Orientation.Portrait
+\li \c Orientation.Landscape
+\li \c Orientation.PortraitInverted (Portrait orientation, upside-down)
+\li \c Orientation.LandscapeInverted (Landscape orientation, upside-down)
\endlist
When the viewer's orientation changes, the appearance of the loaded QML document
diff --git a/doc/src/declarative/qmlviews.qdoc b/doc/src/declarative/qmlviews.qdoc
index 2ab957ec..145bc6c3 100644
--- a/doc/src/declarative/qmlviews.qdoc
+++ b/doc/src/declarative/qmlviews.qdoc
@@ -41,10 +41,10 @@ A set of standard views are provided in the basic set of Qt Quick
graphical elements:
\list
-\o \l{ListView} arranges items in a horizontal or vertical list
-\o \l{GridView} arranges items in a grid within the available space
-\o \l{PathView} arranges items on a path
-\o \l{WebView}{WebView} - available from the \l {QtWebKit QML Module}.
+\li \l{ListView} arranges items in a horizontal or vertical list
+\li \l{GridView} arranges items in a grid within the available space
+\li \l{PathView} arranges items on a path
+\li \l{WebView}{WebView} - available from the \l {QtWebKit QML Module}.
\endlist
Unlike other views, \l WebView is not a fully-featured view item, and needs
to be combined with a \l Flickable item to create a view that performs like
diff --git a/doc/src/declarative/qmlwebkit.qdoc b/doc/src/declarative/qmlwebkit.qdoc
index 776d4b5e..6b726ae6 100644
--- a/doc/src/declarative/qmlwebkit.qdoc
+++ b/doc/src/declarative/qmlwebkit.qdoc
@@ -34,7 +34,7 @@ Qt WebKit QML
\section1 WebKit QML Elements
\list
-\o \l WebView
+\li \l WebView
\endlist
\section1 QtWebKit Module
diff --git a/doc/src/declarative/qtbinding.qdoc b/doc/src/declarative/qtbinding.qdoc
index b22e40c5..07b5d929 100644
--- a/doc/src/declarative/qtbinding.qdoc
+++ b/doc/src/declarative/qtbinding.qdoc
@@ -42,11 +42,11 @@ reusable QML components for distribution.
You may want to mix QML and C++ for a number of reasons. For example:
\list
-\o To use functionality defined in a C++ source (for example, when using a C++ Qt-based data model, or
+\li To use functionality defined in a C++ source (for example, when using a C++ Qt-based data model, or
calling functions in a third-party C++ library)
-\o To access functionality in the Qt Declarative module (for example, to dynamically generate
+\li To access functionality in the Qt Declarative module (for example, to dynamically generate
images using QDeclarativeImageProvider)
-\o To write your own QML elements (whether for your applications, or for distribution to others)
+\li To write your own QML elements (whether for your applications, or for distribution to others)
\endlist
To use the Qt Declarative module, you must include and link to the module appropriately, as shown on
@@ -61,10 +61,10 @@ embedding QML into C++ applications. There are several core classes in the Qt De
that provide the essential capabilities for doing this. These are:
\list
-\o QDeclarativeEngine: A QML engine provides the environment for executing QML code. Every
+\li QDeclarativeEngine: A QML engine provides the environment for executing QML code. Every
application requires at least one engine instance.
-\o QDeclarativeComponent: A component encapsulates a \l{QML Documents}{QML document}.
-\o QDeclarativeContext: A context allows an application to expose data to the QML components
+\li QDeclarativeComponent: A component encapsulates a \l{QML Documents}{QML document}.
+\li QDeclarativeContext: A context allows an application to expose data to the QML components
created by an engine.
\endlist
@@ -97,10 +97,10 @@ UI code}.)
There are a number of ways to extend your QML application through C++. For example, you could:
\list
-\o Load a QML component and manipulate it (or its children) from C++
-\o Embed a C++ object and its properties directly into a QML component (for example, to make a
+\li Load a QML component and manipulate it (or its children) from C++
+\li Embed a C++ object and its properties directly into a QML component (for example, to make a
particular C++ object callable from QML, or to replace a dummy list model with a real data set)
-\o Define new QML elements (through QObject-based C++ classes) and create them directly from your
+\li Define new QML elements (through QObject-based C++ classes) and create them directly from your
QML code
\endlist
@@ -127,11 +127,11 @@ component, which is accessible via QDeclarativeView::rootObject():
\table
\row
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/loading/main.cpp QDeclarativeComponent-a
\dots 0
\snippet doc/src/snippets/declarative/qtbinding/loading/main.cpp QDeclarativeComponent-b
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/loading/main.cpp QDeclarativeView
\endtable
@@ -203,11 +203,11 @@ invokes a method on the object instance:
\table
\row
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/context-advanced/applicationdata.h 0
\codeline
\snippet doc/src/snippets/declarative/qtbinding/context-advanced/main.cpp 0
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/context-advanced/MyItem.qml 0
\endtable
@@ -288,8 +288,8 @@ QMetaObject::invokeMethod(). Here is a C++ application that uses this to call a
\table
\row
-\o \snippet doc/src/snippets/declarative/qtbinding/functions-qml/MyItem.qml 0
-\o \snippet doc/src/snippets/declarative/qtbinding/functions-qml/main.cpp 0
+\li \snippet doc/src/snippets/declarative/qtbinding/functions-qml/MyItem.qml 0
+\li \snippet doc/src/snippets/declarative/qtbinding/functions-qml/main.cpp 0
\endtable
Notice the Q_RETURN_ARG() and Q_ARG() arguments for QMetaObject::invokeMethod() must be specified as
@@ -301,9 +301,9 @@ methods on the \c myObject object, which has been set using QDeclarativeContext:
\table
\row
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/functions-cpp/MyItem.qml 0
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/functions-cpp/myclass.h 0
\codeline
\snippet doc/src/snippets/declarative/qtbinding/functions-cpp/main.cpp 0
@@ -326,9 +326,9 @@ is emitted:
\table
\row
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/signals-qml/MyItem.qml 0
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/signals-qml/myclass.h 0
\codeline
\snippet doc/src/snippets/declarative/qtbinding/signals-qml/main.cpp 0
@@ -342,13 +342,13 @@ C++ object are connected to through \c onImagedChanged and \c onLoadingError sig
\table
\row
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/signals-cpp/imageviewer.h start
\dots 4
\snippet doc/src/snippets/declarative/qtbinding/signals-cpp/imageviewer.h end
-\o
+\li
\snippet doc/src/snippets/declarative/qtbinding/signals-cpp/standalone.qml 0
\endtable
@@ -364,8 +364,8 @@ instead to create the signal handler:
\table
\row
-\o \snippet doc/src/snippets/declarative/qtbinding/signals-cpp/main.cpp connections
-\o \snippet doc/src/snippets/declarative/qtbinding/signals-cpp/MyItem.qml 0
+\li \snippet doc/src/snippets/declarative/qtbinding/signals-cpp/main.cpp connections
+\li \snippet doc/src/snippets/declarative/qtbinding/signals-cpp/MyItem.qml 0
\endtable
C++ signals can use enum values as parameters provided that the enum is declared in the
@@ -412,8 +412,8 @@ property. This property can be written to and read from QML:
\table
\row
-\o \snippet doc/src/snippets/declarative/qtbinding/properties-cpp/applicationdata.h 0
-\o \snippet doc/src/snippets/declarative/qtbinding/properties-cpp/MyItem.qml 0
+\li \snippet doc/src/snippets/declarative/qtbinding/properties-cpp/applicationdata.h 0
+\li \snippet doc/src/snippets/declarative/qtbinding/properties-cpp/MyItem.qml 0
\endtable
Notice the \c backgroundColorChanged signal is declared as the NOTIFY signal for the
@@ -434,20 +434,20 @@ functions - must be of a type that is recognizable by QML.
By default, QML recognizes the following data types:
\list
-\o bool
-\o unsigned int, int
-\o float, double, qreal
-\o QString
-\o QUrl
-\o QColor
-\o QDate, QTime, QDateTime
-\o QPoint, QPointF
-\o QSize, QSizeF
-\o QRect, QRectF
-\o QVariant
-\o QVariantList, QVariantMap
-\o QObject*
-\o Enumerations declared with Q_ENUMS()
+\li bool
+\li unsigned int, int
+\li float, double, qreal
+\li QString
+\li QUrl
+\li QColor
+\li QDate, QTime, QDateTime
+\li QPoint, QPointF
+\li QSize, QSizeF
+\li QRect, QRectF
+\li QVariant
+\li QVariantList, QVariantMap
+\li QObject*
+\li Enumerations declared with Q_ENUMS()
\endlist
To allow a custom C++ type to be created or used in QML, the C++ class must be registered as a QML
@@ -466,12 +466,12 @@ converted to JavaScript array and object values, repectively:
\table
\header
-\o Type
-\o String format
-\o Example
+\li Type
+\li String format
+\li Example
\row
-\o \snippet doc/src/snippets/declarative/qtbinding/variantlistmap/MyItem.qml 0
-\o \snippet doc/src/snippets/declarative/qtbinding/variantlistmap/main.cpp 0
+\li \snippet doc/src/snippets/declarative/qtbinding/variantlistmap/MyItem.qml 0
+\li \snippet doc/src/snippets/declarative/qtbinding/variantlistmap/main.cpp 0
\endtable
This produces output like:
@@ -537,45 +537,45 @@ pass simple values from QML to C++.
\table
\header
-\o Type
-\o String format
-\o Example
+\li Type
+\li String format
+\li Example
\row
-\o QColor
-\o Color name, "#RRGGBB", "#RRGGBBAA"
-\o "red", "#ff0000", "#ff000000"
+\li QColor
+\li Color name, "#RRGGBB", "#RRGGBBAA"
+\li "red", "#ff0000", "#ff000000"
\row
-\o QDate
-\o "YYYY-MM-DD"
-\o "2010-05-31"
+\li QDate
+\li "YYYY-MM-DD"
+\li "2010-05-31"
\row
-\o QPoint
-\o "x,y"
-\o "10,20"
+\li QPoint
+\li "x,y"
+\li "10,20"
\row
-\o QRect
-\o "x,y,WidthxHeight"
-\o "50,50,100x100"
+\li QRect
+\li "x,y,WidthxHeight"
+\li "50,50,100x100"
\row
-\o QSize
-\o "WidthxHeight"
-\o "100x200"
+\li QSize
+\li "WidthxHeight"
+\li "100x200"
\row
-\o QTime
-\o "hh:mm:ss"
-\o "14:22:55"
+\li QTime
+\li "hh:mm:ss"
+\li "14:22:55"
\row
-\o QUrl
-\o URL string
-\o "http://www.example.com"
+\li QUrl
+\li URL string
+\li "http://www.example.com"
\row
-\o QVector3D
-\o "x,y,z"
-\o "0,1,0"
+\li QVector3D
+\li "x,y,z"
+\li "0,1,0"
\row
-\o Enumeration value
-\o Enum value name
-\o "AlignRight"
+\li Enumeration value
+\li Enum value name
+\li "AlignRight"
\endtable
(More details on these string formats and types can be found in the
@@ -617,9 +617,9 @@ in order to update the resources in the package.
To use the resource system in a mixed QML/C++ application:
\list
-\o Create a \c .qrc \l {The Qt Resource System}{resource collection file} that lists resource
+\li Create a \c .qrc \l {The Qt Resource System}{resource collection file} that lists resource
files in XML format
-\o From C++, load the main QML file as a resource using the \c :/ prefix or as a URL with the
+\li From C++, load the main QML file as a resource using the \c :/ prefix or as a URL with the
\c qrc scheme
\endlist
diff --git a/doc/src/declarative/qtprogrammers.qdoc b/doc/src/declarative/qtprogrammers.qdoc
index 9178572d..ef4ad141 100644
--- a/doc/src/declarative/qtprogrammers.qdoc
+++ b/doc/src/declarative/qtprogrammers.qdoc
@@ -39,11 +39,11 @@ an application with a UI defined in QML also uses Qt for all the non-UI logic.
QML provides direct access to the following concepts from Qt:
\list
- \o QAction - the \l {QML Basic Types}{action} type
- \o QObject signals and slots - available as functions to call in JavaScript
- \o QObject properties - available as variables in JavaScript
- \o QWidget - QDeclarativeView is a QML-displaying widget
- \o Qt models - used directly in data binding (QAbstractItemModel)
+ \li QAction - the \l {QML Basic Types}{action} type
+ \li QObject signals and slots - available as functions to call in JavaScript
+ \li QObject properties - available as variables in JavaScript
+ \li QWidget - QDeclarativeView is a QML-displaying widget
+ \li Qt models - used directly in data binding (QAbstractItemModel)
\endlist
Qt knowledge is \e required for \l {Extending QML Functionalities using C++},
@@ -57,9 +57,9 @@ haven't traditionally been used to define the look and feel of view delegates, Q
There are three structurally different types of QWidget:
\list
- \o Simple widgets that are not used as parents (QLabel, QCheckBox, QToolButton, etc.)
- \o Parent widgets that are normally used as parents to other widgets (QGroupBox, QStackedWidget, QTabWidget, etc.)
- \o Compound widgets that are internally composed of child widgets (QComboBox, QSpinBox, QFileDialog, QTabWidget, etc.)
+ \li Simple widgets that are not used as parents (QLabel, QCheckBox, QToolButton, etc.)
+ \li Parent widgets that are normally used as parents to other widgets (QGroupBox, QStackedWidget, QTabWidget, etc.)
+ \li Compound widgets that are internally composed of child widgets (QComboBox, QSpinBox, QFileDialog, QTabWidget, etc.)
\endlist
QML Items also serve these purposes. Each is considered separately below.
@@ -120,9 +120,9 @@ this where it is needed).
This difference has rather far-reaching consequences, for example:
\list
- \o A shadow or highlight around a widget could be a child of that widget.
- \o Particle effects can flow outside the object where they originate.
- \o Transitioning animations can "hide" items by visibly moving them beyond the screen bounds.
+ \li A shadow or highlight around a widget could be a child of that widget.
+ \li Particle effects can flow outside the object where they originate.
+ \li Transitioning animations can "hide" items by visibly moving them beyond the screen bounds.
\endlist
diff --git a/doc/src/declarative/qtquick-intro.qdoc b/doc/src/declarative/qtquick-intro.qdoc
index 9658ef1f..4d60c672 100644
--- a/doc/src/declarative/qtquick-intro.qdoc
+++ b/doc/src/declarative/qtquick-intro.qdoc
@@ -84,24 +84,24 @@ extendibility and openness, while aiming to lower the barrier of entry for
newcomers to Qt Quick and Qt. The key features of Qt Creator allow UI designers
and developers to accomplish the following tasks:
\list
-\o Get started with Qt Quick application development quickly and easily with
+\li Get started with Qt Quick application development quickly and easily with
examples, tutorials, and project wizards.
-\o Design application user interface with the integrated editor, Qt Quick
+\li Design application user interface with the integrated editor, Qt Quick
Designer, or use graphics software to design the user interface and use scripts
to export the design to Qt Quick Designer.
-\o Develop applications with the advanced code editor that provides new powerful
+\li Develop applications with the advanced code editor that provides new powerful
features for completing code snippets, refactoring code, and viewing the element
hierarchy of QML files.
-\o Build and deploy Qt Quick applications that target multiple desktop and
+\li Build and deploy Qt Quick applications that target multiple desktop and
mobile platforms, such as Microsoft Windows, Mac OS X, Linux, Symbian, and
Maemo.
-\o Debug JavaScript functions and execute JavaScript expressions in the current
+\li Debug JavaScript functions and execute JavaScript expressions in the current
context, and inspect QML at runtime to explore the object structure, debug
animations, and inspect colors.
-\o Deploy applications to mobile devices and create application installation
+\li Deploy applications to mobile devices and create application installation
packages for Symbian and Maemo devices that can be published in the Ovi Store
and other channels.
-\o Easily access information with the integrated context-sensitive Qt Help
+\li Easily access information with the integrated context-sensitive Qt Help
system.
\endlist
@@ -116,7 +116,7 @@ The \l {QML Examples and Demos} page has a gallery of QML applications.
\section1 License Information
\list
-\o \l{Qt Quick Licensing Information}
+\li \l{Qt Quick Licensing Information}
\endlist
*/
diff --git a/doc/src/declarative/tutorial.qdoc b/doc/src/declarative/tutorial.qdoc
index 85f40fbf..3a596b43 100644
--- a/doc/src/declarative/tutorial.qdoc
+++ b/doc/src/declarative/tutorial.qdoc
@@ -44,9 +44,9 @@ The tutorial's source code is located in the $QTDIR/examples/declarative/tutoria
Tutorial chapters:
\list 1
-\o \l {QML Tutorial 1 - Basic Types}{Basic Types}
-\o \l {QML Tutorial 2 - QML Components}{QML Components}
-\o \l {QML Tutorial 3 - States and Transitions}{States and Transitions}
+\li \l {QML Tutorial 1 - Basic Types}{Basic Types}
+\li \l {QML Tutorial 2 - QML Components}{QML Components}
+\li \l {QML Tutorial 3 - States and Transitions}{States and Transitions}
\endlist
*/
diff --git a/doc/src/declarative/whatsnew.qdoc b/doc/src/declarative/whatsnew.qdoc
index ebae4e1c..5ec06beb 100644
--- a/doc/src/declarative/whatsnew.qdoc
+++ b/doc/src/declarative/whatsnew.qdoc
@@ -48,11 +48,11 @@ different language areas.
Added the following properties:
\list
-\o \l {Text::}{lineHeight}
-\o \l {Text::}{lineHeightMode}
-\o \l {Text::}{lineCount}
-\o \l {Text::}{maximumLineCount}
-\o \l {Text::}{truncated}
+\li \l {Text::}{lineHeight}
+\li \l {Text::}{lineHeightMode}
+\li \l {Text::}{lineCount}
+\li \l {Text::}{maximumLineCount}
+\li \l {Text::}{truncated}
\endlist
horizontalAlignment now accepts Text.AlignJustify alignment mode.
@@ -61,103 +61,103 @@ horizontalAlignment now accepts Text.AlignJustify alignment mode.
Added the following properties, methods and signal handlers:
\list
-\o \l {TextEdit::}{canPaste}
-\o \l {TextEdit::}{lineCount}
-\o \l {TextEdit::}{inputMethodComposing}
-\o \l {TextEdit::}{mouseSelectionMode}
-\o \l {TextEdit::}{deselect()}
-\o \l {TextEdit::}{isRightToLeft()}
-\o \l {TextEdit::}{moveCursorSelection()} to enable selection by word
-\o \l {TextEdit::}{onLinkActivated}
+\li \l {TextEdit::}{canPaste}
+\li \l {TextEdit::}{lineCount}
+\li \l {TextEdit::}{inputMethodComposing}
+\li \l {TextEdit::}{mouseSelectionMode}
+\li \l {TextEdit::}{deselect()}
+\li \l {TextEdit::}{isRightToLeft()}
+\li \l {TextEdit::}{moveCursorSelection()} to enable selection by word
+\li \l {TextEdit::}{onLinkActivated}
\endlist
\section2 TextInput
Added the following properties and methods:
\list
-\o \l {TextInput::}{canPaste}
-\o \l {TextInput::}{inputMethodComposing}
-\o \l {TextInput::}{mouseSelectionMode}
-\o \l {TextInput::}{deselect()}
-\o \l {TextInput::}{isRightToLeft()}
-\o \l {TextInput::}{moveCursorSelection()} to enable selection by word
+\li \l {TextInput::}{canPaste}
+\li \l {TextInput::}{inputMethodComposing}
+\li \l {TextInput::}{mouseSelectionMode}
+\li \l {TextInput::}{deselect()}
+\li \l {TextInput::}{isRightToLeft()}
+\li \l {TextInput::}{moveCursorSelection()} to enable selection by word
\endlist
\section2 Image, BorderImage and AnimatedImage
Added the following properties:
\list
-\o \l{Image::}{cache}
-\o \l{Image::}{mirror}
+\li \l{Image::}{cache}
+\li \l{Image::}{mirror}
\endlist
\section2 Item
Added the following properties:
\list
-\o \l{Item::}{implicitWidth} and \l{Item::}{implicitHeight}
+\li \l{Item::}{implicitWidth} and \l{Item::}{implicitHeight}
\endlist
\section2 Flickable
Added the following methods:
\list
-\o \l{Flickable::}{resizeContent()}
-\o \l{Flickable::}{returnToBounds()}
+\li \l{Flickable::}{resizeContent()}
+\li \l{Flickable::}{returnToBounds()}
\endlist
\section2 MouseArea
Added the following property:
\list
-\o \l{MouseArea::}{preventStealing}
+\li \l{MouseArea::}{preventStealing}
\endlist
\section2 ListView and GridView
Added the following properties and methods:
\list
-\o \l{ListView::}{layoutDirection}
-\o \l{ListView::}{positionViewAtBeginning()}
-\o \l{ListView::}{positionViewAtEnd()}
+\li \l{ListView::}{layoutDirection}
+\li \l{ListView::}{positionViewAtBeginning()}
+\li \l{ListView::}{positionViewAtEnd()}
\endlist
\section2 Flow, Grid and Row
Added the following property:
\list
-\o \l{Flow::}{layoutDirection}
+\li \l{Flow::}{layoutDirection}
\endlist
\section2 Repeater
Added the following methods and signal handlers:
\list
-\o \l{Repeater::}{onItemAdded}
-\o \l{Repeater::}{onItemRemoved}
-\o \l{Repeater::}{itemAt()}
+\li \l{Repeater::}{onItemAdded}
+\li \l{Repeater::}{onItemRemoved}
+\li \l{Repeater::}{itemAt()}
\endlist
\section2 Component
\list
-\o The \l{Component::}{createObject()} method now accepts a map of initial
+\li The \l{Component::}{createObject()} method now accepts a map of initial
property values for the created object.
\endlist
\section2 Qt
\list
-\o Added the \l {QML:Qt::application}{Qt.application} object to hold generic
+\li Added the \l {QML:Qt::application}{Qt.application} object to hold generic
global application properties.
\endlist
\section2 Other changes
\list
-\o Functions can be \l{Property Binding#Property Binding}{assigned to properties from JavaScript}
+\li Functions can be \l{Property Binding#Property Binding}{assigned to properties from JavaScript}
to create property bindings.
-\o QtQuick now supports Right to Left layout in positioners, views, anchors and text elements.
+\li QtQuick now supports Right to Left layout in positioners, views, anchors and text elements.
\endlist
diff --git a/doc/src/examples/qml-examples.qdoc b/doc/src/examples/qml-examples.qdoc
index 8b537cbe..57b97b19 100644
--- a/doc/src/examples/qml-examples.qdoc
+++ b/doc/src/examples/qml-examples.qdoc
@@ -34,9 +34,9 @@
\table
\row
- \o \image qml-coloranim-example.png
+ \li \image qml-coloranim-example.png
\row
- \o color-animation.qml
+ \li color-animation.qml
\endtable
*/
@@ -49,9 +49,9 @@
\table
\row
- \o \image qml-propertyanim-example.png
+ \li \image qml-propertyanim-example.png
\row
- \o property-animation.qml
+ \li property-animation.qml
\endtable
*/
@@ -100,16 +100,16 @@
\table
\row
- \o \image qml-states-example.png
+ \li \image qml-states-example.png
\row
- \o states.qml
+ \li states.qml
\endtable
\table
\row
- \o \image qml-transitions-example.png
+ \li \image qml-transitions-example.png
\row
- \o transitions.qml
+ \li transitions.qml
\endtable
*/
@@ -123,9 +123,9 @@
\table
\row
- \o \image qml-borderimage-example.png
+ \li \image qml-borderimage-example.png
\row
- \o borderimage.qml
+ \li borderimage.qml
\endtable
*/
@@ -138,9 +138,9 @@
\table
\row
- \o \image qml-borderimage-shadows-example.png
+ \li \image qml-borderimage-shadows-example.png
\row
- \o shadows.qml
+ \li shadows.qml
\endtable
*/
@@ -167,16 +167,16 @@
Furthermore, here are additional pages that discuss each example in detail:
\list
- \o \l {declarative/cppextensions/referenceexamples/adding}{Adding Types}
- \o \l {declarative/cppextensions/referenceexamples/properties}{Object and List Property Types}
- \o \l {declarative/cppextensions/referenceexamples/coercion}{Inheritance and Coercion}
- \o \l {declarative/cppextensions/referenceexamples/default}{Default Property}
- \o \l {declarative/cppextensions/referenceexamples/grouped}{Grouped Properties}
- \o \l {declarative/cppextensions/referenceexamples/attached}{Attached Properties}
- \o \l {declarative/cppextensions/referenceexamples/signal}{Signal Support}
- \o \l {declarative/cppextensions/referenceexamples/methods}{Methods Support}
- \o \l {declarative/cppextensions/referenceexamples/valuesource}{Property Value Source}
- \o \l {declarative/cppextensions/referenceexamples/binding}{Binding}
+ \li \l {declarative/cppextensions/referenceexamples/adding}{Adding Types}
+ \li \l {declarative/cppextensions/referenceexamples/properties}{Object and List Property Types}
+ \li \l {declarative/cppextensions/referenceexamples/coercion}{Inheritance and Coercion}
+ \li \l {declarative/cppextensions/referenceexamples/default}{Default Property}
+ \li \l {declarative/cppextensions/referenceexamples/grouped}{Grouped Properties}
+ \li \l {declarative/cppextensions/referenceexamples/attached}{Attached Properties}
+ \li \l {declarative/cppextensions/referenceexamples/signal}{Signal Support}
+ \li \l {declarative/cppextensions/referenceexamples/methods}{Methods Support}
+ \li \l {declarative/cppextensions/referenceexamples/valuesource}{Property Value Source}
+ \li \l {declarative/cppextensions/referenceexamples/binding}{Binding}
\endlist
\note These examples all print information to the console to demonstrate the concepts presented.
@@ -230,9 +230,9 @@
layout components with QML:
\list
- \o \l{declarative/cppextensions/qgraphicslayouts/layoutitem}{LayoutItem}
- \o \l{declarative/cppextensions/qgraphicslayouts/qgraphicsgridlayout}{QGraphicsGridLayout}
- \o \l{declarative/cppextensions/qgraphicslayouts/qgraphicslinearlayout}{QGraphicsLinearLayout}
+ \li \l{declarative/cppextensions/qgraphicslayouts/layoutitem}{LayoutItem}
+ \li \l{declarative/cppextensions/qgraphicslayouts/qgraphicsgridlayout}{QGraphicsGridLayout}
+ \li \l{declarative/cppextensions/qgraphicslayouts/qgraphicslinearlayout}{QGraphicsLinearLayout}
\endlist
Also see \l {Integrating QML Code with Existing Qt UI Code} for information on using QML
@@ -404,11 +404,11 @@
\page qml-listview-examples.html
\list
- \o \l {Models and Views: Dynamic List ListView Example}
- \o \l {Models and Views: Expanding Delegate ListView Example}
- \o \l {Models and Views: Highlight ListView Example}
- \o \l {Models and Views: Highlight Ranges ListView Example}
- \o \l {Models and Views: Sections ListView Example}
+ \li \l {Models and Views: Dynamic List ListView Example}
+ \li \l {Models and Views: Expanding Delegate ListView Example}
+ \li \l {Models and Views: Highlight ListView Example}
+ \li \l {Models and Views: Highlight Ranges ListView Example}
+ \li \l {Models and Views: Sections ListView Example}
\endlist
*/
@@ -424,9 +424,9 @@
\table
\row
- \o \image qml-listview-dynamiclist-example.png
+ \li \image qml-listview-dynamiclist-example.png
\row
- \o dynamiclist.qml
+ \li dynamiclist.qml
\endtable
*/
@@ -440,9 +440,9 @@
\table
\row
- \o \image qml-listview-expandingdelegates-example.png
+ \li \image qml-listview-expandingdelegates-example.png
\row
- \o expandingdelegates.qml
+ \li expandingdelegates.qml
\endtable
*/
@@ -457,9 +457,9 @@
\table
\row
- \o \image qml-listview-highlight-example.png
+ \li \image qml-listview-highlight-example.png
\row
- \o highlight.qml
+ \li highlight.qml
\endtable
*/
@@ -474,9 +474,9 @@
\table
\row
- \o \image qml-listview-highlightranges-example.png
+ \li \image qml-listview-highlightranges-example.png
\row
- \o highlightranges.qml
+ \li highlightranges.qml
\endtable
*/
@@ -490,9 +490,9 @@
\table
\row
- \o \image qml-listview-sections-example.png
+ \li \image qml-listview-sections-example.png
\row
- \o sections.qml
+ \li sections.qml
\endtable
*/
@@ -563,11 +563,11 @@
\brief These examples show how to use the WebView element.
\list
- \o \l {Models and Views: Alert WebView Example}
- \o \l {Models and Views: Autosize WebView Example}
- \o \l {Models and Views: GoogleMaps WebView Example}
- \o \l {Models and Views: Inline HTML WebView Example}
- \o \l {Models and Views: New Windows WebView Example}
+ \li \l {Models and Views: Alert WebView Example}
+ \li \l {Models and Views: Autosize WebView Example}
+ \li \l {Models and Views: GoogleMaps WebView Example}
+ \li \l {Models and Views: Inline HTML WebView Example}
+ \li \l {Models and Views: New Windows WebView Example}
\endlist
@@ -581,9 +581,9 @@
\table
\row
- \o \image qml-webview-alert-example.png
+ \li \image qml-webview-alert-example.png
\row
- \o alert.qml
+ \li alert.qml
\endtable
*/
@@ -596,9 +596,9 @@
\table
\row
- \o \image qml-webview-autosize-example.png
+ \li \image qml-webview-autosize-example.png
\row
- \o autosize.qml
+ \li autosize.qml
\endtable
*/
@@ -611,9 +611,9 @@
\table
\row
- \o \image qml-webview-googlemaps-example.png
+ \li \image qml-webview-googlemaps-example.png
\row
- \o googlemaps.qml
+ \li googlemaps.qml
\endtable
*/
@@ -626,9 +626,9 @@
\table
\row
- \o \image qml-webview-inlinehtml-example.png
+ \li \image qml-webview-inlinehtml-example.png
\row
- \o inlinehtml.qml
+ \li inlinehtml.qml
\endtable
*/
@@ -641,9 +641,9 @@
\table
\row
- \o \image qml-webview-newwindows-example.png
+ \li \image qml-webview-newwindows-example.png
\row
- \o newwindows.qml
+ \li newwindows.qml
\endtable
*/
@@ -672,9 +672,9 @@
\table
\row
- \o \image qml-fonts-availableFonts-example.png
+ \li \image qml-fonts-availableFonts-example.png
\row
- \o availableFonts.qml
+ \li availableFonts.qml
\endtable
*/
@@ -687,9 +687,9 @@
\table
\row
- \o \image qml-fonts-banner-example.png
+ \li \image qml-fonts-banner-example.png
\row
- \o banner.qml
+ \li banner.qml
\endtable
*/
@@ -702,9 +702,9 @@
\table
\row
- \o \image qml-fonts-fonts-example.png
+ \li \image qml-fonts-fonts-example.png
\row
- \o fonts.qml
+ \li fonts.qml
\endtable
*/
@@ -717,9 +717,9 @@
\table
\row
- \o \image qml-fonts-hello-example.png
+ \li \image qml-fonts-hello-example.png
\row
- \o hello.qml
+ \li hello.qml
\endtable
*/
diff --git a/doc/src/examples/qml-extending.qdoc b/doc/src/examples/qml-extending.qdoc
index b7e74dca..b479d5ab 100644
--- a/doc/src/examples/qml-extending.qdoc
+++ b/doc/src/examples/qml-extending.qdoc
@@ -67,7 +67,7 @@ loads and runs the QML snippet shown at the beginning of this page.
This example builds on:
\list
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
The Object and List Property Types example shows how to add object and list
@@ -115,8 +115,8 @@ loads and runs the QML snippet shown at the beginning of this page.
This example builds on:
\list
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
The Inheritance and Coercion Example shows how to use base classes to assign
@@ -178,9 +178,9 @@ loads and runs the QML snippet shown at the beginning of this page.
This example builds on:
\list
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
The Default Property Example is a minor modification of the
@@ -214,10 +214,10 @@ loads and runs the QML snippet shown at the beginning of this page.
This example builds on:
\list
-\o \l {Extending QML - Default Property Example}
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Default Property Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
*/
@@ -228,11 +228,11 @@ This example builds on:
This example builds on:
\list
-\o \l {Extending QML - Grouped Properties Example}
-\o \l {Extending QML - Default Property Example}
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Grouped Properties Example}
+\li \l {Extending QML - Default Property Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
*/
@@ -243,12 +243,12 @@ This example builds on:
This example builds on:
\list
-\o \l {Extending QML - Attached Properties Example}
-\o \l {Extending QML - Grouped Properties Example}
-\o \l {Extending QML - Default Property Example}
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Attached Properties Example}
+\li \l {Extending QML - Grouped Properties Example}
+\li \l {Extending QML - Default Property Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
*/
@@ -259,10 +259,10 @@ This example builds on:
This example builds on:
\list
-\o \l {Extending QML - Default Property Example}
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Default Property Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
*/
@@ -273,13 +273,13 @@ This example builds on:
This example builds on:
\list
-\o \l {Extending QML - Signal Support Example}
-\o \l {Extending QML - Attached Properties Example}
-\o \l {Extending QML - Grouped Properties Example}
-\o \l {Extending QML - Default Property Example}
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Signal Support Example}
+\li \l {Extending QML - Attached Properties Example}
+\li \l {Extending QML - Grouped Properties Example}
+\li \l {Extending QML - Default Property Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
*/
@@ -290,14 +290,14 @@ This example builds on:
This example builds on:
\list
-\o \l {Extending QML - Property Value Source Example}
-\o \l {Extending QML - Signal Support Example}
-\o \l {Extending QML - Attached Properties Example}
-\o \l {Extending QML - Grouped Properties Example}
-\o \l {Extending QML - Default Property Example}
-\o \l {Extending QML - Inheritance and Coercion Example}
-\o \l {Extending QML - Object and List Property Types Example}
-\o \l {Extending QML - Adding Types Example}
+\li \l {Extending QML - Property Value Source Example}
+\li \l {Extending QML - Signal Support Example}
+\li \l {Extending QML - Attached Properties Example}
+\li \l {Extending QML - Grouped Properties Example}
+\li \l {Extending QML - Default Property Example}
+\li \l {Extending QML - Inheritance and Coercion Example}
+\li \l {Extending QML - Object and List Property Types Example}
+\li \l {Extending QML - Adding Types Example}
\endlist
*/
diff --git a/doc/src/getting-started/gettingstartedqml.qdoc b/doc/src/getting-started/gettingstartedqml.qdoc
index 7a791959..923d8ff1 100644
--- a/doc/src/getting-started/gettingstartedqml.qdoc
+++ b/doc/src/getting-started/gettingstartedqml.qdoc
@@ -69,11 +69,11 @@
Tutorial chapters:
\list 1
- \o \l {Defining a Button and a Menu}{Defining a Button and a Menu}
- \o \l {Implementing a Menu Bar}{Implementing a Menu Bar}
- \o \l {Building a Text Editor}{Building a Text Editor}
- \o \l {Decorating the Text Editor}{Decorating the Text Editor}
- \o \l {Extending QML using Qt C++}{Extending QML using Qt C++}
+ \li \l {Defining a Button and a Menu}{Defining a Button and a Menu}
+ \li \l {Implementing a Menu Bar}{Implementing a Menu Bar}
+ \li \l {Building a Text Editor}{Building a Text Editor}
+ \li \l {Decorating the Text Editor}{Decorating the Text Editor}
+ \li \l {Extending QML using Qt C++}{Extending QML using Qt C++}
\endlist
\section1 Defining a Button and a Menu
@@ -645,11 +645,11 @@
For our application, we need to create the following items:
\list 1
- \o \c Directory class that will handle directory related operations
- \o \c File class which is a QObject, simulating the list of files in a directory
- \o plugin class that will register the class to the QML context
- \o Qt project file that will compile the plugin
- \o A \c qmldir file telling the qmlviewer tool where to find the plugin
+ \li \c Directory class that will handle directory related operations
+ \li \c File class which is a QObject, simulating the list of files in a directory
+ \li plugin class that will register the class to the QML context
+ \li Qt project file that will compile the plugin
+ \li A \c qmldir file telling the qmlviewer tool where to find the plugin
\endlist
\section3 Building a Qt Plugin
diff --git a/doc/src/howtos/qmlbestpractices/qmlbestpractices-coding.qdoc b/doc/src/howtos/qmlbestpractices/qmlbestpractices-coding.qdoc
index 4b908422..2b03366d 100644
--- a/doc/src/howtos/qmlbestpractices/qmlbestpractices-coding.qdoc
+++ b/doc/src/howtos/qmlbestpractices/qmlbestpractices-coding.qdoc
@@ -79,8 +79,8 @@ mean the code is confusing.
Similar to JavaScript or C++, there are two ways of commenting QML code:
\list
-\o Single line comments start with \c{//} and finish at the end of the line
-\o Multiline comments start with \c{/*} and finish with *\/
+\li Single line comments start with \c{//} and finish at the end of the line
+\li Multiline comments start with \c{/*} and finish with *\/
\endlist
\section1 Group Properties