Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Qt5DocumentationProject: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
=The Qt 5 Documentation Renewal Project=
h1. The Qt 5 Documentation Renewal Project


We are working on restructuring and renewing and fixing the Qt Reference Documentation for the Qt 5 release. This consists of several parts:
We are working on restructuring and renewing and fixing the Qt Reference Documentation for the Qt 5 release. This consists of several parts:


* <span class="caps">API</span> documentation: C++ <span class="caps">API</span>, <span class="caps">QML</span> <span class="caps">API</span>, and JavaScript related functions
* API documentation: C++ API, QML API, and JavaScript related functions
* Examples and example documentation: shows how the <span class="caps">API</span> are used
* Examples and example documentation: shows how the API are used
* Overviews: explains the architecture and features of Qt
* Overviews: explains the architecture and features of Qt


==Changes from Qt 4 to Qt 5==
== Changes from Qt 4 to Qt 5 ==


Here is a brief summary of the important changes in the Qt 5 documentation:
Here is a brief summary of the important changes in the Qt 5 documentation:<br />* QDoc's binary is now ''qdoc'' whereas in Qt 4, the binary is called ''qdoc3''<br />* The documentation is ''modularized''. This means that the documentation for each module resides in their respective source directories. The directory ''doc/src'' is no longer used to contain overviews and API documentation<br />* The Qt modules will have their own pages and they may be treated as separate projects with different release schedules.


* QDoc’s binary is now ''qdoc'' whereas in Qt 4, the binary is called ''qdoc3''
== Important Resources ==
* The documentation is ''modularized''. This means that the documentation for each module resides in their respective source directories. The directory ''doc/src'' is no longer used to contain overviews and <span class="caps">API</span> documentation
* The Qt modules will have their own pages and they may be treated as separate projects with different release schedules.


==Important Resources==
These are important resources for contributing to or working with the documentation.<br />* [[Checklist for Adding Documentation for a New Module | Adding Documentation to a New Module]]<br />* [[Documentation | Qt Documentation Wiki]] - the main Documentation wiki which contains style information and contribution details<br />* &quot;QDoc Manual&amp;quot;:http://doc-snapshot.qt.io/qt5-stable/qdoc/qdoc-index.html - contains a guide to QDoc as well as information about C++ and QML commands<br />* [[Qt_Documentation_Structure | Documentation Structure]] page contains a map of how the directory structure of a repository or module should be<br />* [[Building_Qt_Documentation | Building Qt Documentation]] - outlines how to build the documentation for Qt 5 and for each module<br />* [[QtWritingGuidelines | Qt Writing Guidelines]]<br />* &quot;http://doc-snapshot.qt.io/&amp;quot;:http://doc-snapshot.qt.io/ - the documentation snapshot


These are important resources for contributing to or working with the documentation.
== API Documentation in Qt 5 ==


