Skip to content

mumble-voip/mumble-plugin-cpp

Repository files navigation

mumble-plugin-cpp

A C++ wrapper for around the C plugin interface that was introduced with Mumble 1.4.0

What is it?

The aim of this wrapper is to provide an interface that feels "native" when using C++. Therefore it hides away the fact that the plugin API is actually a bunch of free C-functions by providing a C++ class MumblePlugin that can be used to implement the needed functionality using member functions.

On top of that some housekeeping has been automated within this class. For instance plugins implemented using this wrapper don't have to care about how to obtain the API functions used to interact with Mumble.

Speaking of API functions: There is also a C++ wrapper around the Mumble API functions (which originally are just a bunch of function pointers). This wrapper has the following features:

  • No need to pass the plugin's ID as a parameter for every API function call
  • No way to forget to check important error codes (the wrapper will throw exceptions of type MumbleAPIException if there is an error)
  • No need to worry about which returned values need to be freed after usage (smart-pointer-like MumbleResourceWrapper takes care of that)
  • No "out-params": All returned values are actual return values

How do I use it?

When using the wrapper all you have to do in order to create a plugin is to create a class that extends from MumblePlugin. You can then overwrite any of the virtual functions in order to hook into the respective callbacks. The API can be accessed via the m_api member variable.

Furthermore you have to implement MumblePlugin::getPlugin to return a reference to a static instance of your plugin class (which thereby effectively becomes a singleton):

MumblePlugin &MumblePlugin::getPlugin() noexcept {
    static MyPluginClass plugin;

    return plugin;
}

You also have to implement MumblePlugin::releaseResource which is a pure virtual function of the MumblePlugin class. If you are not allocating any resources that need freeing and that are passed to Mumble through the API boundary, you can use a no-op implementation like this:

void <YourPluginClass>::releaseResource(const void *ptr) noexcept {
    // We will terminate here as any call to this function means that there is indeed some resource that needs
    // freeing contradicting our no-op assumption for this function
    std::terminate();
} 

By default only a small subset of functionality is available for you to implement. If you want to implement any of the missing functions, you can set the following cmake-variables:

  • positional-audio
  • server-event-callbacks
  • audio-callbacks
  • plugin-data-callbacks
  • key-event-callbacks
  • plugin-update

Additionally you can also use these meta-variables: all-callbacks, all-features

Finally you have to link to the mumble_plugin_cpp_wrapper target from cmake like this:

target_link_libraries(<yourTargetHere> PRIVATE mumble_plugin_cpp_wrapper)

You can have a look at the example plugin in order to check out a basic example that should get you started writing your own plugins.

Requirements

In order to use the wrapper, you need to have

  • A compiler that is iso-C++17 conform
  • cmake v3.0 or newer

Other than that there are no further dependencies of the wrapper.

About

A C++ wrapper for around the C plugin interface that was introduced with Mumble 1.4.0

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

Packages

No packages published