[Bug 732007] New: Rename GstGlobalDeviceMonitor

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=732007
  GStreamer | gstreamer (core) | git

           Summary: Rename GstGlobalDeviceMonitor
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


What we have now:

GstDevice - ok
GstDeviceMonitor - plugin/device/API-specific monitor singleton for certain
types of devices
GstDeviceMonitorFactory - plugin feature for device monitor
GstGlobalDeviceMonitor - creates one or more DeviceMonitors based on filter
criterion, for use by applications

The naming of GstGlobalDeviceMonitor is unfortunate in two ways:

 -  it sounds like a single one-to-rule-them-all object,
     but it's not; to monitor different device classes,
     one might have to create multiple GlobalDeviceMonitors
     in an application.

 - (app) people intuitively just use GstDeviceMonitor for
    their needs, and then find things awfully complicated
    (because they are supposed to use the Global one for
    the filtering)

We haven't had much success in finding a better name for GlobalDeviceMonitor.

The other option is then to rename the plugin implementations
GstDeviceMonitor/GstDeviceMonitorFactory to something else, and rename
GstGlobalDeviceMonitor to GstDeviceMonitor.

For the monitoring backends we could use e.g.
GstDeviceProbe/GstDeviceProbeFactory or
GstDeviceDiscoverer/GstDeviceDiscovererFactory. Both seemed ok to Olivier.

I think I'd lean towards Discoverer, because Probe sounds more like a
single-shot thing.

Any preferences/opinions/additional suggestions?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.