Commit c0be12c9 authored by Richard Lin's avatar Richard Lin
Browse files

Update descriptions.

parent 320ef18e
# Brief
Experimental scene changing framework for cluster, with Qt5.10 and Qt3DStudio.
# Detail Feature
1. Using dynamic link library to store resources, benifit from its protection of source and loading performance.
2. Each scene plugin is packaged into an individual dll file, easy to distribute.
3. InstrumentCluster will scan scene plugin when start up. The scene plugins should be stored in the InstrumentCluster/Scenes/.
4. InstrumentCluster has a scene selector, with brief previews.
5. Scene plugin will dynamic add/remove qt resource collection files. Delay loading/loading strategy can be adjusted in cpp file (haven't done in the demo).
6. Scene plugin will apply to every visual components, also including transitions, interactives. In a summary, all qml and resource files
can be changed dynamicly.
7. InstrumentCluster can store selected scene, and automatically load it after power on.
Experimental scene changing framework for cluster, using Qt5.10, with QtRO and Qt3DStudio.
# Structure
1. InstrumentCluster is the executable application. It is a demo which can use all scene plugins.
1. InstrumentCluster is the executable application, which can use all scene plugins.
2. ScenePlugin contains several cluster plugins, which generate to dynamic link libraries for InstrumentCluster.
3. Interface folder contains an interface class shared by the InstrumentCluster and every entities of ScenePlugin.
4. AndroidController is an important part of this demo. Runs on Android IVI and can remote control the InstrumentCluster.
# InstrumentCluster's Features
1. Each scene plugin is packaged into an individual ".so" file, easy to distribute.
2. InstrumentCluster will scan scene plugins when start up. The scene plugin files should be stored in the ./InstrumentCluster/Scenes/ folder.
3. InstrumentCluster has a scene selector, with brief previews.
4. Scene plugins can be dynamic add/removed to qt resource tree. Lazy loading or other loading strategies can be adjusted in cpp file (TODO).
5. Can apply to every visual components, also including transitions, interactives. In a summary, all qml and resource files can be changed dynamicly.
6. InstrumentCluster can store selected scene name, and automatically load it after power on.
# AndroidController's Features
1. Based on Android platform, which supposed to be the in-vechiel-infotainment system. Can remote change the InstrumentCluster's scene.
2. Due to the small storage capability in InstrumentCluster, IVI is the better place to store scenes. AndroidController can send the skin file to InstrumentCluster when needed.
3. Built-in AppStore enable scenes' purchasing and downloading (TODO).
4. Should have a UI to manager the loacl storage (TODO).
# Cluster Plugin Description
......@@ -34,10 +39,11 @@ can be changed dynamicly.
# How to build
1. Check the Qt3DStudio installation. Change the import directory in InstrumentCluster/main.cpp Line66 to your own Qt3DStudio/qml directory.
2. qmake make & make install
1. Qt >= 5.10
2. Check the Qt3DStudio installation. Change the import directory in InstrumentCluster/main.cpp Line66 to your own Qt3DStudio/qml directory.
3. qmake make & make install
# How to operate
# How to operate in InstrumentCluster side
1. "Up/Down" to navigate the scenes
2. "Space" to select the scene
......
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