Developing Qt: Difference between revisions
Jump to navigation
Jump to search
(→Coding Guidelines: Link to Writing Unit Tests) |
(Revert my previous; Writing Unit Tests was already there, under another heading.) |
||
| Line 35: | Line 35: | ||
* [[API Design Principles]] | * [[API Design Principles]] | ||
* [[Binary Compatibility Workarounds]] | * [[Binary Compatibility Workarounds]] | ||
* [[Branch Guidelines]] | * [[Branch Guidelines]] | ||
* [[Qt Localization]] | * [[Qt Localization]] | ||
Revision as of 11:19, 15 September 2016
Developing Qt
The Qt Project is a meritocratic consensus-based community interested in Qt. Anyone who shares that interest can join the community, participate in its decision making processes, and contribute to Qt’s development.
This wiki holds guidelines and documentation regarding code contributions to Qt. For an overview over all different ways to contribute to the Qt Project, please take a look at our "home page":http://qt.io.
Contributions
Things you generally need to know if you want to participate with code contributions.
- The Qt Governance Model
- Maintainers
- Qt Contribution Guidelines
- Contributing and Reviewing Code
- Commit Policy
- Reference Documentation
- Qt Framework
- Qt Creator
- Creating New Modules or Tools for Qt
- QtWebKit
Coding Guidelines
Things you need to know before you start writing Qt code.
- Qt Framework Qt_Coding_Style and Coding Conventions
- Qt Creator Coding Style & Conventions
- API Design Principles
- Binary Compatibility Workarounds
- Branch Guidelines
- Qt Localization
- Qt in Namespace
- Transition from Qt 4.x to Qt5
- Creating a new module or tool for Qt
- Project playground
- Naming guidelines
- Module repository structure
Tooling
Things you need to know before you submit your code.
Tools to help development of your code.
Quality Engineering
Things you need to know to ensure good code quality.
Related Articles
- Git Installation
- Get the source
- Building Qt 5 from Git
- Developing and maintaining patches on top of Qt with Git