2020-07-29 19:27:40 +05:30
|
|
|
/* WirePlumber
|
|
|
|
|
*
|
2020-08-31 16:21:35 +03:00
|
|
|
* Copyright © 2020 Collabora Ltd.
|
2020-07-29 19:27:40 +05:30
|
|
|
* @author Raghavendra Rao <raghavendra.rao@collabora.com>
|
|
|
|
|
*
|
|
|
|
|
* SPDX-License-Identifier: MIT
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#define G_LOG_DOMAIN "wp-metadata"
|
|
|
|
|
|
|
|
|
|
#include "metadata.h"
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
#include "core.h"
|
2021-05-06 15:45:13 +03:00
|
|
|
#include "log.h"
|
2020-07-29 19:27:40 +05:30
|
|
|
#include "error.h"
|
|
|
|
|
#include "wpenums.h"
|
|
|
|
|
|
|
|
|
|
#include <pipewire/pipewire.h>
|
|
|
|
|
#include <pipewire/extensions/metadata.h>
|
|
|
|
|
|
2021-05-21 18:40:43 +03:00
|
|
|
/*! \defgroup wpmetadata WpMetadata */
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \struct WpMetadata
|
|
|
|
|
*
|
|
|
|
|
* The WpMetadata class allows accessing the properties and methods of
|
|
|
|
|
* PipeWire metadata object (`struct pw_metadata`).
|
2021-05-13 17:54:58 +03:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* A WpMetadata is constructed internally when a new metadata object appears on the
|
|
|
|
|
* PipeWire registry and it is made available through the WpObjectManager API.
|
2021-05-13 17:54:58 +03:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* \gsignals
|
|
|
|
|
*
|
|
|
|
|
* \par changed
|
|
|
|
|
* \parblock
|
|
|
|
|
* \code
|
|
|
|
|
* void
|
2021-05-13 17:54:58 +03:00
|
|
|
* changed_callback (WpMetadata * self,
|
|
|
|
|
* guint object,
|
2021-05-21 18:40:43 +03:00
|
|
|
* gchar * key,
|
|
|
|
|
* gchar * type,
|
|
|
|
|
* gchar * value,
|
2021-05-13 17:54:58 +03:00
|
|
|
* gpointer user_data)
|
2021-05-21 18:40:43 +03:00
|
|
|
* \endcode
|
|
|
|
|
* Emited when metadata change
|
2021-05-13 17:54:58 +03:00
|
|
|
*
|
|
|
|
|
* Parameters:
|
2021-05-21 18:40:43 +03:00
|
|
|
* - `subject` - the metadata subject id
|
|
|
|
|
* - `key` - the metadata key
|
|
|
|
|
* - `type` - the value type
|
|
|
|
|
* - `value` - the metadata value
|
2021-05-13 17:54:58 +03:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* Flags: G_SIGNAL_RUN_LAST
|
|
|
|
|
* \endparblock
|
2021-05-13 17:54:58 +03:00
|
|
|
*/
|
2020-08-31 16:14:47 +03:00
|
|
|
enum {
|
|
|
|
|
SIGNAL_CHANGED,
|
|
|
|
|
N_SIGNALS,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static guint32 signals[N_SIGNALS] = {0};
|
|
|
|
|
|
|
|
|
|
/* data structure */
|
|
|
|
|
|
|
|
|
|
struct item
|
|
|
|
|
{
|
|
|
|
|
uint32_t subject;
|
|
|
|
|
gchar *key;
|
|
|
|
|
gchar *type;
|
|
|
|
|
gchar *value;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
set_item (struct item * item, uint32_t subject, const char * key,
|
|
|
|
|
const char * type, const char * value)
|
|
|
|
|
{
|
|
|
|
|
item->subject = subject;
|
|
|
|
|
item->key = g_strdup (key);
|
|
|
|
|
item->type = g_strdup (type);
|
|
|
|
|
item->value = g_strdup (value);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
clear_item (struct item * item)
|
|
|
|
|
{
|
|
|
|
|
g_free (item->key);
|
|
|
|
|
g_free (item->type);
|
|
|
|
|
g_free (item->value);
|
|
|
|
|
spa_zero (*item);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static struct item *
|
|
|
|
|
find_item (struct pw_array * metadata, uint32_t subject, const char * key)
|
|
|
|
|
{
|
|
|
|
|
struct item *item;
|
|
|
|
|
|
|
|
|
|
pw_array_for_each (item, metadata) {
|
|
|
|
|
if (item->subject == subject && (key == NULL || !strcmp (item->key, key))) {
|
|
|
|
|
return item;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
return NULL;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int
|
|
|
|
|
clear_subject (struct pw_array * metadata, uint32_t subject)
|
|
|
|
|
{
|
|
|
|
|
struct item *item;
|
|
|
|
|
uint32_t removed = 0;
|
|
|
|
|
|
|
|
|
|
while (true) {
|
|
|
|
|
item = find_item (metadata, subject, NULL);
|
|
|
|
|
if (item == NULL)
|
|
|
|
|
break;
|
|
|
|
|
clear_item (item);
|
|
|
|
|
pw_array_remove (metadata, item);
|
|
|
|
|
removed++;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return removed;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
clear_items (struct pw_array * metadata)
|
|
|
|
|
{
|
|
|
|
|
struct item *item;
|
|
|
|
|
|
|
|
|
|
pw_array_consume (item, metadata) {
|
|
|
|
|
clear_item (item);
|
|
|
|
|
pw_array_remove (metadata, item);
|
|
|
|
|
}
|
|
|
|
|
pw_array_reset (metadata);
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
|
|
|
|
|
typedef struct _WpMetadataPrivate WpMetadataPrivate;
|
|
|
|
|
struct _WpMetadataPrivate
|
|
|
|
|
{
|
|
|
|
|
struct pw_metadata *iface;
|
|
|
|
|
struct spa_hook listener;
|
|
|
|
|
struct pw_array metadata;
|
|
|
|
|
};
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
G_DEFINE_TYPE_WITH_PRIVATE (WpMetadata, wp_metadata, WP_TYPE_GLOBAL_PROXY)
|
2020-07-29 19:27:40 +05:30
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
wp_metadata_init (WpMetadata * self)
|
|
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
WpMetadataPrivate *priv = wp_metadata_get_instance_private (self);
|
|
|
|
|
pw_array_init (&priv->metadata, 4096);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
wp_metadata_finalize (GObject * object)
|
|
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (object));
|
|
|
|
|
|
|
|
|
|
pw_array_clear (&priv->metadata);
|
|
|
|
|
|
2020-07-29 19:27:40 +05:30
|
|
|
G_OBJECT_CLASS (wp_metadata_parent_class)->finalize (object);
|
|
|
|
|
}
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
static WpObjectFeatures
|
|
|
|
|
wp_metadata_get_supported_features (WpObject * object)
|
|
|
|
|
{
|
|
|
|
|
return WP_PROXY_FEATURE_BOUND | WP_METADATA_FEATURE_DATA;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
enum {
|
|
|
|
|
STEP_BIND = WP_TRANSITION_STEP_CUSTOM_START,
|
|
|
|
|
STEP_CACHE
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static guint
|
|
|
|
|
wp_metadata_activate_get_next_step (WpObject * object,
|
|
|
|
|
WpFeatureActivationTransition * transition, guint step,
|
|
|
|
|
WpObjectFeatures missing)
|
|
|
|
|
{
|
|
|
|
|
g_return_val_if_fail (
|
|
|
|
|
missing & (WP_PROXY_FEATURE_BOUND | WP_METADATA_FEATURE_DATA),
|
|
|
|
|
WP_TRANSITION_STEP_ERROR);
|
|
|
|
|
|
|
|
|
|
/* bind if not already bound */
|
|
|
|
|
if (missing & WP_PROXY_FEATURE_BOUND)
|
|
|
|
|
return STEP_BIND;
|
|
|
|
|
else
|
|
|
|
|
return STEP_CACHE;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
wp_metadata_activate_execute_step (WpObject * object,
|
|
|
|
|
WpFeatureActivationTransition * transition, guint step,
|
|
|
|
|
WpObjectFeatures missing)
|
|
|
|
|
{
|
|
|
|
|
switch (step) {
|
|
|
|
|
case STEP_CACHE:
|
|
|
|
|
/* just wait for initial_sync_done() */
|
|
|
|
|
break;
|
|
|
|
|
default:
|
|
|
|
|
WP_OBJECT_CLASS (wp_metadata_parent_class)->
|
|
|
|
|
activate_execute_step (object, transition, step, missing);
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
static int
|
|
|
|
|
metadata_event_property (void *object, uint32_t subject, const char *key,
|
|
|
|
|
const char *type, const char *value)
|
|
|
|
|
{
|
|
|
|
|
WpMetadata *self = WP_METADATA (object);
|
|
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (self));
|
|
|
|
|
struct item *item = NULL;
|
|
|
|
|
|
|
|
|
|
if (key == NULL) {
|
|
|
|
|
if (clear_subject (&priv->metadata, subject) > 0) {
|
|
|
|
|
wp_debug_object (self, "remove id:%d", subject);
|
|
|
|
|
g_signal_emit (self, signals[SIGNAL_CHANGED], 0, subject, NULL, NULL,
|
|
|
|
|
NULL);
|
|
|
|
|
}
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
item = find_item (&priv->metadata, subject, key);
|
|
|
|
|
if (item == NULL) {
|
|
|
|
|
if (value == NULL)
|
|
|
|
|
return 0;
|
|
|
|
|
item = pw_array_add (&priv->metadata, sizeof (*item));
|
|
|
|
|
if (item == NULL)
|
|
|
|
|
return -errno;
|
|
|
|
|
} else {
|
|
|
|
|
clear_item (item);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (value != NULL) {
|
|
|
|
|
if (type == NULL)
|
|
|
|
|
type = "string";
|
|
|
|
|
set_item (item, subject, key, type, value);
|
|
|
|
|
wp_debug_object (self, "add id:%d key:%s type:%s value:%s",
|
|
|
|
|
subject, key, type, value);
|
|
|
|
|
} else {
|
|
|
|
|
type = NULL;
|
|
|
|
|
pw_array_remove (&priv->metadata, item);
|
|
|
|
|
wp_debug_object (self, "remove id:%d key:%s", subject, key);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
g_signal_emit (self, signals[SIGNAL_CHANGED], 0, subject, key, type, value);
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static const struct pw_metadata_events metadata_events = {
|
|
|
|
|
PW_VERSION_METADATA_EVENTS,
|
|
|
|
|
.property = metadata_event_property,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
initial_sync_done (WpCore * core, GAsyncResult * res, WpMetadata * self)
|
|
|
|
|
{
|
|
|
|
|
g_autoptr (GError) error = NULL;
|
|
|
|
|
if (!wp_core_sync_finish (core, res, &error)) {
|
|
|
|
|
wp_warning_object (self, "core sync error: %s", error->message);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
wp_object_update_features (WP_OBJECT (self), WP_METADATA_FEATURE_DATA, 0);
|
2020-08-31 16:14:47 +03:00
|
|
|
}
|
|
|
|
|
|
2020-07-29 19:27:40 +05:30
|
|
|
static void
|
|
|
|
|
wp_metadata_pw_proxy_created (WpProxy * proxy, struct pw_proxy * pw_proxy)
|
|
|
|
|
{
|
|
|
|
|
WpMetadata *self = WP_METADATA (proxy);
|
|
|
|
|
WpMetadataPrivate *priv = wp_metadata_get_instance_private (self);
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
g_autoptr (WpCore) core = wp_object_get_core (WP_OBJECT (self));
|
2020-08-31 16:14:47 +03:00
|
|
|
|
2020-07-29 19:27:40 +05:30
|
|
|
priv->iface = (struct pw_metadata *) pw_proxy;
|
2020-08-31 16:14:47 +03:00
|
|
|
pw_metadata_add_listener (priv->iface, &priv->listener,
|
|
|
|
|
&metadata_events, self);
|
|
|
|
|
wp_core_sync (core, NULL, (GAsyncReadyCallback) initial_sync_done, self);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
static void
|
|
|
|
|
wp_metadata_pw_proxy_destroyed (WpProxy * proxy)
|
|
|
|
|
{
|
|
|
|
|
WpMetadata *self = WP_METADATA (proxy);
|
|
|
|
|
WpMetadataPrivate *priv = wp_metadata_get_instance_private (self);
|
|
|
|
|
|
|
|
|
|
clear_items (&priv->metadata);
|
|
|
|
|
wp_object_update_features (WP_OBJECT (self), 0, WP_METADATA_FEATURE_DATA);
|
2021-05-12 13:52:02 -04:00
|
|
|
|
|
|
|
|
WP_PROXY_CLASS (wp_metadata_parent_class)->pw_proxy_destroyed (proxy);
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
}
|
|
|
|
|
|
2020-07-29 19:27:40 +05:30
|
|
|
static void
|
|
|
|
|
wp_metadata_class_init (WpMetadataClass * klass)
|
|
|
|
|
{
|
|
|
|
|
GObjectClass *object_class = (GObjectClass *) klass;
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
WpObjectClass *wpobject_class = (WpObjectClass *) klass;
|
2020-07-29 19:27:40 +05:30
|
|
|
WpProxyClass *proxy_class = (WpProxyClass *) klass;
|
|
|
|
|
|
|
|
|
|
object_class->finalize = wp_metadata_finalize;
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
wpobject_class->get_supported_features = wp_metadata_get_supported_features;
|
|
|
|
|
wpobject_class->activate_get_next_step = wp_metadata_activate_get_next_step;
|
|
|
|
|
wpobject_class->activate_execute_step = wp_metadata_activate_execute_step;
|
|
|
|
|
|
2020-07-29 19:27:40 +05:30
|
|
|
proxy_class->pw_iface_type = PW_TYPE_INTERFACE_Metadata;
|
|
|
|
|
proxy_class->pw_iface_version = PW_VERSION_METADATA;
|
|
|
|
|
proxy_class->pw_proxy_created = wp_metadata_pw_proxy_created;
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
proxy_class->pw_proxy_destroyed = wp_metadata_pw_proxy_destroyed;
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
signals[SIGNAL_CHANGED] = g_signal_new ("changed", G_TYPE_FROM_CLASS (klass),
|
|
|
|
|
G_SIGNAL_RUN_LAST, 0, NULL, NULL, NULL, G_TYPE_NONE, 4,
|
|
|
|
|
G_TYPE_UINT, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING);
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
struct metadata_iterator_data
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
WpMetadata *metadata;
|
|
|
|
|
const struct item *item;
|
|
|
|
|
guint32 subject;
|
2020-07-29 19:27:40 +05:30
|
|
|
};
|
|
|
|
|
|
2020-07-31 17:36:21 +03:00
|
|
|
static void
|
2020-08-31 16:14:47 +03:00
|
|
|
metadata_iterator_reset (WpIterator *it)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
struct metadata_iterator_data *it_data = wp_iterator_get_user_data (it);
|
|
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (it_data->metadata);
|
|
|
|
|
|
|
|
|
|
it_data->item = pw_array_first (&priv->metadata);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
static gboolean
|
|
|
|
|
metadata_iterator_next (WpIterator *it, GValue *item)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
struct metadata_iterator_data *it_data = wp_iterator_get_user_data (it);
|
|
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (it_data->metadata);
|
|
|
|
|
|
|
|
|
|
while (pw_array_check (&priv->metadata, it_data->item)) {
|
|
|
|
|
if ((it_data->subject == PW_ID_ANY ||
|
2021-01-11 13:09:23 -05:00
|
|
|
it_data->subject == it_data->item->subject)) {
|
2020-08-31 16:14:47 +03:00
|
|
|
g_value_init (item, G_TYPE_POINTER);
|
|
|
|
|
g_value_set_pointer (item, (gpointer) it_data->item);
|
|
|
|
|
it_data->item++;
|
|
|
|
|
return TRUE;
|
|
|
|
|
}
|
|
|
|
|
it_data->item++;
|
|
|
|
|
}
|
|
|
|
|
return FALSE;
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
static gboolean
|
|
|
|
|
metadata_iterator_fold (WpIterator *it, WpIteratorFoldFunc func, GValue *ret,
|
|
|
|
|
gpointer data)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
struct metadata_iterator_data *it_data = wp_iterator_get_user_data (it);
|
2020-07-31 17:36:21 +03:00
|
|
|
WpMetadataPrivate *priv =
|
2020-08-31 16:14:47 +03:00
|
|
|
wp_metadata_get_instance_private (it_data->metadata);
|
|
|
|
|
const struct item *i;
|
|
|
|
|
|
|
|
|
|
pw_array_for_each (i, &priv->metadata) {
|
|
|
|
|
if ((it_data->subject == PW_ID_ANY ||
|
2021-01-11 13:09:23 -05:00
|
|
|
it_data->subject == it_data->item->subject)) {
|
2020-08-31 16:14:47 +03:00
|
|
|
g_auto (GValue) item = G_VALUE_INIT;
|
|
|
|
|
g_value_init (&item, G_TYPE_POINTER);
|
|
|
|
|
g_value_set_pointer (&item, (gpointer) i);
|
|
|
|
|
if (!func (&item, ret, data))
|
|
|
|
|
return FALSE;
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
2020-08-31 16:14:47 +03:00
|
|
|
return TRUE;
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
static void
|
|
|
|
|
metadata_iterator_finalize (WpIterator *it)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
struct metadata_iterator_data *it_data = wp_iterator_get_user_data (it);
|
|
|
|
|
g_object_unref (it_data->metadata);
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
static const WpIteratorMethods metadata_iterator_methods = {
|
2020-11-16 11:16:35 +02:00
|
|
|
.version = WP_ITERATOR_METHODS_VERSION,
|
2020-08-31 16:14:47 +03:00
|
|
|
.reset = metadata_iterator_reset,
|
|
|
|
|
.next = metadata_iterator_next,
|
|
|
|
|
.fold = metadata_iterator_fold,
|
|
|
|
|
.finalize = metadata_iterator_finalize,
|
|
|
|
|
};
|
2020-07-31 17:36:21 +03:00
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \brief Iterates over metadata items that matches the given \a subject.
|
2020-08-31 16:14:47 +03:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* If no constraints are specified, the returned iterator iterates over all the
|
2020-08-31 16:14:47 +03:00
|
|
|
* stored metadata.
|
|
|
|
|
*
|
|
|
|
|
* Note that this method works on cached metadata. When you change metadata
|
|
|
|
|
* with wp_metadata_set(), this cache will be updated on the next round-trip
|
|
|
|
|
* with the pipewire server.
|
|
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* \ingroup wpmetadata
|
|
|
|
|
* \param self a metadata object
|
|
|
|
|
* \param subject the metadata subject id, or -1 (PW_ID_ANY)
|
|
|
|
|
* \returns (transfer full): an iterator that iterates over the found metadata.
|
2020-08-31 16:14:47 +03:00
|
|
|
* Use wp_metadata_iterator_item_extract() to parse the items returned by
|
|
|
|
|
* this iterator.
|
|
|
|
|
*/
|
|
|
|
|
WpIterator *
|
2021-02-05 10:20:33 -05:00
|
|
|
wp_metadata_new_iterator (WpMetadata * self, guint32 subject)
|
2020-08-31 16:14:47 +03:00
|
|
|
{
|
|
|
|
|
WpMetadataPrivate *priv;
|
|
|
|
|
g_autoptr (WpIterator) it = NULL;
|
|
|
|
|
struct metadata_iterator_data *it_data;
|
|
|
|
|
|
|
|
|
|
g_return_val_if_fail (self != NULL, NULL);
|
|
|
|
|
priv = wp_metadata_get_instance_private (self);
|
|
|
|
|
|
|
|
|
|
it = wp_iterator_new (&metadata_iterator_methods,
|
|
|
|
|
sizeof (struct metadata_iterator_data));
|
|
|
|
|
it_data = wp_iterator_get_user_data (it);
|
|
|
|
|
it_data->metadata = g_object_ref (self);
|
|
|
|
|
it_data->item = pw_array_first (&priv->metadata);
|
|
|
|
|
it_data->subject = subject;
|
|
|
|
|
return g_steal_pointer (&it);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \brief Extracts the metadata subject, key, type and value out of a
|
|
|
|
|
* GValue that was returned from the WpIterator of wp_metadata_find()
|
2020-08-31 16:14:47 +03:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* \ingroup wpmetadata
|
|
|
|
|
* \param item a GValue that was returned from the WpIterator of wp_metadata_find()
|
|
|
|
|
* \param subject (out)(optional): the subject id of the current item
|
|
|
|
|
* \param key (out)(optional)(transfer none): the key of the current item
|
|
|
|
|
* \param type (out)(optional)(transfer none): the type of the current item
|
|
|
|
|
* \param value (out)(optional)(transfer none): the value of the current item
|
2020-08-31 16:14:47 +03:00
|
|
|
*/
|
|
|
|
|
void
|
|
|
|
|
wp_metadata_iterator_item_extract (const GValue * item, guint32 * subject,
|
|
|
|
|
const gchar ** key, const gchar ** type, const gchar ** value)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
const struct item *i = g_value_get_pointer (item);
|
|
|
|
|
g_return_if_fail (i != NULL);
|
|
|
|
|
if (subject)
|
|
|
|
|
*subject = i->subject;
|
|
|
|
|
if (key)
|
|
|
|
|
*key = i->key;
|
|
|
|
|
if (type)
|
|
|
|
|
*type = i->type;
|
|
|
|
|
if (value)
|
|
|
|
|
*value = i->value;
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \brief Finds the metadata value given its \a subject and \a key.
|
2021-01-11 13:09:23 -05:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* \ingroup wpmetadata
|
|
|
|
|
* \param self a metadata object
|
|
|
|
|
* \param subject the metadata subject id
|
|
|
|
|
* \param key the metadata key name
|
|
|
|
|
* \param type (out)(optional): the metadata type name
|
|
|
|
|
* \returns the metadata string value, or NULL if not found.
|
2021-01-11 13:09:23 -05:00
|
|
|
*/
|
|
|
|
|
const gchar *
|
|
|
|
|
wp_metadata_find (WpMetadata * self, guint32 subject, const gchar * key,
|
|
|
|
|
const gchar ** type)
|
|
|
|
|
{
|
|
|
|
|
g_autoptr (WpIterator) it = NULL;
|
|
|
|
|
g_auto (GValue) val = G_VALUE_INIT;
|
2021-02-05 10:20:33 -05:00
|
|
|
it = wp_metadata_new_iterator (self, subject);
|
2021-01-11 13:09:23 -05:00
|
|
|
for (; wp_iterator_next (it, &val); g_value_unset (&val)) {
|
|
|
|
|
const gchar *k = NULL, *t = NULL, *v = NULL;
|
|
|
|
|
wp_metadata_iterator_item_extract (&val, NULL, &k, &t, &v);
|
|
|
|
|
if (g_strcmp0 (k, key) == 0) {
|
|
|
|
|
if (type)
|
|
|
|
|
*type = t;
|
|
|
|
|
return v;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
return NULL;
|
|
|
|
|
}
|
|
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \brief Sets the metadata associated with the given \a subject and \a key.
|
|
|
|
|
* Use NULL as a value to unset the given \a key and use NULL in both \a key
|
|
|
|
|
* and \a value to remove all metadata associated with the given \a subject.
|
2020-08-31 16:14:47 +03:00
|
|
|
*
|
2021-05-21 18:40:43 +03:00
|
|
|
* \ingroup wpmetadata
|
|
|
|
|
* \param self the metadata object
|
|
|
|
|
* \param subject the subject id for which this metadata property is being set
|
|
|
|
|
* \param key (nullable): the key to set, or NULL to remove all metadata for
|
|
|
|
|
* \a subject
|
|
|
|
|
* \param type (nullable): the type of the value; NULL is synonymous to "string"
|
|
|
|
|
* \param value (nullable): the value to set, or NULL to unset the given \a key
|
2020-08-31 16:14:47 +03:00
|
|
|
*/
|
|
|
|
|
void
|
|
|
|
|
wp_metadata_set (WpMetadata * self, guint32 subject,
|
|
|
|
|
const gchar * key, const gchar * type, const gchar * value)
|
|
|
|
|
{
|
|
|
|
|
WpMetadataPrivate *priv = wp_metadata_get_instance_private (self);
|
|
|
|
|
pw_metadata_set_property (priv->iface, subject, key, type, value);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \brief Clears permanently all stored metadata.
|
|
|
|
|
* \ingroup wpmetadata
|
|
|
|
|
* \param self the metadata object
|
2020-08-31 16:14:47 +03:00
|
|
|
*/
|
|
|
|
|
void
|
|
|
|
|
wp_metadata_clear (WpMetadata * self)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
WpMetadataPrivate *priv = wp_metadata_get_instance_private (self);
|
|
|
|
|
pw_metadata_clear (priv->iface);
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-05-21 18:40:43 +03:00
|
|
|
* \struct WpImplMetadata
|
|
|
|
|
* Implementation of the metadata object.
|
|
|
|
|
*
|
|
|
|
|
* Activate this object with at least WP_PROXY_FEATURE_BOUND to export it to
|
|
|
|
|
* PipeWire.
|
2021-05-13 17:54:58 +03:00
|
|
|
*/
|
2020-08-31 16:14:47 +03:00
|
|
|
struct _WpImplMetadata
|
|
|
|
|
{
|
|
|
|
|
WpMetadata parent;
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
struct spa_interface iface;
|
|
|
|
|
struct spa_hook_list hooks;
|
|
|
|
|
};
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
G_DEFINE_TYPE (WpImplMetadata, wp_impl_metadata, WP_TYPE_METADATA)
|
2020-07-31 17:36:21 +03:00
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
#define pw_metadata_emit(hooks,method,version,...) \
|
|
|
|
|
spa_hook_list_call_simple(hooks, struct pw_metadata_events, \
|
|
|
|
|
method, version, ##__VA_ARGS__)
|
2020-07-31 17:36:21 +03:00
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
#define pw_metadata_emit_property(hooks,...) \
|
|
|
|
|
pw_metadata_emit(hooks,property, 0, ##__VA_ARGS__)
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-07-31 17:36:21 +03:00
|
|
|
static void
|
2020-08-31 16:14:47 +03:00
|
|
|
emit_properties (WpImplMetadata *self)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
|
|
|
|
struct item *item;
|
2020-07-31 17:36:21 +03:00
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (self));
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
pw_array_for_each(item, &priv->metadata) {
|
|
|
|
|
wp_debug_object (self, "emit property: %d %s %s %s",
|
|
|
|
|
item->subject, item->key, item->type, item->value);
|
|
|
|
|
pw_metadata_emit_property (&self->hooks,
|
|
|
|
|
item->subject,
|
|
|
|
|
item->key,
|
|
|
|
|
item->type,
|
|
|
|
|
item->value);
|
2020-07-31 17:36:21 +03:00
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2020-07-31 17:36:21 +03:00
|
|
|
static int
|
2020-08-31 16:14:47 +03:00
|
|
|
impl_add_listener (void * object, struct spa_hook * listener,
|
|
|
|
|
const struct pw_metadata_events * events, void * data)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
|
|
|
|
WpImplMetadata *self = WP_IMPL_METADATA (object);
|
2020-08-31 16:14:47 +03:00
|
|
|
struct spa_hook_list save;
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
spa_hook_list_isolate (&self->hooks, &save, listener, events, data);
|
|
|
|
|
emit_properties (self);
|
|
|
|
|
spa_hook_list_join (&self->hooks, &save);
|
2020-07-29 19:27:40 +05:30
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2020-08-31 16:14:47 +03:00
|
|
|
static int
|
|
|
|
|
impl_set_property (void * object, uint32_t subject, const char * key,
|
|
|
|
|
const char * type, const char * value)
|
|
|
|
|
{
|
|
|
|
|
return metadata_event_property (object, subject, key, type, value);
|
|
|
|
|
}
|
|
|
|
|
|
2020-07-31 17:36:21 +03:00
|
|
|
static int
|
|
|
|
|
impl_clear (void *object)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
|
|
|
|
WpImplMetadata *self = WP_IMPL_METADATA (object);
|
2020-07-31 17:36:21 +03:00
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (self));
|
2020-08-31 16:14:47 +03:00
|
|
|
|
|
|
|
|
wp_debug_object (self, "clearing all metadata");
|
|
|
|
|
clear_items (&priv->metadata);
|
2020-07-29 19:27:40 +05:30
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static const struct pw_metadata_methods impl_metadata = {
|
|
|
|
|
PW_VERSION_METADATA_METHODS,
|
|
|
|
|
.add_listener = impl_add_listener,
|
|
|
|
|
.set_property = impl_set_property,
|
|
|
|
|
.clear = impl_clear,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
wp_impl_metadata_init (WpImplMetadata * self)
|
|
|
|
|
{
|
2020-07-31 17:36:21 +03:00
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (self));
|
2020-07-29 19:27:40 +05:30
|
|
|
|
|
|
|
|
self->iface = SPA_INTERFACE_INIT (
|
2020-07-31 17:36:21 +03:00
|
|
|
PW_TYPE_INTERFACE_Metadata,
|
|
|
|
|
PW_VERSION_METADATA,
|
|
|
|
|
&impl_metadata, self);
|
2020-08-31 16:14:47 +03:00
|
|
|
spa_hook_list_init (&self->hooks);
|
2020-07-29 19:27:40 +05:30
|
|
|
|
|
|
|
|
priv->iface = (struct pw_metadata *) &self->iface;
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
wp_object_update_features (WP_OBJECT (self), WP_METADATA_FEATURE_DATA, 0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
wp_impl_metadata_dispose (GObject * object)
|
|
|
|
|
{
|
|
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (object));
|
|
|
|
|
|
|
|
|
|
clear_items (&priv->metadata);
|
|
|
|
|
wp_object_update_features (WP_OBJECT (object), 0, WP_METADATA_FEATURE_DATA);
|
|
|
|
|
|
|
|
|
|
G_OBJECT_CLASS (wp_impl_metadata_parent_class)->dispose (object);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
2020-08-31 16:14:47 +03:00
|
|
|
wp_impl_metadata_on_changed (WpImplMetadata * self, guint32 subject,
|
|
|
|
|
const gchar * key, const gchar * type, const gchar * value, gpointer data)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
2020-08-31 16:14:47 +03:00
|
|
|
wp_debug_object (self, "emit property: %d %s %s %s",
|
|
|
|
|
subject, key, type, value);
|
|
|
|
|
pw_metadata_emit_property (&self->hooks, subject, key, type, value);
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
wp_impl_metadata_activate_execute_step (WpObject * object,
|
|
|
|
|
WpFeatureActivationTransition * transition, guint step,
|
|
|
|
|
WpObjectFeatures missing)
|
2020-07-29 19:27:40 +05:30
|
|
|
{
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
WpImplMetadata *self = WP_IMPL_METADATA (object);
|
2020-07-31 17:36:21 +03:00
|
|
|
WpMetadataPrivate *priv =
|
|
|
|
|
wp_metadata_get_instance_private (WP_METADATA (self));
|
2020-07-29 19:27:40 +05:30
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
switch (step) {
|
|
|
|
|
case STEP_BIND: {
|
|
|
|
|
g_autoptr (WpCore) core = wp_object_get_core (object);
|
2020-07-29 19:27:40 +05:30
|
|
|
struct pw_core *pw_core = wp_core_get_pw_core (core);
|
|
|
|
|
|
2020-07-31 17:36:21 +03:00
|
|
|
/* no pw_core -> we are not connected */
|
|
|
|
|
if (!pw_core) {
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
wp_transition_return_error (WP_TRANSITION (transition), g_error_new (
|
|
|
|
|
WP_DOMAIN_LIBRARY, WP_LIBRARY_ERROR_OPERATION_FAILED,
|
2020-07-31 17:36:21 +03:00
|
|
|
"The WirePlumber core is not connected; "
|
|
|
|
|
"object cannot be exported to PipeWire"));
|
|
|
|
|
return;
|
|
|
|
|
}
|
2020-07-29 19:27:40 +05:30
|
|
|
|
2021-04-28 20:46:08 +03:00
|
|
|
wp_proxy_watch_bind_error (WP_PROXY (self), WP_TRANSITION (transition));
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
wp_proxy_set_pw_proxy (WP_PROXY (self), pw_core_export (pw_core,
|
2020-07-31 17:36:21 +03:00
|
|
|
PW_TYPE_INTERFACE_Metadata,
|
2020-08-31 16:14:47 +03:00
|
|
|
NULL, priv->iface, 0));
|
|
|
|
|
g_signal_connect (self, "changed",
|
|
|
|
|
(GCallback) wp_impl_metadata_on_changed, NULL);
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
case STEP_CACHE:
|
|
|
|
|
/* never reached because WP_METADATA_FEATURE_DATA is always enabled */
|
|
|
|
|
g_assert_not_reached ();
|
|
|
|
|
break;
|
|
|
|
|
default:
|
|
|
|
|
WP_OBJECT_CLASS (wp_impl_metadata_parent_class)->
|
|
|
|
|
activate_execute_step (object, transition, step, missing);
|
|
|
|
|
break;
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
static void
|
|
|
|
|
wp_impl_metadata_pw_proxy_destroyed (WpProxy * proxy)
|
|
|
|
|
{
|
|
|
|
|
g_signal_handlers_disconnect_by_func (proxy,
|
|
|
|
|
(GCallback) wp_impl_metadata_on_changed, NULL);
|
|
|
|
|
}
|
|
|
|
|
|
2020-07-29 19:27:40 +05:30
|
|
|
static void
|
|
|
|
|
wp_impl_metadata_class_init (WpImplMetadataClass * klass)
|
|
|
|
|
{
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
GObjectClass *object_class = (GObjectClass *) klass;
|
|
|
|
|
WpObjectClass *wpobject_class = (WpObjectClass *) klass;
|
2020-07-29 19:27:40 +05:30
|
|
|
WpProxyClass *proxy_class = (WpProxyClass *) klass;
|
|
|
|
|
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
object_class->dispose = wp_impl_metadata_dispose;
|
|
|
|
|
|
|
|
|
|
wpobject_class->activate_execute_step =
|
|
|
|
|
wp_impl_metadata_activate_execute_step;
|
|
|
|
|
|
|
|
|
|
/* disable adding a listener for events */
|
2020-07-29 19:27:40 +05:30
|
|
|
proxy_class->pw_proxy_created = NULL;
|
lib: refactor WpProxy
This is an attempt to unclutter the API of WpProxy and
split functionality into smaller pieces, making it easier
to work with.
In this new class layout, we have the following classes:
- WpObject: base class for everything; handles activating
| and deactivating "features"
|- WpProxy: base class for anything that wraps a pw_proxy;
| handles events from pw_proxy and nothing more
|- WpGlobalProxy: handles integration with the registry
All the other classes derive from WpGlobalProxy. The reason
for separating WpGlobalProxy from WpProxy, though, is that
classes such as WpImplNode / WpSpaDevice can also derive from
WpProxy now, without interfacing with the registry.
All objects that come with an "info" structure and have properties
and/or params also implement the WpPipewireObject interface. This
provides the API to query properties and get/set params. Essentially,
this is implemented by all classes except WpMetadata (pw_metadata
does not have info)
This interface is implemented on each object separately, using
a private "mixin", which is a set of vfunc implementations and helper
functions (and macros) to facilitate the implementation of this interface.
A notable difference to the old WpProxy is that now features can be
deactivated, so it is possible to enable something and later disable
it again.
This commit disables modules, tests, tools, etc, to avoid growing the
patch more, while ensuring that the project compiles.
2020-11-10 19:17:02 +02:00
|
|
|
proxy_class->pw_proxy_destroyed = wp_impl_metadata_pw_proxy_destroyed;
|
2020-07-29 19:27:40 +05:30
|
|
|
}
|
|
|
|
|
|
2021-05-13 17:54:58 +03:00
|
|
|
/*!
|
2021-06-01 19:39:13 -04:00
|
|
|
* \brief Creates a new metadata implementation
|
2021-05-21 18:40:43 +03:00
|
|
|
* \ingroup wpmetadata
|
|
|
|
|
* \param core the core
|
|
|
|
|
* \returns (transfer full): a new WpImplMetadata
|
2021-05-13 17:54:58 +03:00
|
|
|
*/
|
2020-07-29 19:27:40 +05:30
|
|
|
WpImplMetadata *
|
|
|
|
|
wp_impl_metadata_new (WpCore * core)
|
|
|
|
|
{
|
|
|
|
|
g_return_val_if_fail (WP_IS_CORE (core), NULL);
|
|
|
|
|
|
|
|
|
|
return g_object_new (WP_TYPE_IMPL_METADATA,
|
2020-07-31 17:36:21 +03:00
|
|
|
"core", core,
|
|
|
|
|
NULL);
|
2021-05-21 18:40:43 +03:00
|
|
|
}
|