* [[Checklist-for-Adding-Documentation-for-a-New-Module|Adding Documentation to a New Module]]
Essentially, each module needs:<br />* landing page (using the command) [[QtLandingPage | see specifications]]<br />* example page<br />* c++ class list (using the command)<br />* qml type list (command)
* [[Documentation|Qt Documentation Wiki]] – the main Documentation wiki which contains style information and contribution details
* [http://doc-snapshot.qt.io/qt5-stable/qdoc/qdoc-index.html QDoc Manual] ''[doc-snapshot.qt.io]'' – contains a guide to QDoc as well as information about C++ and <span class="caps">QML</span> commands
* [[Qt Documentation Structure|Documentation Structure]] page contains a map of how the directory structure of a repository or module should be
* [[Building Qt Documentation]] – outlines how to build the documentation for Qt 5 and for each module
* [[QtWritingGuidelines|Qt Writing Guidelines]]
* http://doc-snapshot.qt.io/ ''[doc-snapshot.qt.io]'' – the documentation snapshot


==<span class="caps">API</span> Documentation in Qt 5==
To get started, the &quot;QDoc Guide&amp;quot;:http://doc-snapshot.qt.io/qdoc/qdoc-guide.html explains how QDoc generates documentation from QDoc comments.


Essentially, each module needs:
== Overview Documentation ==


* landing page (using the \page command) [[QtLandingPage|see specifications]]
Overviews describe a functionality, a group of APIs, and the technology in Qt. These overviews help developers decide which feature or API suits them best and helps them understand how the API cooperate within Qt and their applications.
* example page
* c++ class list (using the \module command)
* qml type list (\qmlmodule command)
 
To get started, the [http://doc-snapshot.qt.io/qdoc/qdoc-guide.html QDoc Guide] ''[doc-snapshot.qt.io]'' explains how QDoc generates documentation from QDoc comments.
 
==Overview Documentation==
 
Overviews describe a functionality, a group of <span class="caps">API</span>s, and the technology in Qt. These overviews help developers decide which feature or <span class="caps">API</span> suits them best and helps them understand how the <span class="caps">API</span> cooperate within Qt and their applications.


For Qt 5, many of the overviews are being edited and rewritten for correctness and relevancy.
For Qt 5, many of the overviews are being edited and rewritten for correctness and relevancy.


==Example documentation==
== Example documentation ==
 
Examples have two components:
 
* '''code''' – must compile and be delivered to the <span class="caps">SDK</span>. The ''.pro'' files must exist and <span class="caps">SDK</span> users must be able to compile them
* '''documentation''' – the documentation walks through the example code. This page is created by QDoc’s ''\example'' topic command


A brief list of the tasks:
Examples have two components:<br />* '''code''' - must compile and be delivered to the SDK. The ''.pro'' files must exist and SDK users must be able to compile them<br />* '''documentation''' - the documentation walks through the example code. This page is created by QDoc's '''' topic command


* Triage and sort the examples * current status: [http://community.kde.org/Qt5/Documentation/ExampleList Example List] ''[community.kde.org]''
A brief list of the tasks:<br />* Triage and sort the examples * - current status: &quot;Example List&amp;quot;:http://community.kde.org/Qt5/Documentation/ExampleList<br />* Fix the example code - the examples must be modularized and follow the [[Qt_Documentation_Structure | documentation structure]].
* Fix the example code the examples must be modularized and follow the [[Qt Documentation Structure|documentation structure]].
* Create the documentation page – the examples must be documented and walk through the example code. The [[Writing Qt Examples]] page contains information about proper style.

Revision as of 09:40, 24 February 2015

h1. The Qt 5 Documentation Renewal Project

We are working on restructuring and renewing and fixing the Qt Reference Documentation for the Qt 5 release. This consists of several parts:

  • API documentation: C++ API, QML API, and JavaScript related functions
  • Examples and example documentation: shows how the API are used
  • Overviews: explains the architecture and features of Qt

Changes from Qt 4 to Qt 5

Here is a brief summary of the important changes in the Qt 5 documentation:
* QDoc's binary is now qdoc whereas in Qt 4, the binary is called qdoc3
* The documentation is modularized. This means that the documentation for each module resides in their respective source directories. The directory doc/src is no longer used to contain overviews and API documentation
* The Qt modules will have their own pages and they may be treated as separate projects with different release schedules.

Important Resources

These are important resources for contributing to or working with the documentation.
* Adding Documentation to a New Module
* Qt Documentation Wiki - the main Documentation wiki which contains style information and contribution details
* "QDoc Manual&quot;:http://doc-snapshot.qt.io/qt5-stable/qdoc/qdoc-index.html - contains a guide to QDoc as well as information about C++ and QML commands
* Documentation Structure page contains a map of how the directory structure of a repository or module should be
* Building Qt Documentation - outlines how to build the documentation for Qt 5 and for each module
* Qt Writing Guidelines
* "http://doc-snapshot.qt.io/&quot;:http://doc-snapshot.qt.io/ - the documentation snapshot

API Documentation in Qt 5

Essentially, each module needs:
* landing page (using the command) see specifications
* example page
* c++ class list (using the command)
* qml type list (command)

To get started, the "QDoc Guide&quot;:http://doc-snapshot.qt.io/qdoc/qdoc-guide.html explains how QDoc generates documentation from QDoc comments.

Overview Documentation

Overviews describe a functionality, a group of APIs, and the technology in Qt. These overviews help developers decide which feature or API suits them best and helps them understand how the API cooperate within Qt and their applications.

For Qt 5, many of the overviews are being edited and rewritten for correctness and relevancy.

Example documentation

Examples have two components:
* code - must compile and be delivered to the SDK. The .pro files must exist and SDK users must be able to compile them
* documentation - the documentation walks through the example code. This page is created by QDoc's ' topic command

A brief list of the tasks:
* Triage and sort the examples * - current status: "Example List&quot;:http://community.kde.org/Qt5/Documentation/ExampleList
* Fix the example code - the examples must be modularized and follow the documentation structure.