| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I7d124886c71093d2fc8405a7ec4157464e3c3333
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Rerun pro2cmake.py for all examples and tests.
Ivigenerator based tests and examples are compiling
fine, but the cmake files need to be reworked to be
also able to run them.
Task-number: AUTOSUITE-1633
Change-Id: Icb95ecfa62ecb319d042dc30ea9f643b69a4aacf
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
| |
Also delete orphan pro file in one of the ivigenerator templates
Change-Id: I115ebe504344269c1554b6396df545467f5b0a59
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
| |
Some special cases are already addressed.
Task-number: AUTOSUITE-1633
Change-Id: I5409522c1c5eb76b8aac3e7e332d1e1cc27e594f
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
| |
Change-Id: I259eb331e0abdb80cc25a2f25c2130596393d37d
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|\
| |
| |
| | |
Change-Id: I0a79176763ca001072d41f377869854e1982e4e7
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Added a link to the Generator Tutorial to the front page
* Added a short paragraph about RPATH linking to the tutorial
* Fixed linking warnings
Change-Id: I085ddbe5c0e9939e2e22ae7188c307fae52f77b2
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|/
|
|
|
|
|
|
|
|
|
|
| |
The plugin class name is used to instantiate the plugin when used as
static plugin and also defines the name for the cmake files to include
those plugins.
Using the same name sometimes caused build errors when generating the
same cmake file.
Change-Id: I28e6b83148d14265fb74690d2b912628446301eb
Fixes: AUTOSUITE-1322
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
| |
This is needed for the plugins to find the frontend lib on the target
Change-Id: I6b83b5ac96b450f7a35b241b2f64275d2ff5dbc5
Fixes: AUTOSUITE-1250
Reviewed-by: Stanislav Maksimov <smaksimov@luxoft.com>
|
|
|
|
|
|
| |
Task-number: AUTOSUITE-1250
Change-Id: I6cbdc49fce071d4b5e5e415d313d3622362e47c8
Reviewed-by: Bernd Weimer <bernd.weimer@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
| |
* Add the missing gifs
* Don't create bundles on mac
* Signature fix for the dbus chapter
* Link to this tutorial instead of the Climate Example in some places
Change-Id: I1c1afd3c61a04f3eb040440816afc8c2abedc978
Reviewed-by: Kavindra Palaraja <kpalaraja@luxoft.com>
|
|
|
|
|
|
|
|
|
|
| |
The tutorial has multiple chapters and shows how to extend a
UI step-by-step with a Middleware API using the IVI Generator.
Fixes: AUTOSUITE-1155
Fixes: AUTOSUITE-600
Change-Id: Ib18de9e3d53d7163f880a2258173e0b6119ef3af
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Only the qface-ivi-addressbook example needed it for setting a specific
style. The default QQC2 platform style should be good enough for our
examples.
Change-Id: Ibec54f4f34ad5fb616589ade26e621d7dad38d8e
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default QtRemoteObjects always wants to return a result for
a function call right away. For function calls which take longer
this doesn't work very well as the Qt main event loop is blocked
until the result is ready and in the meantime no other communication
can take place.
This commit introduces a workaround for this limitation by
generating a interface specific PendingResult object which can
be returned as a placeholder to inform the client that the result
is not yet ready. The actual result is emitted by the server using
the pendingResultAvailable signal with the call-id and the result.
To also support returning the result right away the return value
always needs to be of type QVariant. This also has the good side
effect that the client side always gets informed of whether a
call has been finished or not as QtRemoteObjects doesn't provide
QRemoteObjectPendingReply<void> for this.
Change-Id: I68bf29b84b95042b69b5e1a18096f48ee9da7c7c
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to the frontend QML API, this adds the generation of a qmltypes
file for the simulation API, which can be used in the simulation engine.
Because QtCreator cannot handle the same import uris in different folder
we always need to generate the frontend qmltypes together with the
simulation qmltypes in one combined folder structure.
For now the qmltypes are moved into the common folder and generated
in the frontend and the backend_simulator template to make it easier
to include them.
Later the same files can be used for the qml_plugin generator.
Task-number: AUTOSUITE-743
Change-Id: I49aecf4d158fc46dbc1eac80c707194440c5763f
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
| |
By also using the qml_types filter here, we make sure that the uri for the simulation
is similar to the frontend API. (It just adds a extra .simulation at the end).
Also juse the qface module version in the autogenerated QML API
Change-Id: I4804302a18f7af93345a905c79dd86b00c77702b
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of registering the QML types with a custom uri, we now
just use the default argument of the type registration and by
that make sure that the types are registered with the same uri
which was used in the qface file and the same which is used
by the autogenerated qml types.
Adding the QML_IMPORT_PATH to our autogenerated qmltypes makes
sure QtCreator knows the type and can provide a code-completion
Change-Id: Ifd4ce8ec32da240ccf0070b737fd02c17f8fe2dc
Fixes: AUTOSUITE-743
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
In theory the documentation inside the qface files could be
transformed using the javadoc syntax and the parse_doc filter
function, but so far we only supported the brief tag and already
used qdoc commands in the function directly. As the tag functionality
of parse_doc is nothing we can really use, better use qdoc commands
in the qface documentation right away.
Change-Id: I9b23fe84acc6cd942e6fa7ec5933911b84ce22ec
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The qml_type tries to read both annotations now, qml_name and qml_type
For modules the filter returns the module_name or the new name from
the annotation.
As before this can be used to register all types under a specific
QML uri.
The last section of the uri is now also used as the QML name for
the module singleton holding all enums and factory functions.
E.g. a module named "com.example.climate" will now make all its
enums available from the "Climate" object (Climate.AutoRecirculation)
Change-Id: I6481a34876d6c47bd8f34c946c7638e34cc857f1
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
As long as the examples are not using frameworks on osx, it is better
to only build the configuration which is needed, instead of building
debug_and_release for the plugin and the libs.
Not using frameworks could lead to loading a wrong plugin version
when the application is build in debug mode, but the frameworks used
are in release mode (or vice versa).
Change-Id: Id5da6adafe5091edc489c22f36bc059542db2098
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
| |
The other templates have been fixed already before. Also make sure
the example doesn't specify a custom id to make sure we test this path
by default.
Change-Id: Icf4eb17c057ea8cba7673b9884c5123c4e749ffd
Fixes: AUTOSUITE-735
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
| |
- added 2019
- everything is (c) Luxoft instead of Pelagicore from now on
Change-Id: I4a6dbd46aaffbb90cea57626bd75e3972cea2cfc
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
| |
Change-Id: I820277271cb968958649fe4144a886133d74fd5c
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
| |
Change-Id: Id88db48e0e18761a9bc1b1014628bf0099c4e5cf
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
| |
Change-Id: I8f9caa83814519934fd244ae75817ae940e059a7
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
| |
Task-number: AUTOSUITE-628
Change-Id: Ia90e42d801c68d91dd71b309ea4c518f349f13f9
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|\
| |
| |
| | |
Change-Id: If48055bb577b4b59a836b2c4a00d940401b97c6a
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using the full uri makes it more unlikely that the export macro names
clash with the export macro of an library with the same name.
Task-number: AUTOSUITE-509
Change-Id: If5d66f7dc4d7e3e8edc4cbede1d2dfcbaad3b1d7
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix PLUGIN_CLASS_NAME in all places and remove PLUGIN_EXTENDS
where it is not needed.
For all plugins which are provided with the modules, fix the
PLUGIN_EXTENDS to match the module name to also deliver the cmake
file for these plugins.
Renamed the MprisPlugin class name to not clash with the normal
plugin name, as this is also used for the cmake filename.
This should also fix build errors when trying to create the cmake
files in non-existent folders.
Change-Id: I102019fab327273903c8c378595c06a25964cfe8
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds the addressbook example which is used to explain how the autogeneration
of models works.
Task-number: AUTOSUITE-422
Change-Id: I2a0c6cba81dfdcf072da9584b731f170cc927711
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|/
|
|
|
|
|
|
| |
As all qface examples have the same structure we end up with multiple
"demo" targets in QtCreator otherwise.
Change-Id: Ie12ca791a09f5fb2175dab1399cc4cbab56d98bc
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
| |
Use qdoc \snippet instead of hard coded snippets in the QtIvi core example walkthroughs
Task-number: AUTOSUITE-278
Change-Id: Icd966aeb53805d7b0009db490d5c462c22d75bf8
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Add documentation for remote object templates: update list of template
files and add a general description of the remote objects features.
Add an example project and a walkthrough to demonstrate the remote objects
generation features.
Task-number: QTAUTO-919
Change-Id: I3d25d29fd9b9ca2a72bbc6662f05b968d9aa5413
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
| |
Task-number: AUTOSUITE-190
Change-Id: I18a9f4d00951d3b0284846d7ef2808f59a512ff8
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
| |
Change-Id: I582e8c4c9aa137c6497594433ab751cd961d05f4
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Add better step by step explanations.
Make sure also the qface and yaml files are listed in the example
Removed the copright headers from the project files
Change-Id: I7f7480809efa52fae63a93a8724f86548fa160f6
Reviewed-by: Antti Hölttä <ahoelttae@luxoft.com>
|
|
|
|
|
| |
Change-Id: I408c855d9619e20f481a592dc1f514b90af642f9
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
| |
Change-Id: I602e0202457533cc9e6cfa8706577e1e951340e0
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
core -> ivicore
media -> ivimedia
vehiclefunctions -> ivivehiclefunctions
Change-Id: Icd8d7c45f2dbf0e18de1eea775398b45f8ff78f8
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|