Revision history [back]

What is the correct way to use the native booster for accelerated app launching of a QML/C++ App? And are there any dependencies required?

I am encountering the following issue in my application:

My .desktop file currently uses the X-Nemo-Application-Type=qtquick2 booster, but I want to switch to X-Nemo-Application-Type=silica-qt5 as recommended of the rpm-validator inside the SDK. The issue is that if I switch to the silica-qt5 booster I am getting a strange behaviour with the app cache folder:

Starting the app with the silica-qt5 booster from the desktop icon creates a wrong cache folder named mdeclarativecache_pre_initialized_qapplication-PID containing the actual cache folder. But the cache folder is correcly created if I start the app from the terminal.

Inside my application I am creating the cache folder the following way:

QStandardPaths::writableLocation(QStandardPaths::CacheLocation) + "/harbour-myApp"

Has anyone an idea what causes this issue and how to resolve it?

What is the correct way to use the native booster for accelerated app launching of a QML/C++ App? And are there any dependencies required?

I am encountering the following issue in my application:

My .desktop file currently uses the X-Nemo-Application-Type=qtquick2 booster, but I want to switch to X-Nemo-Application-Type=silica-qt5 as recommended of by the rpm-validator inside the SDK. The issue is that if I switch to the silica-qt5 booster I am getting a strange behaviour with the app cache folder:

Starting the app with the silica-qt5 booster from the desktop icon creates a wrong cache folder named mdeclarativecache_pre_initialized_qapplication-PID containing the actual cache folder. But the cache folder is correcly created if I start the app from the terminal.

Inside my application I am creating the cache folder the following way:

QString path = QStandardPaths::writableLocation(QStandardPaths::CacheLocation) + "/harbour-myApp"
"/harbour-myApp";
QDir dir(path);
if (!dir.exists())
    dir.mkpath(".");

Has anyone an idea what causes this issue and how to resolve it?

What is the correct way to use the native booster for accelerated app launching of a QML/C++ App? And are there any dependencies required?

I am encountering the following issue in my application:

My .desktop file currently uses the X-Nemo-Application-Type=qtquick2 booster, but I want to switch to X-Nemo-Application-Type=silica-qt5 as recommended by the rpm-validator inside the SDK. The issue is that if I switch to the silica-qt5 booster I am getting a strange behaviour with the app cache folder:

Starting the app with the silica-qt5 booster from the desktop icon creates a wrong cache folder named mdeclarativecache_pre_initialized_qapplication-PID containing the actual cache folder. But the cache folder is correcly created if I start the app from the terminal.

Inside my application I am creating the cache folder the following way:

QString path = QStandardPaths::writableLocation(QStandardPaths::CacheLocation) + "/harbour-myApp";
QDir dir(path);
if (!dir.exists())
    dir.mkpath(".");

Has anyone an idea what causes this issue and how to resolve it?

As there is no documentation I have the following questions:

1. What is the correct way to use the native booster for accelerated app launching of a QML/C++ App?
2. And are there any dependencies required?

Currently I am encountering the following issue in my application:

My .desktop file currently uses the X-Nemo-Application-Type=qtquick2 booster, but I want to switch to X-Nemo-Application-Type=silica-qt5 as recommended by the rpm-validator inside the SDK. The issue is that if I switch to the silica-qt5 booster I am getting a strange behaviour with the app cache folder:

Starting the app with the silica-qt5 booster from the desktop icon creates a wrong cache folder named mdeclarativecache_pre_initialized_qapplication-PID containing the actual cache folder. But the cache folder is correcly created if I start the app from the terminal.

Inside my application I am creating the cache folder the following way:

QString path = QStandardPaths::writableLocation(QStandardPaths::CacheLocation) + "/harbour-myApp";
QDir dir(path);
if (!dir.exists())
    dir.mkpath(".");

Has anyone an idea what causes this issue and how to resolve it?