creator-overview.qdoc 6.26 KB
Newer Older
1 2
3 4
** Copyright (C) 2016 The Qt Company Ltd.
** Contact:
** This file is part of the Qt Creator documentation.
8 9 10 11 12 13 14
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and The Qt Company. For licensing terms
** and conditions see For further
** information use the contact form at
** GNU Free Documentation License Usage
17 18
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
19 20 21 22
** Foundation and appearing in the file included in the packaging of
** this file. Please review the following information to ensure
** the GNU Free Documentation License version 1.3 requirements
** will be met:
23 24 25 26 27 28 29 30 31 32

// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the script to adjust the links to the index order.
// **********************************************************************

    \contentspage {Qt Creator Manual}
Oswald Buddenhagen's avatar
Oswald Buddenhagen committed
    \previouspage creator-getting-started.html
35 36 37 38 39 40 41 42
    \page creator-overview.html
    \nextpage creator-quick-tour.html

    \title IDE Overview

    \QC is an integrated development environment (IDE) that provides you with
    tools to design and develop applications with the Qt application framework.
    Qt is designed for developing applications and user interfaces once and
    deploying them to several desktop, embedded, and mobile operating systems. \QC
44 45
    provides you with tools for accomplishing your tasks throughout the whole
    application development life-cycle, from creating a project to deploying the
    application to the target platforms.

48 49
50 51 52
            \li \inlineimage creator_managingprojects.png
            \li \inlineimage creator_designinguserinterface.png
            \li \inlineimage creator_coding.png
            \li \b {\l{Managing Projects}}
55 56 57 58 59 60 61 62 63 64

                To be able to build and run applications, \QC needs the same
                information as a compiler would need. This information is
                specified in the project settings.

                Setting up a new project in \QC is aided by a wizard that guides
                you step-by-step through the project creation process, creates
                the necessary files, and specifies settings depending on the
                choices you make. For more information, see
                \l{Managing Projects}.
            \li \b {\l{Designing User Interfaces}}
66 67 68

                \QC provides two integrated visual editors, \QMLD and \QD.
                To create intuitive, modern-looking, fluid user interfaces, you
                can use \l{Qt Quick}.
70 71 72 73
                If you need a traditional user interface that is clearly
                structured and enforces a platform look and feel, you can use
                the integrated \QD. For more information, see
                \l{Designing User Interfaces}.
            \li \b {\l{Coding}}
75 76 77 78 79 80 81 82

                As an IDE, \QC differs from a text editor in that it knows how
                to build and run applications. It understands the C++ and QML
                languages as code, not just as plain text. This enables it to
                provide you with useful features, such as semantic highlighting,
                checking code syntax, code completion, and refactoring actions.
                For more information, see \l{Coding}.
83 84 85
            \li \inlineimage creator_buildingrunning.png
            \li \inlineimage creator_testing.png
            \li \inlineimage creator_publishing.png
            \li \b {\l{Building and Running}}
88 89

                \QC is integrated with cross-platform systems for build
90 91
                automation: qmake, Qbs, CMake, and Autotools. In addition, you
                can import
92 93 94
                projects as \e {generic projects} and fully control the steps
                and commands used to build the project.

95 96 97
                \QC provides support for running and deploying Qt applications
                built for the desktop environment as well as embedded and
                mobile devices. \l{glossary-buildandrun-kit}{Kits}, build,
                run, and deployment settings allow you to quickly switch between
                different setups and target platforms.
100 101

                For more information, see \l{Building and Running}.
            \li \b {\l{Testing}}
103 104 105

                \QC is integrated to several external native debuggers: GNU
                Symbolic Debugger (GDB), Microsoft Console Debugger (CDB), and
                internal JavaScript debugger. In the \uicontrol Debug mode, you
107 108 109 110 111 112 113 114
                can inspect the state of your application while debugging.

                The memory and CPU power available on devices are limited and
                you should use them carefully. \QC integrates Valgrind code
                analysis tools for detecting memory leaks and profiling function
                execution. In addition, the QML Profiler enables you to profile
                Qt Quick applications.

115 116 117
                \QC is integrated to the \l{Qt Test} and Google C++ Testing
                frameworks for unit testing applications and libraries. You can
                use \QC to build and run autotests.
118 119

                For more information, see \l{Testing}.
            \li \b {Publishing}
121 122 123

                \QC allows you to create installation packages for mobile
                devices that are suitable for publishing to application stores
124 125
                and other channels. You must make sure that the package contents
                meet the requirements for publishing on the channel.
126 127 128

                For more information, see \l{Publishing to Google Play}.
129 130