What's New

Qt ApplicationManager 6.6

Two new features have been added:

• NotificationModel will now complement the existing ApplicationModel and IntentModel classes.
• The application manager now comes with a bubblewrap container integration: this uses the bubblewrap utility to create a new kernel namespace and runs the requested binary in this sandbox isolated from the rest of the system. This is the base technology used in the Linux Flatpak ecosystem. See the Bubblewrap Container Example for an example setup with test applications.

In addition, there have been some changes in functionality:

• The IntentServerHandler::visibility property now defaults to Public instead of Private, the same way as it works for client-side intent definitions in an app's manifest file.
• QML applications will now quit immediately when requested to via ApplicationManager::stopApplication(), if no handler is connected to the ApplicationInterface::quit() signal. These applications would have been force-terminated only after a 250msec timeout before.
• The quick launch mechanism can now detect broken runtime/container combinations and will disable them instead of re-trying to start them in an infinite loop. This can be fine tuned via the new failedStartLimit and failedStartLimitIntervalSec configuration parameters.
• In order to support JavaScript's strict mode, the package role of the PackageManager singleton had to be renamed to packageObject, as package is a reserved JS keyword in strict mode. The old package role is still available in non-strict mode. All the other singleton models got a similar *Object alias role to keep the APIs consistent.

Qt ApplicationManager 6.3

The APIs and manifest definitions concerning the Package, Application and Intent fields for icon, name and description have been cleaned up. All three support the same API now, with the package's fields acting as a fallback for both the application and intent objects. Due to a clash between the property name and the function name in ApplicationObject, user code that called the Application.name(language) function before, now needs to replace this with Application.names[language].

Qt Application Manager 6.2

No new APIs were added, but the build system switched from qmake to CMake and the deprecated legacy ApplicationInterfaceExtension IPC mechanism was finally removed. A direct replacement for the old IPC had been added in 5.14 already in form of the new Intents mechanism.