mirror of https://github.com/qt/qtbase.git
6cfd7944bf
The existing implementation only works for online HTML and the workaround generates nonsensical DocBook that not a single processor could parse. This implementation is not ideal, but gives enough information for processors to do their job (i.e. the tab title and contents are uniquely linked, the tabs in a group are related). Unaware processors still render useful information to the user thanks to links. The ideal presentation would use a container such as `formalgroup` for the tabs, but there is no notion of tab in DocBook. The missing part in this patch is allowing all uses of tabs with DocBook; they are still guarded by `\if defined(onlinedocs)`. For instance, this change updates `porting-to-ios.xml` from: ```xml <db:listitem…> <db:para>If your application uses imports or plugins that depend on special Qt modules, these Qt modules should be added to your build configuration file. For example, if your application uses the Qt Multimedia import in QML, you should add the following to your .pro or CMakeLists.txt file: </db:para> <db:section xml:id="using-cmake"> <db:title>Using CMake</db:title> <db:programlisting language="cpp" role="bad">find_package(Qt6 REQUIRED COMPONENTS Multimedia) target_link_libraries(my_project PRIVATE Qt6::Multimedia) </db:programlisting> </db:section> <db:section xml:id="using-qmake"> <db:title>Using qmake</db:title> <db:programlisting language="cpp" role="bad">QT += multimedia </db:programlisting> <db:para>In Qt for iOS, everything is compiled statically and placed into the application bundle. The applications are "sandboxed" inside their bundles and cannot make use of shared object files. Because of this, also the plugins used by the Qt modules need to be statically linked. To do this, define the required plugins using the <db:link xlink:href="qmake-variable-reference.xml#qtplugin">QTPLUGIN</db:link> variable.</db:para> </db:section> ``` to: ```xml <db:listitem…> <db:para>If your application uses imports or plugins that depend on special Qt modules, these Qt modules should be added to your build configuration file. For example, if your application uses the Qt Multimedia import in QML, you should add the following to your .pro or CMakeLists.txt file: </db:para> <db:bridgehead xml:id="tab-cmake" renderas="sect5" role="tabbed checked tab-group_build-ios-app" xlink:href="#tab-cmake_contents">CMake</db:bridgehead> <db:bridgehead xml:id="tab-qmake" renderas="sect5" role="tabbed checked tab-group_build-ios-app" xlink:href="#tab-qmake_contents">qake</db:bridgehead> <db:sidebar xml:id="tab-cmake_contents"> <db:programlisting language="cpp" role="bad">find_package(Qt6 REQUIRED COMPONENTS Multimedia) target_link_libraries(my_project PRIVATE Qt6::Multimedia) </db:programlisting> </db:sidebar> <db:sidebar xml:id="tab-qmake_contents"> <db:programlisting language="cpp" role="bad">QT += multimedia </db:programlisting> </db:sidebar> ``` Change-Id: I63f3e8d03a5f4ee52e7c67971d14d4497dd78cb8 Reviewed-by: Paul Wicking <paul.wicking@qt.io> |
||
|---|---|---|
| .. | ||
| externalsites | ||
| includes | ||
| includes-online | ||
| snippets/code | ||
| template | ||
| tools-doc-front-page | ||
| compat.qdocconf | ||
| config.qdocconf | ||
| cpp-doc-macros.qdocconf | ||
| externalsites.qdocconf | ||
| fileextensions.qdocconf | ||
| grid.qdocconf | ||
| html-config.qdocconf | ||
| html-footer-online.qdocconf | ||
| html-footer.qdocconf | ||
| html-header-offline.qdocconf | ||
| html-header-online.qdocconf | ||
| htmltabs.qdocconf | ||
| macros-online.qdocconf | ||
| macros.qdocconf | ||
| manifest-meta.qdocconf | ||
| qt-cpp-defines.qdocconf | ||
| qt-html-templates-offline-simple.qdocconf | ||
| qt-html-templates-offline.qdocconf | ||
| qt-html-templates-online.qdocconf | ||
| qt-module-defaults-offline.qdocconf | ||
| qt-module-defaults-online-commercial.qdocconf | ||
| qt-module-defaults-online.qdocconf | ||
| qt-module-defaults.qdocconf | ||
| warninglimit.qdocconf | ||