From b5cd355c00b6ea8b12b706d3c2b83bde9f9e101c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 30 Dec 2025 12:38:43 +0000 Subject: [PATCH] doc: Update --- doc/clapper/migrating-to-010.html | 38 +++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/doc/clapper/migrating-to-010.html b/doc/clapper/migrating-to-010.html index 19de232d..6aa89ae6 100644 --- a/doc/clapper/migrating-to-010.html +++ b/doc/clapper/migrating-to-010.html @@ -132,6 +132,32 @@ their availability at runtime instead of compile time like before.
For more information how to use enhancers and how to write your own, see Clapper Enhancers documentation.
+If you still want to support both deprecated and new enhancer based implementations for the time being,
+you can always add an else code block for when proxy is not found and move your old logic there.
If you are developing/maintaining a Flatpak application, it is recommended to build Clapper without above 3 deprecated
+features (disable them through meson) as you can get enhancer plugins in the form of an extension. If you have not
+done that already, check out Clapper Flathub repo for info
+how to add them to your application manifest.
The clapper_enhancer_check() function gets deprecated. It was originally designed when only Extractable enhancers
+existed. Now with more robust plugin system that simply allows more then just handling certain scheme and host this
+function does not fit in it, hence its deprecation.
In most cases, applications should follow normal workflow, that is play something and if it does not work, handle an error
+(with possible fallback action). For cases where an app wants to inspect available enhancers and their capabilities, it can
+iterate (or get by module name) from ClapperEnhancerProxyList proxies (either from player or global list) and inspect
+its plugin info using given proxy object.
An easy to use replacement for clapper_enhancer_check() with proxies that implement ClapperExtractable interface,
+would be clapper_enhancer_proxy_extra_data_lists_value() with X-Schemes and X-Hosts as keys.
This version adds a clapper_media_item_populate_tags() which allows to set an item tag list initially.
+Useful for applications that know additional media item metadata that may not be inside its container or
+if they want to set some initial values to be displayed in UI before player will update them.
Previously the sole method to do something like that was to use taginject element in pipeline (e.g. as player
+video-filter). That method is still valid and supported, but trickier to perform as it requires app to synchronize
+values for another media item at the right moment (stop, change item, set new tag list, play).
Basically, use taginject if you want to force override for tags of media item. If you want to just set some
+initial values to ensure they never are empty, use clapper_media_item_populate_tags() instead.