aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/doc.pri2
-rw-r--r--doc/neptune3ui-project.qdocconf2
-rw-r--r--doc/src/examples-parking-app-tutorial.qdoc52
-rw-r--r--doc/src/neptune3ui-3d-integration.qdoc2
-rw-r--r--doc/src/neptune3ui-companion-app.qdoc2
-rw-r--r--doc/src/neptune3ui-configure.qdoc4
-rw-r--r--doc/src/neptune3ui-external-pages.qdoc42
-rw-r--r--doc/src/neptune3ui-install.qdoc18
-rw-r--r--doc/src/neptune3ui-middleware.qdoc18
-rw-r--r--doc/src/neptune3ui-overview.qdoc10
-rw-r--r--doc/src/neptune3ui-qt-safe-renderer-integration.qdoc4
-rw-r--r--doc/src/neptune3ui-system-dialog.qdoc2
-rw-r--r--doc/src/neptune3ui-toc.qdoc2
13 files changed, 78 insertions, 82 deletions
diff --git a/doc/doc.pri b/doc/doc.pri
index a1708b71..8e4e7f10 100644
--- a/doc/doc.pri
+++ b/doc/doc.pri
@@ -1,5 +1,5 @@
CONFIG += force_qt
-QT *= quick ivicore
+QT *= quick interfaceframework
INCLUDEPATH += $$OUT_PWD/../src/remotesettings/frontend \
$$OUT_PWD/../src/drivedata/frontend \
diff --git a/doc/neptune3ui-project.qdocconf b/doc/neptune3ui-project.qdocconf
index 53f19f0e..b118e0e4 100644
--- a/doc/neptune3ui-project.qdocconf
+++ b/doc/neptune3ui-project.qdocconf
@@ -24,7 +24,7 @@ depends += qtcore \
qtquick \
qtqml \
qtgui \
- qtivi \
+ interfaceframework \
applicationmanager \
qt3d \
qt3dstudio \
diff --git a/doc/src/examples-parking-app-tutorial.qdoc b/doc/src/examples-parking-app-tutorial.qdoc
index 71a64273..c2d6ef44 100644
--- a/doc/src/examples-parking-app-tutorial.qdoc
+++ b/doc/src/examples-parking-app-tutorial.qdoc
@@ -256,19 +256,19 @@ simulation which shows the number of parking lots currently available.
While this chapter does introduce the Middleware integration, how it works, and what needs to be
done to package it correctly, a full deep dive is out of scope. For more in-depth details on
-how to develop Middleware APIs, refer to the \l{Qt IVI Generator Tutorial}.
+how to develop Middleware APIs, refer to the \l{Qt Interface Framework Generator Tutorial}.
\note This application requires a multi-process environment.
\section2 Define the Middleware API
-To define our Middleware API, we use the IVI Generator from the QtIvi module. This generator uses
+To define our Middleware API, we use the generator from the QtInterfaceFramework module. This generator uses
an Interface Definition Language (IDL) to generate code, significantly reducing the amount of code
we need to write.
\section3 QFace
-QtIvi uses the QFace IDL to describe what needs to be generated. For this example, we define a
+QtInterfaceFramework uses the QFace IDL to describe what needs to be generated. For this example, we define a
simple interface, \c ParkingInfo, that provides a \c readonly property called \c freeLots, inside
a \c Parking module.
@@ -277,27 +277,27 @@ a \c Parking module.
\section2 Autogeneration
Now that the first version of our IDL file is ready, it's time to autogenerate API from it with
-the \l{IVI Generator} tool. Similar to \l moc, this autogeneration process is integrated into the
+the \l{Qt Interface Framework Generator} tool. Similar to \l moc, this autogeneration process is integrated into the
\l qmake Build System and is done at compile time.
In the following \c{.pro} file, we build a C++ library based on our IDL file:
\quotefile ../examples/neptune3ui/parking-app-tutorial/chapter3-middleware/frontend/frontend.pro
-By adding \c ivigenerator to the \c CONFIG variable, qmake's IVI Generator integration is loaded
-and it expects a QFace IDL file in the \C QFACE_SOURCES variable. The set \c DEFINE makes sure
+By adding \c ifcodegen to the \c CONFIG variable, qmake's Interface Framework Generator integration is loaded
+and it expects a QFace IDL file in the \C IFCODEGEN_SOURCES variable. The set \c DEFINE makes sure
that the library exports its symbols, which is necessary for Windows systems.
\section2 Which Files are Autogenerated
-The IVI Generator works based on generation templates -- these define what content should be
-generated from a QFace file. If no \c QFACE_FORMAT is defined, then the default template,
+The Interface Framework Generator works based on generation templates -- these define what content should be
+generated from a QFace file. If no \c IFCODEGEN_TEMPLATE is defined, then the default template,
\c frontend is used. For more details on these templates, see \l{Use the Generator}.
This \c frontend template generates:
\list
- \li a C++ class derived from QIviAbstractFeature for every interface in the QFace file
+ \li a C++ class derived from QIfAbstractFeature for every interface in the QFace file
\li one module class that helps to register all interfaces to QML and stores global types
and functions
\endlist
@@ -309,14 +309,14 @@ These files are available in your library's build folder, should you wish to ins
In addition to the library that contains our Middleware API, we also need a QML plugin to be able
to use the API from within QML.
-The IVI Generator can help us generate such a plugin with a different generation template. The
+The Interface Framework Generator can help us generate such a plugin with a different generation template. The
following \c{.pro} file generates a QML plugin that exports the API to QML:
\quotefile ../examples/neptune3ui/parking-app-tutorial/chapter3-middleware/imports/imports.pro
We use \c CONFIG to build a plugin, then define the settings for the linker to link against our
-frontend library. Next, we use \c QFACE_FORMAT to choose \c qmlplugin as the generation template.
-Instead of adding \c ivigenerator to the \c CONFIG, this time we use \l{https://doc.qt.io/qt-5/qmake-test-function-reference.html#load-feature} {qmake's load() function} to explicitly load the
+frontend library. Next, we use \c IFCODEGEN_TEMPLATE to choose \c qmlplugin as the generation template.
+Instead of adding \c ifcodegen to the \c CONFIG, this time we use \l{https://doc.qt.io/qt-5/qmake-test-function-reference.html#load-feature} {qmake's load() function} to explicitly load the
feature. This way, we can use the \c URI variable, that's part of the \c qmlplugin generation
template. This variable can define a \c DESTDIR by repliacing all dots with slashes.
@@ -324,7 +324,7 @@ In addition to the folder structure, the QmlEngine also needs a \c qmldir file w
what files are part of the plugin, and under which \c URI. For more information, see
\l{https://doc.qt.io/qt-5/qtqml-modules-qmldir.html}{Module Definition qmldir Files}.
-Both -- the \c qmldir file and the \c plugins.qmltypes file -- are autogenerated by the IVI
+Both -- the \c qmldir file and the \c plugins.qmltypes file -- are autogenerated by the Interface Framework
Generator and provide information about code-completion; but they need to be placed next to
the library. To do so, we add these files to a scope similar to an \c INSTALL target, but add it
to the \c COPIES variable instead. This makes sure that the files are copied when the plugin is
@@ -396,16 +396,16 @@ With those settings in place, the app can be deployed. It should show \c 0 free
\section2 Define a Simulation Behavior
-To simulate some values for our Middleware API, first we need to understand QtIvi's architecture a
-little bit better. As we learned when generating the library, the IVI Generator used a template
+To simulate some values for our Middleware API, first we need to understand QtInterfaceFramework's architecture a
+little bit better. As we learned when generating the library, the Interface Framework Generator used a template
called \c frontend. To define some simulation values or to connect to a real API, we also need
-corresponding \c backend. This \c backend is provided in the form of a plugin, and QtIvi takes care
+corresponding \c backend. This \c backend is provided in the form of a plugin, and QtInterfaceFramework takes care
to load and connect the \c frontend to the \c backend. For more information on this concept, see
\l{Dynamic Backend Architecture}.
\section2 Backend Plugin with Static Values
-The next step is to generate such a backend using the IVI Generator and use \l{Annotations} to
+The next step is to generate such a backend using the Interface Framework Generator and use \l{Annotations} to
define what the simulation should do.
Let's start with the \c{.pro} to generate and build our backend:
@@ -413,10 +413,10 @@ Let's start with the \c{.pro} to generate and build our backend:
\quotefile ../examples/neptune3ui/parking-app-tutorial/chapter3-middleware/backend_simulator/backend_simulator.pro
To build a plugin, we need to add \c plugin to the \c CONFIG variable as well as change the
-\c QFACE_FORMAT to use the \c backend_simulator generation template. Similar to the QML plugin,
+\c IFCODEGEN_TEMPLATE to use the \c backend_simulator generation template. Similar to the QML plugin,
the backend also needs to link to our frontend library, since it uses the types defined there.
-TO ensure that QtIvi can find the backend, it needs to be placed in a \c qtivi folder. In turn,
+TO ensure that QtInterfaceFramework can find the backend, it needs to be placed in a \c interfaceframework folder. In turn,
this folder needs to be part of the Qt plugin search path.
Just like with the import path, the additional plugin path needs to be setup in the package
@@ -427,7 +427,7 @@ manifest:
pluginPaths: [ '.' ]
\endcode
-Now, we have created a simulation backend, but without additional information, the IVI Generator
+Now, we have created a simulation backend, but without additional information, the Interface Framework Generator
can't create something really useful.
First, we define a static default value which the simulation backend should provide. The easiest
@@ -440,7 +440,7 @@ a default value we change the IDL file like this:
\printuntil }
\printuntil }
-Because of the change to the IDL file, the IVI Generator now recreates the backend plugin. Now,
+Because of the change to the IDL file, the Interface Framework Generator now recreates the backend plugin. Now,
when we run the updated application, we should see \c 42 free parking lots.
\section2 Simulation QML
@@ -450,7 +450,7 @@ having a generated simulation backend can do more. It would also allow you to de
behavior that's more dynamic.
To achieve this, we add another annotation to our QFace IDL file and define a \c simulationFile.
-This file contains our simulation behavior and QIviSimulationEngine loads it. Similar to other QML
+This file contains our simulation behavior and QIfSimulationEngine loads it. Similar to other QML
files, the best way to serve this file is to embed it inside a Qt resource.
Our \c simulation.qml looks like this:
@@ -460,8 +460,8 @@ Our \c simulation.qml looks like this:
\printuntil } } } }
First, there's a \c settings property, that's initialized with the return value from the
-\l{IviSimulator::findData}{IviSimulator.findData} method, which takes the
-\l{IviSimulator::simulationData}{IviSimulator.simulationData} and a string as input. The
+\l{IfSimulator::findData}{IfSimulator.findData} method, which takes the
+\l{IfSimulator::simulationData}{IfSimulator.simulationData} and a string as input. The
\c simulationData is the JSON file represented as a JavaScript object.
The \c findData method helps us to extract only data that is of interest for this interface,
@@ -477,9 +477,9 @@ also writable to make it possible to change them to provide a useful simulation.
Each time a frontend instance connects to a backend, the \c initialize() function is called.
The same applies to the QML simulation: as the \c initialize() C++ function forwards this to the
QML insitance. This behavior also applies to all other functions, like getters and setters.
-For more details, see \l{QIviSimulationEngine}.
+For more details, see \l{QIfSimulationEngine}.
-Inside the QML \c initialize() function, we call \c{IviSimulator.initializeDefault()}, to read
+Inside the QML \c initialize() function, we call \c{IfSimulator.initializeDefault()}, to read
the default values from the \c simulationData object and iniitialize all properties. This is done
only \b once, as we don't want the properties to be reset to default when the next frontend
instance connects to the backend. Lastly, the base implementation is called to make sure that the
diff --git a/doc/src/neptune3ui-3d-integration.qdoc b/doc/src/neptune3ui-3d-integration.qdoc
index 997f387b..870e3878 100644
--- a/doc/src/neptune3ui-3d-integration.qdoc
+++ b/doc/src/neptune3ui-3d-integration.qdoc
@@ -191,7 +191,7 @@
\li Clone the Qt 3D Studio runtime git repository from
\l{https://code.qt.io/cgit/qt3dstudio/qt3d-runtime.git/}
\li Next, build and install the Qt 3D Studio runtime from the branch 2.1.
- \li Finally, build and install \l{Qt Application Manager}, \l{Qt IVI} and then
+ \li Finally, build and install \l{Qt Application Manager}, \l{Qt Interface Framework} and then
\l{Neptune 3 UI} as explained in the Installation sections of those components.
\endlist
diff --git a/doc/src/neptune3ui-companion-app.qdoc b/doc/src/neptune3ui-companion-app.qdoc
index 17051af5..9c8339f8 100644
--- a/doc/src/neptune3ui-companion-app.qdoc
+++ b/doc/src/neptune3ui-companion-app.qdoc
@@ -39,7 +39,7 @@
changing the instrument cluster values, for demonstration or testing purposes.
The app connects to the same remote middleware services and utilizes the same autogenerated
- QtIVI interfaces and mechanisms; just like Neptune 3 UI. This solution simplifies the task of
+ QtInterfaceFramework interfaces and mechanisms; just like Neptune 3 UI. This solution simplifies the task of
implementing this kind of app, without requiring separate APIs and a dedicated architecture to
access vehicle function data.
diff --git a/doc/src/neptune3ui-configure.qdoc b/doc/src/neptune3ui-configure.qdoc
index ebdeda74..bfd38ea6 100644
--- a/doc/src/neptune3ui-configure.qdoc
+++ b/doc/src/neptune3ui-configure.qdoc
@@ -128,10 +128,6 @@
in Neptune 3 UI. When enabled, the Sheets app is included in the Application Launcher and
developers can see all of the components that Neptune 3 UI supports, to develop an app.
- The \c enableCursorManagement option can be set to \c yes or \c no, to enable or disable the
- Cursor Support in Neptune 3 UI's Center Console only. When enabled, it's possible to navigate
- the Center Console with input methods other than touch, such as a keyboard or a gamepad.
-
The \c hardwareVariant parameter can be used to specify the type of hardware used. According to
the variant, features are enabled or disabled depending on whether the hardware supports them.
Currently, this parameter accepts two values: \c high or \c low. If set to \c low, some
diff --git a/doc/src/neptune3ui-external-pages.qdoc b/doc/src/neptune3ui-external-pages.qdoc
index 1d8cf7dd..bf018955 100644
--- a/doc/src/neptune3ui-external-pages.qdoc
+++ b/doc/src/neptune3ui-external-pages.qdoc
@@ -27,12 +27,12 @@
****************************************************************************/
/*!
- \externalpage http://www.qt.io/qt-automotive-suite/
+ \externalpage https://www.qt.io/qt-automotive-suite/
\title Qt Automotive Suite Product
*/
/*!
- \externalpage http://doc.qt.io/QtAutomotiveSuite/
+ \externalpage https://doc.qt.io/QtAutomotiveSuite/
\title Qt Automotive Suite
*/
@@ -52,18 +52,18 @@
*/
/*!
- \externalpage http://doc.qt.io/QtApplicationManager/manifest.html
+ \externalpage https://doc.qt.io/QtApplicationManager/manifest.html
\title Qt Application Manager Manifest File
*/
/*!
- \externalpage http://doc.qt.io/QtApplicationManager/qml-qtapplicationmanager-notification.html
+ \externalpage https://doc.qt.io/QtApplicationManager/qml-qtapplicationmanager-notification.html
\title Notification
*/
/*!
- \externalpage https://doc.qt.io/QtIVI/index.html
- \title Qt IVI
+ \externalpage https://doc.qt.io/QtInterfaceFramework/index.html
+ \title Qt InterfaceFramework
*/
/*!
@@ -72,52 +72,52 @@
*/
/*!
- \externalpage http://doc.qt.io/QtForDeviceCreation/qtee-custom-embedded-linux-image.html
+ \externalpage https://doc.qt.io/QtForDeviceCreation/qtee-custom-embedded-linux-image.html
\title Building eLinux Image
*/
/*!
- \externalpage http://doc.qt.io/QtForDeviceCreation/qtee-requirements-x11.html#requirements-for-boot-to-qt-emulator
+ \externalpage https://doc.qt.io/QtForDeviceCreation/qtee-requirements-x11.html#requirements-for-boot-to-qt-emulator
\title Emulator Requirements for Linux/x11
*/
/*!
- \externalpage http://doc.qt.io/QtForDeviceCreation/qtee-requirements-windows.html#requirements-for-boot-to-qt-emulator
+ \externalpage https://doc.qt.io/QtForDeviceCreation/qtee-requirements-windows.html#requirements-for-boot-to-qt-emulator
\title Emulator Requirements for Windows
*/
/*!
- \externalpage http://doc.qt.io/qt-5/qtquickcontrols2-environment.html
+ \externalpage https://doc.qt.io/qt-5/qtquickcontrols2-environment.html
\title Qt QuickControls 2 Environment Variables
*/
/*!
- \externalpage http://code.qt.io/cgit/qt/qtapplicationmanager.git/
+ \externalpage https://code.qt.io/cgit/qt/qtapplicationmanager.git/
\title Qt Application Manager Git Repository
*/
/*!
- \externalpage http://code.qt.io/cgit/qt/qtivi.git/
- \title Qt IVI Git Repository
+ \externalpage https://code.qt.io/cgit/qt/qtinterfaceframework.git/
+ \title Qt InterfaceFramework Git Repository
*/
/*!
- \externalpage http://code.qt.io/cgit/qt-apps/neptune3-ui.git/
+ \externalpage https://code.qt.io/cgit/qt-apps/neptune3-ui.git/
\title Neptune3-UI Git Repository
*/
/*!
- \externalpage http://developer.gnome.org/notification-spec/
+ \externalpage https://developer.gnome.org/notification-spec/
\title GNOME Desktop Notifications Specification
*/
/*!
- \externalpage http://doc.qt.io/qtcreator/creator-project-qmake.html
+ \externalpage https://doc.qt.io/qtcreator/creator-project-qmake.html
\title Create Project Qmake
*/
/*!
- \externalpage http://doc.qt.io/qtcreator/creator-build-settings.html#build-steps
+ \externalpage https://doc.qt.io/qtcreator/creator-build-settings.html#build-steps
\title Build Steps
*/
@@ -142,13 +142,13 @@
*/
/*!
- \externalpage http://doc.qt.io/QtIVI/ipc-integration.html
- \title Qt IVI Inter-Process Communication Integration
+ \externalpage https://doc.qt.io/QtInterfaceFramework/ipc-integration.html
+ \title Qt InterfaceFramework Inter-Process Communication Integration
*/
/*!
- \externalpage http://doc.qt.io/QtIVI/qtivi-ivicore-qface-ivi-remote-example.html
- \title Qt IVI Generator Remote Objects Example
+ \externalpage https://doc.qt.io/QtInterfaceFramework/qtinterfaceframework-interfaceframework-qface-remote-example.html
+ \title Qt InterfaceFramework Generator Remote Objects Example
*/
/*!
diff --git a/doc/src/neptune3ui-install.qdoc b/doc/src/neptune3ui-install.qdoc
index 515bc74d..23677632 100644
--- a/doc/src/neptune3ui-install.qdoc
+++ b/doc/src/neptune3ui-install.qdoc
@@ -43,9 +43,9 @@
\section1 Run Neptune 3 UI from a Qt Automotive Suite Installation
- Neptune 3 UI depends on \l{Qt Application Manager} and \l{Qt IVI} to provide support for both a
- Center Console display and an Instrument Cluster. It also uses the Qt IVI plugins and its
- \c ivigenerator to generate and access various services. Neptune 3 UI offers a multi-process
+ Neptune 3 UI depends on \l{Qt Application Manager} and \l{Qt InterfaceFramework} to provide support for both a
+ Center Console display and an Instrument Cluster. It also uses the Qt InterfaceFramework plugins and its
+ \c ifcodegen to generate and access various services. Neptune 3 UI offers a multi-process
application model using a central System UI and various apps. The System UI provides an
application launcher to start and stop apps; it also acts as a full-fledged compositor.
Additionally, the \l{Qt Creator Plugin for Qt Application Manager} lets you develop and deploy
@@ -101,7 +101,7 @@
\section2 Prerequisites
\list
- \li \b{Qt 5.12} or higher
+ \li \b{Qt 6.2.5} or higher
\li To support multi-process mode, your Qt installation must include the \c qtwayland
submodule, and be built with Open GL ES \c{(-opengl es2 -opengles3)}.
\endlist
@@ -109,8 +109,8 @@
\section2 Dependencies
\list
- \li \l{Qt Application Manager} 5.15
- \li \l{Qt IVI} 5.15
+ \li \l{Qt Application Manager} 6.2.5+
+ \li \l{Qt InterfaceFramework} 6.2.5+
\li \l{Qt Safe Renderer} 1.1 (optional)
\li \l{Qt 3D Studio} (optional)
\endlist
@@ -119,10 +119,10 @@
\list 1
\li Clone the repositories mentioned in \l{Install Qt Automotive Suite}.
- \li Build \l{Qt Application Manager} against Qt 5.15. For more detailed build
+ \li Build \l{Qt Application Manager} against Qt 6.2.5. For more detailed build
instructions, see \l{Qt Applicaton Manager Installation}.
- \li Build \l{Qt IVI} against Qt 5.15. For more detailed build instructions, see
- \l[QtIvi]{Installation}.
+ \li Build \l{Qt InterfaceFramework} against Qt 6.2.5. For more detailed build instructions, see
+ \l[QtInterfaceFramework]{Installation}.
\li Run the following command in a terminal, to build Neptune 3 UI:
\badcode
qmake neptune3-ui.pro
diff --git a/doc/src/neptune3ui-middleware.qdoc b/doc/src/neptune3ui-middleware.qdoc
index 9f07afd3..1df2ac08 100644
--- a/doc/src/neptune3ui-middleware.qdoc
+++ b/doc/src/neptune3ui-middleware.qdoc
@@ -30,14 +30,14 @@
\title Neptune 3 UI - Middleware
\brief Describes Neptune 3 UI's middleware implementation.
- Neptune 3 UI uses QtIvi, its autogenerator tools, QtIviVehicleFunctions, and QtIviMedia to
+ Neptune 3 UI uses QtInterfaceFramework, its autogenerator tools, QtIfVehicleFunctions, and QtIfMedia to
implement Middleware APIs in an automotive UI context. There are two such APIs that Neptune 3 UI
implements and utilizes: \c RemoteSettings and \c DriveData.
Neptune 3 UI connects to their corresponding remote services: \c remotesettings-server and the
\c drivedata-simulation-server. In this case, a remote service refers to an independent process,
- possibly running on a different host. For an introduction to QtIvi's middleware services, see
- \l {Qt IVI Inter-Process Communication Integration}.
+ possibly running on a different host. For an introduction to QtInterfaceFramework's middleware services, see
+ \l {Qt Interface Framework Inter-Process Communication Integration}.
\section1 Why use Middleware
@@ -67,13 +67,13 @@
\section1 Implementation
- The middleware architecture is based on QtIVI and its \l {Qt IVI Autogenerator}{ivigenerator}
+ The middleware architecture is based on QtInterfaceFramework and its \l {Qt Interface Framework Generator}{ifcodegen}
tool. Neptune 3 UI's built-in apps, the companion app, and System UI all connect to the remote
services through auto-generated components. Communication between the middleware services and
frontends is achieved with QtRemoteObjects. This is done transparently; you can replace this
communication with other messaging mechanisms, without changing the APIs.
- QtIvi-based middleware is described in \c{.qface} files; for each file, the QtIVI autogenerator
+ QtInterfaceFramework-based middleware is described in \c{.qface} files; for each file, the QtInterfaceFramework autogenerator
generates these distinct components: frontend, backend plugin, and a separate service
executable.
@@ -94,7 +94,7 @@
\endlist
As discussed above, the \b remotesettings.qface file is the interface description that the
- \c ivigenerator takes as input. The \b frontend is a shared library containing a C++
+ \c ifcodegen takes as input. The \b frontend is a shared library containing a C++
implementation of our middleware and the interface to implement a backend for it. Whether the
middleware service is remote or not, is hidden from the code that uses the frontend (opaque).
For example, all methods in the frontend's interface are asynchronous. For convenience, the
@@ -126,10 +126,10 @@
\section2 Related Information
\list
- \li See \l{Qt IVI Inter-Process Communication Integration} and
- \l {Generate QtRemoteObjects based backends with the Qt IVI Generator} for a more
+ \li See \l{Qt Interface Framework Inter-Process Communication Integration} and
+ \l {Generate QtRemoteObjects based backends with the Qt Interface Framework Generator} for a more
detailed explanation and a walkthrough on generating middleware services.
- \li See \l{Qt IVI Simulation System} for more info about simulations.
+ \li See \l{Qt Interface Framework Simulation System} for more info about simulations.
\li See \l{Develop a Parking App}
\endlist
diff --git a/doc/src/neptune3ui-overview.qdoc b/doc/src/neptune3ui-overview.qdoc
index 1045bc03..5508b10f 100644
--- a/doc/src/neptune3ui-overview.qdoc
+++ b/doc/src/neptune3ui-overview.qdoc
@@ -43,7 +43,7 @@
\li Provide UI designers with methods to control the look-and-feel.
\li Improve flexibility by enabling
\l{Qt Automotive Suite Product} {Qt Automotive Suite} to integrate with
- external tools, such as 3D tools, Maps, Qt IVI, and more.
+ external tools, such as 3D tools, Maps, Qt Interface Framework, and more.
\li Provide a multi-process UI that forms a base for an IVI system.
\endlist
@@ -56,7 +56,7 @@
takes care of the application and window management.
\li Can be integrated with various car 3D model technologies.
\li Can be integrated with various navigation solutions.
- \li Utilizes the \l{Qt IVI} module, that provides C++ classes and QML types
+ \li Utilizes the \l{Qt Interface Framework} module, that provides C++ classes and QML types
to access vehicle features, as well as a core API to implement new IVI
features.
\li Supports \l{Neptune 3 UI Cursor Management Support}{cursor management}
@@ -110,7 +110,7 @@
\row
\li Music App (\c musicapp)
\li A Media app that can play music that was previously indexed by
- \l{Qt IVI} using the Qt Multimedia backend.
+ \l{Qt Interface Framework} using the Qt Multimedia backend.
\row
\li \l{Neptune 3 UI - Maps App}{Maps App} (\c mapapp)
\li A Maps app that is created using the MapBoxGL plugin from Qt
@@ -131,7 +131,7 @@
\row
\li Tuner App (\c tunerapp)
\li A media app that has a pre-set station list, provided by the
- simulation backend from \l{Qt IVI}.
+ simulation backend from \l{Qt Interface Framework}.
\row
\li Downloads App (\c downloadsapp)
\li Allows the user to install apps from the Neptune Deployment Store
@@ -391,7 +391,7 @@
The Climate Bar is located at the bottom of the \l{Center Console Display}.
Tapping on it displays a climate panel with some simulation data interface
- to \l{Qt IVI} as shown in the following image:
+ to \l{Qt Interface Framework} as shown in the following image:
\image center-stack-climate.png
diff --git a/doc/src/neptune3ui-qt-safe-renderer-integration.qdoc b/doc/src/neptune3ui-qt-safe-renderer-integration.qdoc
index 2e1b4b89..49884dbe 100644
--- a/doc/src/neptune3ui-qt-safe-renderer-integration.qdoc
+++ b/doc/src/neptune3ui-qt-safe-renderer-integration.qdoc
@@ -62,7 +62,7 @@
The Client to Neptune's \l{Neptune 3 UI - Middleware}{Middleware} provides the value sources
for Safe UI: telltales state, speed, and so on. The \c neptune3-ui-qsr-cluster app connects to
- the same remote middleware services and utilizes the same autogenerated QtIVI interfaces and
+ the same remote middleware services and utilizes the same autogenerated QtInterfaceFramework interfaces and
mechanisms as Neptune 3 UI. The \c neptune3-ui-qsr-cluster app expects to find both services
running at the same address. By default, it assumes the \c {tcp://127.0.0.1} address, ports 9998
for the drivedata-simulation-server and 9999 for the remotesettings-server. To override these
@@ -199,7 +199,7 @@
and receiving notification that \c {Main UI} is about to shutdown. We use the simple Qt TCP
Server (\c TcpMsgHandler) for this.
\li Communicating with Neptune's \l {Neptune 3 UI - Middleware}
- {Middleware} to get values of Safe UI elements states. The same \l{Qt IVI} auto
+ {Middleware} to get values of Safe UI elements states. The same \l{Qt InterfaceFramework} auto
generated client is used as with Neptune's \l {Neptune 3 UI - Companion App}.
\endlist
diff --git a/doc/src/neptune3ui-system-dialog.qdoc b/doc/src/neptune3ui-system-dialog.qdoc
index 2a5ce418..fe70b990 100644
--- a/doc/src/neptune3ui-system-dialog.qdoc
+++ b/doc/src/neptune3ui-system-dialog.qdoc
@@ -47,7 +47,7 @@
resources as well)
\li Network (Internet Connection) Status
\li Connected Network Devices with all their address information
- \li Version: shows which Neptune 3 UI, Application Manager and Qt IVI versions are being
+ \li Version: shows which Neptune 3 UI, Application Manager and Qt Interface Framework versions are being
used
\li Platform: shows which operating system, Qt version, and OpenGL are being used.
\endlist
diff --git a/doc/src/neptune3ui-toc.qdoc b/doc/src/neptune3ui-toc.qdoc
index eb5d36a5..17866273 100644
--- a/doc/src/neptune3ui-toc.qdoc
+++ b/doc/src/neptune3ui-toc.qdoc
@@ -4,7 +4,7 @@
** Copyright (C) 2018 Pelagicore AG
** Contact: https://www.qt.io/licensing/
**
-** This file is part of the Neptune IVI UI.
+** This file is part of the Neptune 3 UI.
**
** $QT_BEGIN_LICENSE:FDL-QTAS$
** Commercial License Usage
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-09 19:10:26 +0000