Change Details

The old traders could lookup both applications and plugins, but plugins should nowadays be loaded via their JSON file, no desktop-file trader needed anymore. To get rid of plugins and servicetypes from the API, and keep only the application-lookup-related code, the older traders will be deprecated and their users should either switch to JSON for plugins (KPluginLoader) or KApplicationTrader for application desktop files. One API question remains: KApplicationTrader::self()->query("...") like the old traders, or KApplicationTrader::query("...") (static methods only, or making it a namespace, a bit procedural rather than OO), or KApplicationTrader().query("...") like QMimeDatabase/QFontDatabase (but with default ctors for performance) ?

KMimeTypeTrader and KServiceTypeTrader could lookup both applications and plugins, but plugins should nowadays be loaded via their JSON file (KPluginLoader), no desktop-file trader needed anymore. Except maybe for non-C++ plugins? KApplicationTrader gets rid of plugins and servicetypes from the API, in order to keep only the API to look up application desktop files. The trader query language is no longer used, as discussed on kde-frameworks-devel; instead we use a std::function for filtering, like KPluginLoader. This commit also adds KApplicationTrader::isSubsequence, necessary to replace the subseq operator of the trader query language.

The old tKMimeTypeTrader and KServiceTypeTraders could lookup both applications and plugins, but plugins should nowadays be loaded via their JSON fileplugins, no desktop-file traderbut plugins should nowadays be loaded via their JSON file (KPluginLoader), no desktop-file trader needed anymore. Except maybe for non-C++ plugins? ToKApplicationTrader gets rid of plugins and servicetypes from the API, and keep only the application-lookup-related code, the older traders will be deprecated and their users should either switch to JSON for plugins (KPluginLoader)in or KApplicationTrader fororder to keep only the API to look up application desktop files. One API question remains:The trader query language is no longer used, as discussed on KApplicationTrader::self()->query("...") like the old traderskde-frameworks-devel; instead we use a std::function for filtering, orlike KApplicationTrader::query("...") (static methods only, or making it a namespace, a bit procedural rather than OO)KPluginLoader. This commit also adds KApplicationTrader::isSubsequence, ornecessary to KApplicationTrader().query("...") like QMimeDatabase/QFontDatabase (but with default ctors for performance) ?replace the subseq operator of the trader query language.