4 commits

Author	SHA1	Message	Date
Wim Taymans	8ea78c2e3f	pw_core -> pw_context ... The proxy API is the one that we would like to expose for applications and the other API is used internally when implementing modules or factories. The current pw_core object is really a context for all objects so name it that way. It also makes it possible to rename pw_core_proxy to pw_proxy later.	2019-12-10 18:19:56 +01:00
Wim Taymans	ca6f1bd2f1	remote: remove the remote ... Mostly rename pw_remote_* to pw_core_proxy_*	2019-12-06 13:40:23 +01:00
Wim Taymans	8a959ea7a1	core_proxy: prepare to rename pw_remote -> pw_core_proxy ... The pw_remote object is really a wrapper around the pw_core_proxy. The events it emits are also available in the core proxy and are generally awkward to use. With some clever new pw_core_proxy_* methods and a pw_core_connect to create the core_proxy, we can convert all code away from pw_remote. This is a first step in this conversion, using the pw_remote behind the scenes. It leaks into some places because it really needs to become its own struct in a next step.	2019-12-06 11:48:40 +01:00
Julian Bouzas	ef94b5c345	tools: add new pipewire-dot tool to generate a global objects dot graph	2019-11-19 15:41:50 +01:00