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
103
104
105
106
107
108
109
110
111
112
113
114
115
|
/****************************************************************************
**
** Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/
**
** This file is part of the documentation of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:FDL$
** GNU Free Documentation License
** 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.
**
** Other Usage
** Alternatively, this file may be used in accordance with the terms
** and conditions contained in a signed written agreement between you
** and Nokia.
**
**
**
**
**
** $QT_END_LICENSE$
**
****************************************************************************/
/*!
\page qml-codingconventions.html
\title QML Coding Conventions
\brief code style convention
This document contains the QML coding conventions that we follow in our documentation and examples and recommend that others follow.
\section1 QML Object Declarations
Throughout our documentation and examples, \l{QML Object Attributes}{QML object attributes} are always structured in the following order:
\list
\li id
\li property declarations
\li signal declarations
\li JavaScript functions
\li object properties
\li child objects
\li states
\li transitions
\endlist
For better readability, we separate these different parts with an empty line.
For example, a hypothetical \e photo QML object would look like this:
\snippet qml/codingconventions/photo.qml 0
\section1 Grouped Properties
If using multiple properties from a group of properties,
consider using \e {group notation} instead of \e {dot notation} if it
improves readability.
For example, this:
\snippet qml/codingconventions/dotproperties.qml 0
could be written like this:
\snippet qml/codingconventions/dotproperties.qml 1
\section1 Lists
If a list contains only one element, we generally omit the square brackets.
For example, it is very common for a component to only have one state.
In this case, instead of:
\snippet qml/codingconventions/lists.qml 0
we will write this:
\snippet qml/codingconventions/lists.qml 1
\section1 JavaScript Code
If the script is a single expression, we recommend writing it inline:
\snippet qml/codingconventions/javascript.qml 0
If the script is only a couple of lines long, we generally use a block:
\snippet qml/codingconventions/javascript.qml 1
If the script is more than a couple of lines long or can be used by different objects, we recommend creating a function and calling it like this:
\snippet qml/codingconventions/javascript.qml 2
For long scripts, we will put the functions in their own JavaScript file and import it like this:
\snippet qml/codingconventions/javascript-imports.qml 0
*/
|
