Qt
Internal/Contributor docs for the Qt SDK. Note: These are NOT official API docs; those are found at https://doc.qt.io/
Loading...
Searching...
No Matches
objecttypes.qdoc
Go to the documentation of this file.
1// Copyright (C) 2017 The Qt Company Ltd.
2// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
3/*!
4\page qtqml-typesystem-objecttypes.html
5\meta {keywords} {qmltopic}
6\title QML Object Types
7\brief describes QML object types and how to create them
8
9
10A QML object type is a type from which a QML object can be instantiated.
11
12In syntactic terms, a QML object type is one which can be used to declare an
13object by specifying the \e{type name} followed by a set of curly braces that
14encompasses the attributes of that object. This differs from \e {value types},
15which cannot be used in the same way. For example, \l Rectangle is a QML object
16type: it can be used to create \c Rectangle type objects. This cannot be done
17with primitive types such as \c int and \c bool, which are used to hold simple
18data types rather than objects.
19
20Custom QML object types can be defined by creating a .qml file that defines the
21type, as discussed in \l {qtqml-documents-definetypes.html}
22{Documents as QML object type definitions}, or by defining a QML type from C++
23and registering the type with the QML engine, as discussed in
24\l{qtqml-cppintegration-definetypes.html}{Defining QML Types from C++}.
25Note that in both cases, the type name must begin with an uppercase letter in
26order to be declared as a QML object type in a QML file.
27
28For more information about C++ and the different QML integration methods,
29see the
30\l {Overview - QML and C++ Integration} {C++ and QML integration overview} page.
31
32There are two built-in object types that can be used without importing any other
33modules: \l{QtObject} is the base type of all object types. \l{Component} can be
34used to define new object types inline in QML documents.
35
36\section1 Defining Object Types from QML
37
38
39\section2 Defining Object Types Through QML Documents
40
41Plugin writers and application developers may provide types defined as QML
42documents. A QML document, when visible to the QML import system, defines a
43type identified by the name of the file minus the file extensions.
44
45Thus, if a QML document named "MyButton.qml" exists, it provides the definition
46of the "MyButton" type, which may be used in a QML application.
47
48See the documentation about \l{QML Documents} for
49information on how to define a QML document, and the syntax of the QML
50language. Once you are familiar with the QML language and how to define QML
51documents, see the documentation which explains how to
52\l{qtqml-documents-definetypes.html}
53{define and use your own reusable QML types in QML documents}.
54
55See \l {Defining Object Types through QML Documents} for more information.
56
57
58
59\section2 Defining Anonymous Types with Component
60
61Another method of creating object types from within QML is to use the \l Component type.
62This allows a type to be defined inline within a QML document, instead of using a separate
63document in a \c .qml file.
64
65\qml
66Item {
67 id: root
68 width: 500; height: 500
69
70 Component {
71 id: myComponent
72 Rectangle { width: 100; height: 100; color: "red" }
73 }
74
75 Component.onCompleted: {
76 myComponent.createObject(root)
77 myComponent.createObject(root, {"x": 200})
78 }
79}
80\endqml
81
82Here the \c myComponent object essentially defines an anonymous type that can be instantiated
83using \l {Component::createObject} to create objects of this anonymous type.
84
85
86Inline components share all
87the characteristics of regular top-level components and use the same \c import
88list as their containing QML document.
89
90
91
92Note that each \l Component object declaration creates its own \e {component scope}. Any
93\e id values used and referred to from within a \l Component object declaration must be
94unique within that scope, but do not need to be unique within the document within which the
95inline component is declared. So, the \l Rectangle declared in the \c myComponent object
96declaration could have an \e id of \c root without conflicting with the \c root declared
97for the \l Item object in the same document, as these two \e id values are declared within
98different component scopes.
99
100See \l{qtqml-documents-scope.html}{Scope and Naming Resolution} for more details.
101
102
103\section1 Defining Object Types from C++
104
105C++ plugin writers and application developers may register types defined in C++
106through API provided by the Qt Qml module. There are various registration
107functions which each allow different use-cases to be fulfilled.
108For more information about those registration functions, and the specifics of
109exposing custom C++ types to QML, see the documentation regarding
110\l{qtqml-cppintegration-definetypes.html}{Defining QML Types from C++}.
111
112The QML type-system relies on imports, plugins and extensions being installed
113into a known import path. Plugins may be provided by third-party developers
114and reused by client application developers. Please see the documentation
115about \l{qtqml-modules-topic.html}{QML modules} for more information about
116how to create and deploy a QML extension module.
117
118*/