This bug is to document the trail to include MiniApps into the regular CTK CMD Plugin.

We tried to make MiniApps "parseable" using different strategies:

Implementation of a two layer approach,

• registering a MiniApp and parsing for submodules
• resitering submoldules as executables

This approach did not work because the xml output is cached,
and the cache object uses a default xml parser that cannot be adapted,
so parsing it the second time allways failed.

Deactivating the cache (by always returning -1 as time steps),
would make it parsable and the correctly showed all mini apps ind the plugin.

The next problem arises when executing a mini app,
the problem is that the Sub-App needs to be the first argument after the executable, but this is not possible to inject into the CTK launcher (as is uses a hash table, and the forst arguement cannot be guaranteed to be the Sub-App).

Re-implementing the argument parsing on Backend-level (the parsing in CTK is private (PIMPL) ) would allow this, but at this point we already arrived at a notable number of changes and "un-nice" changes that we decided to stop here, and look for another option.

Current Plan is to, get rid of the MiniApp-way of grouping together these executables and creating single executables. Thereby using the Plugin in its original form.
Consequences of creating a variety of different executables still have to be discussed.