QML Documentation Style

This page is part of the Qt Writing Guidelines.

Documentation using QDoc

Qt uses QDoc to generate the QML documentation.

To get started, familiarize yourself with how QDoc works and the basics of setting up a QDoc project.

• QDoc Manual
  • The QDoc Configuration File
  • Topic Commands
  • Context Commands
  • Markup Commands
  • Macros

The general guideline is: Make your documentation set consistent with the rest of Qt.

Follow existing C++ ´documentation and make sure the documentation fits into the current structure.

How QDoc generates QML documentation

QDoc can document QML types with a C++ definition or a purely QML defined type.

QDoc can parse through .cpp implementation files and .qml files, creating a QML node tree to resolve the type properties, functions, and modules. For Qt documentation, QDoc assumes that a QML type may be:

• implemented in C++ .cpp files. C++ class documentation must exist.
• implemented using QML in .qml files. QML documentation must be above the declaration.
• implicitly defined in Javascript or aliases. QML documentation may be in a QDoc .qdoc file.

Otherwise, QDoc will output warnings and will not resolve the QML documentation properly.

QML modules and versions

In Qt 6, QML versioning is no longer applicable but QDoc can still apply versioning to the QML documentation if you need.

For QML modules, the following commands document a module:

• \qmlmodule - QDoc generates the import statement from the module
• \inqmlmodule - types and member documentation can declare membership to a QML module

A QML module documentation must also include:

• \brief - the class' brief description. See section below on the Brief.
• \since - the version when class was added
• \inmodule - associates a class to a Qt module
• \section1 QML Types - use \generatelist and QDoc generates a list of types in the module. See example below
• \section1 Related Information - include links to relevant documentation such as examples or related modules

The example below generates the documentation for the QtNetwork QML module page.

/*!
    \qmlmodule QtNetwork
    \title Qt QML Network QML Types
    \since 6.7
    \ingroup qmlmodules
    \brief Provides core network functionality in QML.

    The Qt QML Network module provides core network functionality in QML.

    The QML types can be imported into your application using the
    following import statement in your .qml file:

    \qml
    import QtNetwork
    \endqml

    \section1 QML Types

    \generatelist {qmltypesbymodule QtNetwork}

    \section1 Related Information
    \list
        \li \l {Qt Network}
        \li \l {Qt Qml QML Types}{Base QML Types}
    \endlist
    \noautolist
*/

QML Types

QML type documentation is generated using the \qmltype command.

Context commands add information about the type, such as its module or which version the class was added.

Some mandatory context commands are:

• \brief - the class' brief description. See section below on the Brief

• \since - the version when class was added

• \inqmlmodule - types and member documentation can declare membership to a QML module

Other important context commands:

• \internal - marks the type as internal. Internal types including their members do not appear in the public API documentation
• \nativetype - set to the C++ class and QDoc creates associations between the C++ and QML documentation

The Brief and Detailed Description

The brief description is marked with the \brief command and it is for summarizing the purpose or functionality of the class. QDoc adds the brief descriptions to the annotated lists and tables listing the QML types.

It is a good practice to begin a brief description with a verb, but a noun is appropriate in some areas. Ensure that the brief fits into a QDoc generated table.

Some common initial words for the brief:

• Provides...
• Contains...
• Generates...
• Convenience wrapper...

The Detailed Description section starts after the brief description. It provides more information about the class. The detailed description may contain images, snippet code, or links to other relevant documents. There must be an empty line which separates the brief and detailed description.

The example below generates the documentation for NetworkInformation QML type.

/*!
    \qmltype NetworkInformation
    \inqmlmodule QtNetwork
    \nativetype QNetworkInformation
    \brief  Provides a cross-platform interface to network-related information.

    NetworkInformation provides a cross-platform interface to network-related information.

    NetworkInformation is a singleton.

    \sa QNetworkInformation
*/

Properties

The property description focuses on what the property does. Property documentation usually starts with "This property…" but for certain properties, these are the common expressions:

• "This property holds…"
• "This property describes…"
• "This property represents…"
• "Returns true when… and false when…" - for properties that are marked read-only.
• "Sets the…" - for properties that configure a type.

Aliases

The QDoc parser cannot guess the type of the alias, therefore, the type must be fully documented with the \qmlproperty command.

Signals and Handlers Documentation

QML signals are documented either in the QML file or in the C++ implementation with the \qmlsignal command. Signal documentation must include the condition for emitting the signal, mention the corresponding signal handler, and document whether the signal accepts a parameter.

/*
 This signal is emitted when the user clicks the button. A click is defined
 as a press followed by a release. The corresponding handler is
 onClicked.
*/

These are the possible documentation styles for signals:

• "This signal is triggered when…"
• "Triggered when…"
• "Emitted when…"

Read-Only Properties

To mark that a property is a read-only property, add the \readonly command to the property documentation. QDoc then notes that the property is a read-only property.

For properties that are declared in QML files with the readonly keyword, QDoc can detect that it is a read-only property and will automatically add the read-only marking.

Methods and JavaScript Functions

Typically, function documentation immediately precedes the implementation of the function in the .cpp file. The topic command for functions is \qmlmethod. For functions in QML or JavaScript, the documentation must reside immediately above the function declaration.

The function documentation starts with a verb, indicating the operation the function performs.

/*!
    \qmlmethod QtQuick2::ListModel::remove(int index, int count = 1)

    Deletes the content at \a index from the model.

    \sa clear()
*/
void QQuickListModel::remove(QQmlV8Function *args)

Some common verbs for function documentation:

• "Copies…" - for constructors
• "Destroys…" - for destructors
• "Returns…" - for accessor functions

The function documentation must document:

• the return type
• the parameters
• the actions of the functions

The \a command marks the parameter in the documentation. The return type documentation should link to the type documentation or be marked with the \c command in the case of Boolean values.

Enumerations

QML enumerations are documented as QML properties with the \qmlproperty command. The type of the property is enumeration.

/*!
    \qmlproperty enumeration QtQuick2::Text::font.weight

    Sets the font's weight.

    The weight can be one of:
    \list
    \li Font.Light
    \li Font.Normal - the default
    \li Font.DemiBold
    \li Font.Bold
    \li Font.Black
    \endlist

    \qml
    Text { text: "Hello"; font.weight: Font.DemiBold }
    \endqml
*/

To begin the description, use:

• "This enumeration…"