George Kiagiadakis 8a8cd97ca8 core: make the object registration functions public ... This allows registering arbitrary objects on the core's registry and finding them later, without having to add API for each and every object. I think this is useful enough to have it public, even though it's probably not going to be used that much... The rationale here is to allow registering custom component loaders without having to make them subclass WpPlugin or to create custom API for registering component loaders specifically. Also, remove the wp_plugin_register() and wp_si_factory_register() functions, since they are not going to be used much in the future. The idea is to let the component loader do the registration under the scenes, as the component is getting loaded.		2023-06-20 12:39:29 +03:00
..
internal-comp-loader.c	core: introduce the notion of provided features on components	2023-06-20 12:39:29 +03:00
internal-comp-loader.h	component-loader: move module loading to a new WpInternalCompLoader object	2023-05-26 13:49:40 +03:00
pipewire-object-mixin.c	log: rename "message" level to "notice" and print criticals with "E"	2023-05-18 16:19:49 +03:00
pipewire-object-mixin.h	lib: remove WpEndpoint and WpSiEndpoint APIs	2023-04-17 07:48:18 -04:00
registry.h	core: make the object registration functions public	2023-06-20 12:39:29 +03:00