Re: [rox-devel] ROX-Session and D-BUS

[Guido S. <gu...@ar...>]

Am 11.04.2004 11:10:55 schrieb(en) Thomas Leonard:

> Some things which will hopefully one day be handled by the bus:
>=20
> - Notification of option changes (changing a value in one application
>   affects other instances).

Sounds like this would clash with gconfd. As dbus won't watch gconf =20
options directly, dbus can't obsolete gconfd without changing the =20
behaviour of the desktop. gconftool and GConf-Editor could send =20
messages over dbus, but what happens when the admin edits gconf options =20
manually? With gconfd instant apply is guaranteed, with dbus replacing =20
gconfd this will no longer work. That's not good enough a reason not to =20
drop gconfd though, IMHO. What is Gnome planning to do?


> The next step is to get ROX-Session to allow XSettings change =20
> requests
> through D-BUS, and then move those options into separate =20
> applications.
> As
> well as being easier to use, this will allow people to write extra
> applications to control new settings, without having to modify
> ROX-Session
> itself.

As this is not happening tomorrow, I'd still be thankfull if ROX-=20
Session would be enhanced to support the toolbar/menu xsetting. This is =20
good enough a reason for me to block ROX-Session xsettings in favour of =20
gnome-settings-daemon. gnome-settings-daemon has a few other nifty =20
features like applying gtk theme colours to Motif/Tk apps. I hope =20
someone implements that after the design change.=20