forked from qt-creator/qt-creator
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: Jerome Pasion <jerome.pasion@digia.com> Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
This commit is contained in:
@@ -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));
|
||||
|
||||
Reference in New Issue
Block a user