blob: ab24e97fac5c5dc7ec2dca2205ab4e79132dbb45 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
// Copyright (C) 2021 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
// **********************************************************************
// 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 fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\previouspage accelbubble
\page creator-project-managing.html
\nextpage creator-project-creating.html
\title Managing Projects
\image front-projects.png
One of the major advantages of \QC is that it allows a team of designers and
developers to share a project across different development platforms with a
common tool for design, development, and debugging.
\list
\li \l{Creating Projects}
To set up a project, you first have to decide what kind of an
application you want to develop: do you want a user interface based
on Qt Quick or Qt widgets. Second, you have to choose the
language to implement the application logic: C++, JavaScript, or
Python.
\li \l{Using Version Control Systems}
The recommended way to set up a project is to use a version control
system. Store and edit only project source files and configuration
files. Do not store generated files.
\li \l{Configuring Projects}
Installation programs and project wizards create default
configurations for \QC and your projects. You can modify
the settings in the Projects mode.
\li \l{Managing Sessions}
Items such as open files, breakpoints, and evaluated expressions
are stored in sessions. They are not considered to be part of
the information shared across platforms.
\endlist
\section1 Related Topics
\list
\li \l{Build Systems}
\endlist
*/
|
