When you add plugins or contribute new features to Qt Creator, you probably want other people to know about them and to be able to use them. Therefore, you should also contribute documentation for them. Follow the guidelines in this section to make sure that your documentation fits in well with the rest of the Qt Creator documentation.
When you contribute a plugin, you should write documentation both for the developers who use Qt Creator and for the ones who develop it.
Write the following user documentation for addition to the Qt Creator Manual:
Write the following developer documentation for addition to the Extending Qt Creator Manual:
Qt Creator documentation is written by using QDoc. For more information about using QDoc, see QDoc Reference Documentation.
QDoc finds the new topics automatically, when you place them as .qdoc files in the correct folder. However, to make the topics accessible to readers, you must also add them to the table of contents and fix the next page and previous page links to them from other topics.
These instructions apply only to the Qt Creator Manual. Add API documentation directly to the code source files. However, you can write an API overview also as a separate .qdoc file.
Create a subfolder for your documentation in the Qt Creator project folder in the doc\src folder. Create a separate file for each topic.
The easiest way is probably to copy an existing file, save it as a new file, and modify it. This way, you already have samples of the necessary bits and pieces in place, such as topic start and end commands, copyright statement, links to next and previous topics, and topic title.
You must integrate your new topics to the Qt Creator Manual and Extending Qt Creator Manual by adding links to them to the table of contents and to other relevant topics.
To link to the topic, you can use the topic title. For example:
\l{Integrating Topics to Documentation}
This does not work if topic titles are not unique. Also, if you change the title, the link breaks. You can avoid this risk by adding the \target command to your topic and then linking to the target.
When you add new topics to a document, you must also change the navigation links of the topics around them. This is very error prone when done manually, and therefore we have a script called fixnavi.pl for it. For the script to work, you must add the \nextpage and \previouspage commands to the topic, with dummy values (for example, \nextpage=anything.html).
Note: The script creates the links according to the TOC on the front page. If your topics are not listed in the TOC, the script removes the \nextpage and \previouspage commands from them.
To run the script, you must have Perl installed. If you build Qt yourself, you should already have it. Otherwise, download and install Perl.
To run the script, enter the following command in the doc folder:
Follow the guidelines for writing Qt documentation.
The documentation must be grammatically correct English and use the standard form of written language. Do not use dialect or slang words. Use idiomatic language, that is, expressions that are characteristic for English. If possible, ask a native English speaker for a review.
Use the book title capitalization style for all titles and section headings (\title, \section1, \section2, and so on). For more information, see Using Book Style Capitalization.
You can illustrate your documentation by using screen shots, diagrams, and other images.
Qt Creator has the native look and feel on Windows, Linux, and Mac OS, and therefore, screen shots can end up looking very different, depending on who takes them and which system they use. To try to preserve a consistent look and feel in the Qt Creator Manual, observe the guidelines listed in this section when taking screen shots.
To make the images look similar regardless of the operating system they were taken on, you are asked to adjust their size to 75%. This makes the screen shots hard to read, but they are provided more as reassurance for users that they are in the correct place in the UI than as an actual source of information. To make sure that no important information is lost, always place example values also in the text.
Save images in the PNG format in the Qt Creator project folder in the doc\images folder. Binary images can easily add megabytes to the Git history. To keep the history as small as possible, the Git post-commit hooks remind you to try to keep image size below 50 kilobytes. To achieve this goal, crop images so that only relevant information is visible in them. Before committing images, optimize them by using an image optimization tool.
Optimization should not visibly reduce image quality. If it does, do not do it. You can use the Radical Image Optimization Tool (RIOT) on Windows (very efficient) or ImageOptim on Mac OS (much less efficient), or some other tool available on Linux.
With ImageOptim, you simply drag and drop the image files to the application. The following section describes the settings to use for RIOT.
Use the \image and \inlineimage QDoc commands to refer to images from the text. You do not need to add paths to image names. For example:
\image riot.png
Download and install RIOT.
[Missing image riot.png]
Open your images in RIOT and use the following settings for them:
Compare the initial and optimized images to check that image quality is preserved. If the image quality deteriorates, do not use color reduction (select the True Color option, instead).
You can also see the sizes of the initial and optimized image.
You use QDoc to build the documentation. Build the documentation from time to time, to check its structure and the validity of the QDoc commands. The error messages that QDoc issues are generally very useful for troubleshooting.
The content and formatting of documentation are separated in QDoc. The documentation configuration, style sheets, and templates have changed over time, so they differ between Qt and Qt Creator versions. In Qt 4, separate style sheets are used to generate help files for Qt Creator and online documentation for the Web.
In Qt 5, only one set of templates is used, as defined by the qt5\qtbase\doc\global\qt-module-defaults.qdocconf configuration file. It is fetched from Qt sources by adding the following line to the qdocconf file:
include ($QT_INSTALL_DOCS/global/qt-module-defaults.qdocconf)
To pick the Qt to use, run qmake from either Qt 4 or Qt 5.
To build documentation for the sources from the qtcreator master branch, use build scripts defined in the doc.pri file. To build all Qt Creator docs in the help format and to create help files (.qch), enter the following build commands from the project folder (after running qmake):
Besides docs, you have the following options: