~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon:wip/settings-relocation

Last commit made on 2015-01-15
Get this branch:
git clone -b wip/settings-relocation https://git.launchpad.net/~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Branch merges

Branch information

Name:
wip/settings-relocation
Repository:
lp:~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Recent commits

de8363a... by Carlos Garnacho

common: Migrate input settings to gsettings-desktop-schemas keys

The deprecated keys are kept in isolated ".deprecated" suffixed schemas.
On plugin startup, the settings-daemon paths are opened with these legacy
schemas, and all user-modified keys are dumped to the new location and
reset.

This ensures the transition just happens once per-key, and ensures the
dconf database is left clean.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

d432d4e... by Carlos Garnacho

mouse: Use gsettings-desktop-schemas mouse/touchpad settings

Most settings have been moved there, so make this plugin use the new
schemas for the handled settings, and remain using the settings-daemon
schema for settings that can just be honored on X11.

In order to simplify the situation for the future, the management of
"middle-button-enabled", "horiz-scroll-enabled" and "disable-while-typing"
settings have been removed, and the sane default is applied on non-libinput
devices on X11.

For all other settings, the mouse plugin has been made to ignore devices
created through the libinput driver, as mutter handles these.

Additionally, the entire plugin is disabled on Wayland, the settings
remaining in g-s-d schemas are not a thing there.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

6fc7a6c... by Carlos Garnacho

keyboard: Apply numlock/bell settings on X11 only.

These are not a windowing/desktop thing on wayland, so just ignore these
there at the moment.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

9626ffd... by Carlos Garnacho

keyboard: Remove handling of keyboard repeat settings

With patches from bug #739397 applied. This is managed by mutter on X11
too, so no need to do it here again.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

a012d1b... by Carlos Garnacho

common: Add xdevice_is_libinput()

This function pokes a libinput-driver-specific property, and can be used to
find out whether a device uses the libinput driver or not.

This will be used to determine whether a device is to be managed by mutter,
or by g-s-d itself.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

5bea224... by Carlos Garnacho

schemas: Remove "display" setting from wacom devices' schema

This is part now of org.gnome.desktop.peripherals.[tablet|touchscreen],
in use now by g-s-d.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

01697a4... by Carlos Garnacho

wacom: Remove some dead code from GsdWacomDevice

The direct usage of GsdDeviceMapper allows us to remove some code here.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

bff3b07... by Carlos Garnacho

common: Make GsdDeviceMapper use devices from GsdDeviceManager

This has brought some changes in the xrandr and wacom modules, which now
use GsdDevice for device mapping.

The use of GdkDevices and XInput properties remain for these settings not
yet in the gsettings-desktop-schemas peripherals settings in the wacom case,
and those bits have been made to run only on X11 as expected.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

c2b6967... by Carlos Garnacho

power: Restrict disabling of touchscreens/tablets to X11

This should be eventually done by the compositor. In the mean time, restrict
it to X11, and remove the GsdDeviceMapper usage, as it's not strictly
necessary.

https://bugzilla.gnome.org/show_bug.cgi?id=742593

d6cc1d2... by Carlos Garnacho

common: Add X11-based GsdDeviceManager implementation

This will be used on X11 environments, poking device capabilities
through device properties. This will be the default backend on
X11.

https://bugzilla.gnome.org/show_bug.cgi?id=742593