The API is super generic, it's all strings and json objects.
There's no proper way to share text, just an Array of URLs, etc.
It needs some serious cleanup.
Apparently it needs to stay generic for Android and what not but there should still be some more higher-level convenience API for common stuff like sharing a certain file, some URL, or plain text.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T12184 Purpose | ||
| Open | ognarb | T12186 Purpose: Platform support | ||
| Open | None | T12188 Purpose: Split framework from providers | ||
| Open | None | T12190 Purpose: API Clean up or use contenthub instead |
Could it make sense to introduce a KPluginMetaData like API? Maybe where the class directly extends a QJsonObject and only provides typesafe getters/setters?
It could make sense to provide façade interfaces to do the common things the different plugin types allow.
This could be generated from the ./src/plugins/*PluginType.json files.
Would you like separate classes for the inbound/outbound args and the different types? Personally I would say that one class is enough for the different usecases.