Commit dd4bd99c authored by Leena Miettinen's avatar Leena Miettinen

Doc: replace "element" with "QML type" or "item"

Try to make terminology more consistent, by using
"QML type" when describing the types, "item" when
describing instances of QML types, and "component"
when describing objects built by using QML types.

Change-Id: Ie03f3a7e6f483471e344ae1f35bec0742173b27c
Reviewed-by: default avatarJerome Pasion <jerome.pasion@digia.com>
Reviewed-by: default avatarThomas Hartmann <Thomas.Hartmann@digia.com>
parent 8c97b21e
......@@ -103,7 +103,7 @@
\li Compiling the QML sources
\li Creating elements
\li Creating items using QML types
\li Binding evaluations
......
......@@ -116,7 +116,7 @@
the \c text property to change it temporarily from \gui {Quit} to
\gui {End Game}.
When you select an element, the cursor moves to it in the code
When you select an item, the cursor moves to it in the code
editor, where you can change the value permanently.
\endlist
......
......@@ -172,29 +172,29 @@
\gui {Locals and Expressions} view, they are immediately updated in the running
application, but not in the source code.
\section1 Inspecting QML Objects
\section1 Inspecting Items
While the application is running, you can use the
\gui {Locals and Expressions} view to explore the QML object structure.
\gui {Locals and Expressions} view to explore the QML item structure.
\image qml-observer-view.png "QML object tree"
\image qml-observer-view.png "QML item tree"
To keep the application visible while you interact with the debugger, click
\inlineimage qml-inspector-app-on-top.png
(\gui {Show Application on Top}).
You can view a QML element in \gui {Locals and Expressions} in the following
You can view a QML item in \gui {Locals and Expressions} in the following
ways:
\list
\li Expand the element in the object tree.
\li Expand the item in the object tree.
\li Select the element in the code editor.
\li Select the item in the code editor.
\li Click
\inlineimage qml-inspector-select-button.png
(\gui Select) to activate selection mode and then click an element
(\gui Select) to activate selection mode and then click an item
in the running application.
\endlist
......@@ -206,16 +206,16 @@
\section1 Inspecting User Interfaces
When you debug complex applications, you can jump to the position in code
where an element is defined or you can zoom into the user interface.
where an item is defined or you can zoom into the user interface.
When the \gui Select tool is enabled, you can click elements in the running
When the \gui Select tool is enabled, you can click items in the running
application to jump to their definitions in the code. The properties of the
selected element are displayed in the \gui {Locals and Expressions} view.
selected item are displayed in the \gui {Locals and Expressions} view.
You can also right-click an element in the running application to view the
element hierarchy as a context menu.
You can also right-click an item in the running application to view the
item hierarchy as a context menu.
\image qml-observer-context-menu.png "QML element hierarchy"
\image qml-observer-context-menu.png "QML item hierarchy"
To switch to the zoom mode, click the \gui Zoom button. Click in the
running application to zoom in. Right-click to open a context menu that
......
......@@ -507,12 +507,12 @@
\row
\li M204
\li Warning
\li This type is not supported in the Qt Quick Designer
\li This QML type is not supported in the Qt Quick Designer
\li
\row
\li M205
\li Warning
\li Reference to parent item cannot be resolved correctly by the
\li Reference to parent QML type cannot be resolved correctly by the
Qt Quick Designer
\li
......@@ -526,7 +526,7 @@
\row
\li M207
\li Warning
\li Qt Quick Designer only supports states in the root item
\li Qt Quick Designer only supports states in the root QML type
\li
\row
......@@ -761,7 +761,7 @@
\li A C++ code snippet
\row
\li \inlineimage completion/element.png
\li A QML element
\li A QML type
\row
\li \inlineimage completion/qmlsnippet.png
\li A QML code snippet
......@@ -1492,7 +1492,7 @@
To apply refactoring actions to C++ code, right-click an operand,
conditional statement, string, or name to open a context menu. In QML code,
click an element ID or name.
click an item ID or name.
In the context menu, select \gui {Refactoring} and then select a refactoring
action.
......@@ -1877,7 +1877,7 @@
\li Split initializers
\li Move a QML element into a separate file to reuse it in other
\li Move a QML type into a separate file to reuse it in other
.qml files
\endlist
......@@ -1894,11 +1894,11 @@
\row
\li Move Component into 'filename.qml'
\li Moves a QML element into a separate file
\li Element name
\li Moves a QML type into a separate file
\li QML type name
\row
\li Split Initializer
\li Reformats a one-line element into a multi-line element. For example,
\li Reformats a one-line type into a multi-line type. For example,
rewrites
\code
Item { x: 10; y: 20; width: 10 }
......@@ -1913,12 +1913,12 @@
width: 10
}
\endcode
\li Element property
\li QML type property
\row
\li Wrap in Loader
\li Wraps the element in a Component element and loads it dynamically in
a Loader element. This is usually done to improve startup time.
\li Element name
\li Wraps the type in a Component type and loads it dynamically in
a Loader type. This is usually done to improve startup time.
\li QML type name
\row
\li Add a message suppression comment
\li Prepends the line with an annotation comment that stops the message
......
......@@ -127,7 +127,7 @@
\li \gui {Class View} shows the class hierarchy of the currently
open projects.
\li \gui Outline shows the symbol hierarchy of a C++ file and the element
\li \gui Outline shows the symbol hierarchy of a C++ file and the type
hierarchy of a QML file.
\li \gui {Type Hierarchy} shows the base classes of a class.
......@@ -209,16 +209,16 @@
\inlineimage qtcreator-show-subprojects.png
(\gui {Show Subprojects}).
\section2 Viewing QML Elements
\section2 Viewing QML Types
The \gui Outline view shows the element hierarchy in a QML file.
The \gui Outline view shows the type hierarchy in a QML file.
\list
\li To see a complete list of all bindings, select \gui {Filter Tree >
Show All Bindings}.
\li To keep the position in the view synchronized with the element
\li To keep the position in the view synchronized with the QML type
selected in the editor, select \gui {Synchronize with Editor}.
\endlist
......
......@@ -69,7 +69,7 @@
Button component to create Button objects. Alternatively, a
component may be defined inside a
\l{http://qt-project.org/doc/qt-5.0/qtqml/qml-qtquick2-component.html}
{Component} element.
{Component} QML type.
\row
\li Deploy configuration
......
......@@ -112,9 +112,9 @@
Qt 4.6.x
\endif
\li Qt Quick Application (Built-in Elements)
\li Qt Quick Application (Built-in Types)
Use built-in QML elements to design user interfaces based on
Use built-in QML types to design user interfaces based on
Qt Quick 1 (Qt 4.7.1, or later) or Qt Quick 2 (Qt 5) with a
custom look and feel and QML and C++ code to implement the
application logic
......@@ -279,7 +279,7 @@
\li Qt resource files, which allow you to store binary files in the
application executable
\li QML files, which specify elements in Qt Quick projects.
\li QML files, which specify items in Qt Quick projects.
\gui {Qt Quick 1} creates a QML file that imports Qt Quick 1.1 and
\gui {Qt Quick 2} creates a QML file that imports Qt Quick 2.0.
Select \gui {Qt Quick 1} to add files to a Qt Quick 1 application
......
......@@ -30,7 +30,7 @@
\title Creating a Qt Quick Application
This tutorial uses built-in QML elements and illustrates basic concepts of
This tutorial uses built-in QML types and illustrates basic concepts of
\l {http://qt-project.org/doc/qt-5.0/qtquick/qtquick-index.html}{Qt Quick}.
This tutorial describes how to use \QC to implement Qt states and transitions. We use
......@@ -48,11 +48,11 @@
\list 1
\li Select \gui{File > New File or Project > Applications >
Qt Quick 2 Application (Built-in Elements) > Choose}.
Qt Quick 2 Application (Built-in Types) > Choose}.
\note The QML types used in this example are also supported in Qt Quick 1. To create
this example application for platforms that run Qt 4, select \gui {Qt Quick 1
Application (Built-in Elements)}.
Application (Built-in Types)}.
\li In the \gui{Name} field, type \b {Transitions}.
......@@ -91,7 +91,7 @@
directory in the Qt installation directory. For example:
\c {C:\Qt\Qt5.0.1\5.0.1\msvc2010\examples\declarative\animation\states}. The image appears
in the \gui Resources pane. You can also use any other image or a QML
element, instead.
type, instead.
\list 1
......@@ -132,7 +132,7 @@
\endlist
\li In the \gui Library view, \gui Items tab, select \gui Rectangle,
\li In the \gui Library view, \gui {QML Types} tab, select \gui Rectangle,
drag and drop it to the canvas, and edit its properties.
\image qmldesigner-tutorial-topleftrect.png "Rectangle properties"
......@@ -174,10 +174,10 @@
\endlist
\li In the \gui Navigator pane, drag and drop the \gui {Mouse Area}
element from \e page to \e topLeftRect to make it apply only to the
from \e page to \e topLeftRect to make it apply only to the
rectangle and not to the whole page.
\li Edit \gui {Mouse Area} properties:
\li Edit the \gui {Mouse Area} properties:
\list a
......@@ -187,7 +187,7 @@
rectangle.
\li In the code editor, edit the pointer to the clicked expression
in the mouse area element, as illustrated by the following code
in the mouse area, as illustrated by the following code
snippet:
\qml
......@@ -208,7 +208,7 @@
\li In the \gui Navigator pane, copy topLeftRect (by pressing
\key {Ctrl+C}) and paste it to the canvas twice (by pressing
\key {Ctrl+V}). \QC renames the new instances of the element
\key {Ctrl+V}). \QC renames the new instances of the type
topLeftRect1 and topLeftRect2.
\li Select topLeftRect1 and edit its properties:
......@@ -225,7 +225,7 @@
for the vertical center anchor.
\li In the code editor,add a pointer to a clicked expression to the
mouse area element. The following expression sets the state to
mouse area. The following expression sets the state to
\e State1:
\c {onClicked: page.state = 'State1'}
......@@ -247,7 +247,7 @@
for the left anchor.
\li In the code editor, add a pointer to a clicked expression to the
mouse area element. The following expression sets the state to
mouse area. The following expression sets the state to
\e State2:
\c {onClicked: page.state = 'State2'}
......
......@@ -60,8 +60,8 @@
\endlist
\li Drag and drop a \gui {Text} item on top of the \gui Rectangle. This
creates a nested element where \gui Rectangle is the parent element
of \gui Text. Elements are positioned relative to their parents.
creates a nested item where \gui Rectangle is the parent item
of \gui Text. Items are positioned relative to their parents.
\li In the \gui Properties pane, edit the properties of the \gui Text
item.
......@@ -92,7 +92,7 @@
To create a graphical button that scales beautifully without using vector
graphics, use the \l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-borderimage.html}
{Border Image} element. For more information, see
{Border Image} type. For more information, see
\l{Creating Scalable Buttons and Borders}.
*/
......@@ -109,11 +109,11 @@
You can use the
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-borderimage.html}
{Border Image} element to display an image, such as a PNG file, as a border
{Border Image} type to display an image, such as a PNG file, as a border
and a background.
Use two Border Image elements and suitable graphics to make it look like the
button is pushed down when it is clicked. One of the Border Image elements
Use two Border Image items and suitable graphics to make it look like the
button is pushed down when it is clicked. One of the Border Image items
is visible by default. You can specify that it is hidden and the other one
becomes visible when the mouse is clicked.
......@@ -250,7 +250,7 @@
\endlist
\li In the code editor, add to the \c MouseArea item a pointer to the
\li In the code editor, add to the \c MouseArea a pointer to the
\c clicked expression that you added earlier:
\c {onClicked: parent.clicked()}.
......
......@@ -31,13 +31,13 @@
\title Creating Components
A \l{glossary-component}{component} provides a way of defining a new type
A \l{glossary-component}{component} provides a way of defining a new visual item
that you can re-use in other QML files. A component is like a black box; it
interacts with the outside world through properties, signals, and slots, and
is generally defined in its own QML file. You can import components to
screens and applications.
You can use the following QML elements to create components:
You can use the following QML types to create components:
\list
......@@ -49,9 +49,9 @@
adds a bitmap to the scene. You can stretch and tile images.
\li \l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-item.html}{Item}
is the most basic of all visual items in QML. Even though it has no
is the most basic of all visual types in QML. Even though it has no
visual appearance, it defines all the properties that are common
across visual items, such as the x and y position, width and height,
across visual types, such as the x and y position, width and height,
anchoring, and key handling.
\li \l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-rectangle.html}{Rectangle}
......@@ -73,7 +73,7 @@
\endlist
QML elements allow you to write cross-platform applications with custom look
QML types allow you to write cross-platform applications with custom look
and feel. You can also use ready-made Qt Quick Components that enable you to
create applications with a native look and feel for a particular target
platform. You can install the components as part of the Qt 4 SDK.
......@@ -97,11 +97,11 @@
\li Click \gui Design to open the .qml file in \QMLD.
\li Drag and drop an item from the \gui Library pane to the editor.
\li Drag and drop a QML type from the \gui Library pane to the editor.
\li Edit item properties in the \gui Properties pane.
\li Edit its properties in the \gui Properties pane.
The available properties depend on the item.
The available properties depend on the QML type.
\endlist
......
......@@ -43,9 +43,9 @@
QDeclarativeView. You can build the application and deploy it to
desktop and mobile target platforms.
You can select a template that uses either the built-in QML elements
You can select a template that uses either the built-in QML types
or Qt Quick components for a particular platform. The built-in QML
elements enable you to create cross-platform applications with a
types enable you to create cross-platform applications with a
custom look and feel, whereas the components provide the look and
feel for a particular platform.
......@@ -91,14 +91,14 @@
files in the project folder belong to the project. Therefore, you do
not need to individually list all the files in the project.
\li .qml file defines an element, such as a component, screen, or the
\li .qml file defines an UI item, such as a component, screen, or the
whole application UI.
\endlist
The \c import statement in the beginning of the .qml file specifies the Qt modules to
\l{http://qt-project.org/doc/qt-5.0/qtqml/qtqml-syntax-imports.html}{import}. Each Qt module
contains a set of default elements. Specify a version to get the features you want.
contains a set of default QML types. Specify a version to get the features you want.
To use JavaScript and image files in the application, copy them to the
project folder.
......@@ -106,9 +106,8 @@
\section1 Creating Qt Quick Applications
Select \gui File > \gui {New File or Project} > \gui Applications >
\gui {Qt Quick Application 1 (Built-in Elements)} or \gui {Qt Quick
Application 2 (Built-in Elements)} > \gui Choose, and follow the
instructions of the wizard.
\gui {Qt Quick Application 1 (Built-in Types)} or \gui {Qt Quick Application 2 (Built-in Types)}
> \gui Choose, and follow the instructions of the wizard.
\note The SDK for a particular target platform might install additional
templates for that platform. For example, the \gui {Qt Quick Application for
......
This diff is collapsed.
......@@ -33,8 +33,8 @@
You can export designs from graphics software, such as Adobe Photoshop and
GIMP, to QML files. Each scene is converted into a single QML file with an
Image or a Text element for each layer and saved on the development PC.
Top-level layer groups are converted into merged QML Image elements.
Image or a Text item for each layer and saved on the development PC.
Top-level layer groups are converted into merged QML Image types.
\note GIMP does not support grouping, and therefore, each layer is exported
as an item in GIMP.
......@@ -54,16 +54,16 @@
\list
\li Layer names are used as element names. Spaces and hash marks (#) are
\li Layer names are used as item names. Spaces and hash marks (#) are
replaced with underscore characters to create valid ids for the
elements.
items.
\li Layer styles, such as drop shadows, are converted to images.
\li Offset, size, ordering and opacity are preserved.
\li Text layers are converted to Text elements, unless you specify that
they be converted to Image elements.
\li Text layers are converted to Text items, unless you specify that
they be converted to Image items.
\li Hidden layers can be exported, and their visibility is set to
hidden.
......@@ -79,12 +79,12 @@
\list
\li To minimize the number of elements, minimize the number of layers or
\li To minimize the number of items, minimize the number of layers or
use top-level layer groups, because each layer or layer group is
exported as a Text or Image element.
exported as a Text or Image item.
\li To make sure that all related elements are exported to the same
element, use top-level layer groups.
\li To make sure that all related items are exported to the same
item, use top-level layer groups.
\li To determine that some layers are not exported, hide them, and
deselect the \gui {Export hidden} check box during exporting.
......@@ -133,10 +133,10 @@
location for the QML file.
\li Select the \gui {Rasterize text} check box to export text layers as
images, not as Text elements.
images, not as Text items.
\li Select the \gui {Group layers} check box to export each top-level
group as a merged QML Image element.
group as a merged QML Image item.
\li Select the \gui {Export hidden} check box to export hidden layers
and to set their visibility property to hidden.
......
......@@ -49,7 +49,7 @@
Ideally, QML modules have a \c{plugins.qmltypes} file in the same directory
as the \c qmldir file. The \c qmltypes file contains a description of the
components exported by the module's plugins and is loaded by \QC when the
types exported by the module's plugins and is loaded by \QC when the
module is imported.
For Qt 4.8 and later, one or more \c qmltypes files can be listed in the
......
......@@ -31,7 +31,7 @@
\title Creating Screens
You can use predefined QML elements and your own components to create
You can use predefined QML types and your own components to create
screens. Typically, the main qml file in a Qt Quick project specifies the
main window of an application.
......@@ -78,10 +78,10 @@
\endlist
When you add a Grid View, List View, or Path View element, the
When you add a Grid View, List View, or Path View, the
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-listmodel.html}{ListModel} and the
delegate component that creates an instance for each item in the model are
added automatically. You can edit element properties
added automatically. You can edit item properties
\if defined(qcmanual)
in the \gui Properties pane or
\endif
......@@ -90,7 +90,7 @@
\section1 Positioning Items on Screens
You can use the following items to arrange items on screens:
You can use the following QML types to arrange items on screens:
\list
......@@ -110,8 +110,8 @@
\endlist
\if defined(qcmanual)
To lay out several items in a Column, Row, Grid, or Flow element, select
the elements on the canvas, and then select \gui Layout in the context
To lay out several items in a Column, Row, Grid, or Flow, select
the items on the canvas, and then select \gui Layout in the context
menu.
\endif
......@@ -121,7 +121,7 @@
Use states and transitions to navigate between screens.
QML states typically describe user interface configurations, such as the UI
elements, their properties and behavior and the available actions. For
controls, their properties and behavior and the available actions. For
example, you can use states to create two screens.
\if defined(qcmanual)
......@@ -137,7 +137,7 @@
To keep the QML code clean, you should create a base state that contains all
the elements you will need in the application. You can then create states,
the types you will need in the application. You can then create states,
in which you hide and show a set of items and modify their properties.
This allows you to:
......@@ -146,7 +146,7 @@
\li Align items on different screens with each other.
\li Avoid excessive property changes. If an item is invisible in the
base state, you must define all changes to its child elements as
base state, you must define all changes to its child types as
property changes, which leads to complicated QML code.
\li Minimize the differences between the base state and the other states
......@@ -162,24 +162,24 @@
\list 1
\li In the base state, add all elements you will need in the
\li In the base state, add all items you will need in the
application (1).
While you work on one screen, you can click the
\inlineimage qmldesigner-show-hide-icon.png
icon to hide elements on the canvas that are not part of a screen.
icon to hide items on the canvas that are not part of a screen.
\li In the \gui States pane, click the empty slot to create a new state
and give it a name. For example, \c Normal.
\li In the \gui Properties pane (2), deselect the \gui Visibility check box
or set \gui Opacity to 0 for each element that is not needed in this
view. If you specify the setting for the parent element, all child
elements inherit it and are also hidden.
or set \gui Opacity to 0 for each item that is not needed in this
view. If you specify the setting for the parent item, all child
items inherit it and are also hidden.
\image qmldesigner-screen-design.png "Designing screens"
\li Create additional states for each screen and set the visibility
or opacity of the elements in the screen.
or opacity of the items in the screen.
\li To determine which view opens when the application starts, use the
code editor to set the state of the root item of the .qml file, as
......@@ -213,8 +213,8 @@
\l{http://qt-project.org/doc/qt-5.0/qtquick/qtquick-statesanimations-animations.html}
{Animation and Transitions in Qt Quick}.
You can use the \c ParallelAnimation element to start several animations at
the same time. Or use the \c SequentialAnimation element to run them one
You can use the \c ParallelAnimation type to start several animations at
the same time. Or use the \c SequentialAnimation type to run them one
after another.
You can use the code editor to specify transitions. For more information,
......
......@@ -30,12 +30,12 @@
\title Using Qt Quick Toolbars
When you select a component in the code and a toolbar is available,
When you select a QML type in the code and a toolbar is available,
a light bulb icon appears:
\inlineimage qml-toolbar-indicator.png
. Select the icon to open the toolbar.
To open toolbars immediately when you select a component, select
To open toolbars immediately when you select a QML type, select
\gui{Tools > Options > Qt Quick > Qt Quick Toolbar > Always show Qt Quick
Toolbar}.
......@@ -49,7 +49,7 @@
The Qt Quick Toolbar for images allows you to edit the properties of
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-borderimage.html}{Border Image}
and \l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-image.html}{Image} components.
and \l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-image.html}{Image} items.
You can scale and tile the images, replace them with other images,
preview them, and change the image margins.
......@@ -63,7 +63,7 @@
\section1 Formatting Text
The Qt Quick Toolbar for text allows you to edit the properties of
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-text.html}{Text} components.
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-text.html}{Text} items.
You can change the font family and size as well as text formatting, style,
alignment, and color.
......@@ -80,7 +80,7 @@
The Qt Quick Toolbar for animation allows you to edit the properties of
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-propertyanimation.html}
{PropertyAnimation} components and the components that inherit it. You can
{PropertyAnimation} items and the items that inherit it. You can
change the easing curve type and duration. For some curves, you can also
specify amplitude, period, and overshoot values.
......@@ -92,7 +92,7 @@
The Qt Quick Toolbar for rectangles allows you to edit the properties of
\l{http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-rectangle.html}{Rectangle}
components. You can change the fill and border colors and add
items. You can change the fill and border colors and add
gradients.
\image qml-toolbar-rectangle.png "Qt Quick Toolbar for rectangles"
......
......@@ -108,7 +108,7 @@ ItemLibraryWidget::ItemLibraryWidget(QWidget *parent) :
/* other widgets */
QTabBar *tabBar = new QTabBar(this);
tabBar->addTab(tr("Items", "Title of library items view"));
tabBar->addTab(tr("QML Types", "Title of library QML types view"));
tabBar->addTab(tr("Resources", "Title of library resources view"));
tabBar->setSizePolicy(QSizePolicy::Fixed, QSizePolicy::Fixed);
......
......@@ -141,18 +141,18 @@ void QtQuickAppWizard::createInstances(ExtensionSystem::IPlugin *plugin)
basicFeatures = Core::Feature(QtSupport::Constants::FEATURE_QT_QUICK_1);
parameter = base;
parameter.setDisplayName(tr("Qt Quick 1 Application (Built-in Elements)"));
parameter.setDescription(basicDescription + tr("The built-in elements in the QtQuick 1 namespace allow "
parameter.setDisplayName(tr("Qt Quick 1 Application (Built-in Types)"));
parameter.setDescription(basicDescription + tr("The built-in QML types in the QtQuick 1 namespace allow "
"you to write cross-platform applications with "
"a custom look and feel.\n\nRequires <b>Qt 4.7.0</b> or newer."));
parameter.setRequiredFeatures(basicFeatures);
list << parameter;
parameter = base;
parameter.setDisplayName(tr("Qt Quick 2 Application (Built-in Elements)"));
parameter.setDisplayName(tr("Qt Quick 2 Application (Built-in Types)"));
parameter.setDescription(tr("Creates a Qt Quick 2 application project that can contain "
"both QML and C++ code and includes a QQuickView.\n\n"
"The built-in elements in the QtQuick 2 namespace allow "
"The built-in QML types in the QtQuick 2 namespace allow "
"you to write cross-platform applications with "
"a custom look and feel.\n\nRequires <b>Qt 5.0</b> or newer."));
parameter.setRequiredFeatures(Core::Feature(QtSupport::Constants::FEATURE_QT_QUICK_2));
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment