Skip to content
Snippets Groups Projects
  • George Kiagiadakis's avatar
    2f3f5f8e
    lib: refactor WpProxy · 2f3f5f8e
    George Kiagiadakis authored
    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.
    2f3f5f8e
    History
    lib: refactor WpProxy
    George Kiagiadakis authored
    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.