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
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
/****************************************************************************
**
** Copyright (C) 2021 The Qt Company Ltd.
** Contact: https://www.qt.io/licensing/
**
** This file is part of the Qt Design Studio documentation.
**
** 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 https://www.qt.io/terms-conditions. For further
** information use the contact form at https://www.qt.io/contact-us.
**
** GNU Free Documentation License Usage
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** 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: https://www.gnu.org/licenses/fdl-1.3.html.
**
****************************************************************************/
/*!
\previouspage qt-design-viewer.html
\page studio-advanced.html
\nextpage studio-platforms.html
\title Advanced Topics
\QDS attempts to meet your needs, whether you have previous experience with
QML and coding or not. When you install \QDS, the default configuration
allows you to start designing and previewing UIs with very little effort.
However, you might want to use the \l{Text Editor} view sometimes to edit
your component files (.qml) or write some JavaScript to simulate application
logic and bring your UI to life. If you use JavaScript, you might also want
to debug and profile you UIs to find and fix problems in them.
You can also use special options to start \QC from the command line and use
it mainly from the keyboard.
\list
\li \l{Supported Platforms}
You can install and run \QC on several operating systems to design
UIs for multiple desktop, embedded, and mobile device platforms.
\li \l{Keyboard Shortcuts}
\QDS provides various keyboard shortcuts to speed up your
development process. You can change the keyboard shortcuts,
as well as import and export keyboard shortcut mapping schemes.
\li \l{Coding}
You can use the code editor in the \uicontrol {Text Editor} view or
in the Edit mode to modify QML code. The code editor understands
the QML language 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.
\li \l{Simulating Data Input}
\QDS enables you to connect UIs to different forms of data from various
sources, such as QML-based data models, JavaScript files, and backend
services. You can also connect your UI to Simulink to load live data from a
Simulink simulation.
\li \l{Debugging and Profiling}
\QDS comes with a JavaScript debugger. In the Debug mode, you
can inspect the state of your UI while debugging.
The memory and CPU power available on devices are limited and
you should use them carefully. The QML Profiler enables you to
profile Qt Quick UIs.
\endlist
\section1 Related Topics
\list
\li \l{Using External Tools}
You can use external tools directly from \QC. lupdate and lrelease,
QML preview tools (QML Viewer and QML Scene), the default text
editor for your system, and the \c sort tool are preconfigured for
use. You can change their default configurations and configure new
tools.
\li \l{Managing Data Collection Settings}
\if defined (qtcreator)
You can enable \QC to report crashes automatically. If you agreed to
pseudonymous user statistics collection during the \QC installation,
you can turn it on and determine what type of data is collected and
transmitted to the backend storage.
\else
You can enable \QDS to report crashes automatically. If you enable
the telemetry plugin, you can turn on the pseudonymous user
statistics collection and determine what type of data is collected
and transmitted to the backend storage.
\endif
\endlist
*/
|
