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
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en_US" lang="en_US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- qmlbestpractices-coding.qdoc -->
<title>Qt 4.8: QML Best Practices: Coding Conventions</title>
<link rel="stylesheet" type="text/css" href="style/offline.css" />
</head>
<body>
<div class="header" id="qtdocheader">
<div class="content">
<a href="index.html" class="qtref"><span>Qt Reference Documentation</span></a>
</div>
<div class="breadcrumb toolblock">
<ul>
<li class="first"><a href="index.html">Home</a></li>
<!-- Breadcrumbs go here -->
<li>QML Best Practices: Coding Conventions</li>
</ul>
</div>
</div>
<div class="content mainContent">
<link rel="prev" href="qml-best-practices.html" />
<link rel="start" href="qml-best-practices.html" />
<p class="naviNextPrevious headerNavi">
<a class="prevPage" href="qml-best-practices.html">QML Best Practices Guides</a>
</p><p/>
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#coding-conventions">Coding Conventions</a></li>
<li class="level1"><a href="#importing-files-into-qml">Importing Files into QML</a></li>
<li class="level1"><a href="#commenting-code">Commenting Code</a></li>
<li class="level1"><a href="#group-properties">Group Properties</a></li>
</ul>
</div>
<h1 class="title">QML Best Practices: Coding Conventions</h1>
<span class="subtitle"></span>
<!-- $$$qml-best-practices-coding.html-description -->
<div class="descr"> <a name="details"></a>
<p>There are many different ways to code using QML. These are a set of guidelines to help your code look better and consistent.</p>
<a name="coding-conventions"></a>
<h2>Coding Conventions</h2>
<p>The official QML Coding Conventions may be found at <a href="qml-coding-conventions.html">QML Coding Conventions</a>. This is the recommended convention that will be used throughout the QML documentation.</p>
<p>In addition, Qt's official code style may be found at the <a href="http://qt.gitorious.org/qt/pages/QtCodingStyle">Qt Coding Style</a>.</p>
<a name="importing-files-into-qml"></a>
<h2>Importing Files into QML</h2>
<p>To import items such as directories, use the "import" keyword, similar to the way the <tt>import QtQuick 1.0</tt> statement is used.</p>
<pre class="qml"> import QtQuick 1.0
import QtWebKit 1.0
import "subdirectory"
import "script.js"</pre>
<p>To facilitate the import of QML components, it is best to begin the QML file with an uppercase character. This way, the user can simply declare the component using the file name as the component name. For example, if a QML component is in a file named <tt>Button.qml</tt>, then the user may import the component by declaring a <tt>Button {}</tt>. Note that this method only works if the QML files are in the same directory.</p>
<p>It is also possible to import QML files which have file names that begin in lower case or files in a different directory by using a <tt>qmldir</tt> file.</p>
<p>A <tt>qmldir</tt> file tells your QML application which QML components, plugins, or directories to import. The <tt>qmldir</tt> file must reside in an imported directory. By using the <tt>qmldir</tt> file, users may import any QML file and assign any valid QML component name to the component.</p>
<p>For more information, read the section on <a href="qmlreusablecomponents.html#qml-loading-components">Loading a Component</a>.</p>
<a name="commenting-code"></a>
<h2>Commenting Code</h2>
<p>Commenting code allows others to read the source code better. As well, comments allow the programmer to think about his or her code; a confusing comment may mean the code is confusing.</p>
<p>Similar to JavaScript or C++, there are two ways of commenting QML code:</p>
<ul>
<li>Single line comments start with <tt>//</tt> and finish at the end of the line</li>
<li>Multiline comments start with <tt>/*</tt> and finish with */</li>
</ul>
<a name="group-properties"></a>
<h2>Group Properties</h2>
<p>Many QML properties are <a href="propertybinding.html#attached-properties">attached</a> or <a href="propertybinding.html#qml-grouped-properties">group</a> properties. For convenience, you may treat them as another element when dealing with multiple properties belonging to the same group.</p>
<pre class="qml"> <span class="name">border</span>.width: <span class="number">1</span>
<span class="name">border</span>.color: <span class="string">"red"</span>
<span class="name">anchors</span>.bottom: <span class="name">parent</span>.<span class="name">bottom</span>
<span class="name">anchors</span>.left: <span class="name">parent</span>.<span class="name">left</span></pre>
<p>Treating groups of properties as a block can ease confusion and help relate the properties with other properties.</p>
<pre class="qml"> <span class="type">border</span> {
<span class="name">width</span>: <span class="number">1</span>;
<span class="name">color</span>: <span class="string">"red"</span>
}
<span class="type">anchors</span> {
<span class="name">bottom</span>: <span class="name">parent</span>.<span class="name">bottom</span>;
<span class="name">left</span>: <span class="name">parent</span>.<span class="name">left</span>
}</pre>
</div>
<!-- @@@qml-best-practices-coding.html -->
<p class="naviNextPrevious footerNavi">
<a class="prevPage" href="qml-best-practices.html">QML Best Practices Guides</a>
</p>
<div class="ft">
<span></span>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2012 Nokia Corporation and/or its
subsidiaries. Documentation contributions included herein are the copyrights of
their respective owners.</p>
<br />
<p>
The documentation provided herein is licensed under the terms of the
<a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation
License version 1.3</a> as published by the Free Software Foundation.</p>
<p>
Documentation sources may be obtained from <a href="http://www.qt-project.org">
www.qt-project.org</a>.</p>
<br />
<p>
Nokia, Qt and their respective logos are trademarks of Nokia Corporation
in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. <a title="Privacy Policy"
href="http://en.gitorious.org/privacy_policy/">Privacy Policy</a></p>
</div>
</body>
</html>
|
