From: Guido S. <__g...@we...> - 2006-05-12 11:54:59
|
Hi, Attached is a patch for ROX-Session. The patch adds code to control gamma and screensaver settings. Due to size limitations for mails I'm sending the updated Gamma, Appearance and Font configlets separately. Gamma is my own version - not Thomas's - with reference bitmaps above the sliders. 'Appearance' is 'Theme' and 'Toolbars&Menus' joined. There is one problem with screensaver settings: BlankTime <= DPMSStandby <= DPMSSuspend <= ROX/DPMSOff needs to be enforced somehow. When I cleared DPMSSuspend or DPMSStandby - don't recall - in order to type in a new number, ROX-Session at one time even crashed, although I can't reproduce now. Instant apply makes this a bit tricky to do. Currently only blanking is supported, no 'XScreensaver hacks'. I personally don't use fancy screensavers, so I'm not terribly motivated myself to add support for flying toasters and stuff. PS: The configlets on the ROX site were still my old now disfunct ones, when I downloaded them a few days ago. The attached configlets I created from the ones from Tony's site. Please replace 'Keyboard' and 'Mouse' with Tony's. I haven't included them here, as I have done no changes of my own to them yet. |
From: Thomas L. <ta...@ec...> - 2006-05-13 09:48:37
|
On Fri, 12 May 2006 13:54:06 +0000, Guido Schimmels wrote: > Hi, > > Attached is a patch for ROX-Session. Can't see any patch here... > The patch adds code to control gamma and screensaver settings. > > Due to size limitations for mails I'm sending the updated > Gamma, Appearance and Font configlets separately. Please feel free to upload the patches and configlets to the file releases page and/or commit them and the patches to subversion! You should have permission already. Thanks, -- Dr Thomas Leonard http://rox.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Guido S. <__g...@we...> - 2006-05-13 14:04:11
Attachments:
ROX-Session.diff
|
On Sat, 13 May 2006 10:51:24 +0100 Thomas Leonard <ta...@ec...> wrote: > On Fri, 12 May 2006 13:54:06 +0000, Guido Schimmels wrote: > > > Hi, > > > > Attached is a patch for ROX-Session. > > Can't see any patch here... Sent it with another post, which hasn't arrived. Hope this one does. |
From: Ken H. <ke...@ha...> - 2006-05-16 14:03:45
|
On May 13, 2006, at 9:03 AM, Guido Schimmels wrote: > On Sat, 13 May 2006 10:51:24 +0100 > Thomas Leonard <ta...@ec...> wrote: > >> On Fri, 12 May 2006 13:54:06 +0000, Guido Schimmels wrote: >> >>> Hi, >>> >>> Attached is a patch for ROX-Session. >> >> Can't see any patch here... > > Sent it with another post, which hasn't arrived. > Hope this one does. > <ROX-Session.diff> ROX-Session currently has to do a lot of things with these settings. Wouldn't a more modular approach be better? Should Session call external modules (part of the configlets but with no UI?) to actually save/restore these settings? Could we have some kind of registration process so nothing would have to be hard-coded in Session? Just a thought. |
From: Thomas L. <ta...@ec...> - 2006-05-21 18:11:33
|
On Tue, 16 May 2006 07:03:34 -0700, Ken Hayber wrote: [...] > ROX-Session currently has to do a lot of things with these settings. > Wouldn't a more modular approach be better? Should Session call > external modules (part of the configlets but with no UI?) to actually > save/restore these settings? Really, ROX-Session shouldn't be involved in this process at all. What we actually want is a decent configuration system that the configlets and the windowing system talk to directly. That's a way off, though. I guess it depends how many more settings we need to cope with... surely we're nearing the limit of the number of things you can set on the X server? If not, your modules idea does sound like a possible plan. Maybe having a '~/.config/rox.sourceforge.net/ROX-Session/plugins.d' directory is the answer? -- Dr Thomas Leonard http://rox.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Guido S. <__g...@we...> - 2006-05-21 19:48:56
|
On Sun, 21 May 2006 19:14:29 +0100 Thomas Leonard <ta...@ec...> wrote: > On Tue, 16 May 2006 07:03:34 -0700, Ken Hayber wrote: > [...] > > ROX-Session currently has to do a lot of things with these settings. > > Wouldn't a more modular approach be better? Should Session call > > external modules (part of the configlets but with no UI?) to actually > > save/restore these settings? > > Really, ROX-Session shouldn't be involved in this process at all. What we > actually want is a decent configuration system that the configlets and the > windowing system talk to directly. A question about xsettings. Have those to be "hold" by a process and become invalid when this process stops or are the settings kept in the X server independently? What I mean, does the XSettings system really need a running xsettings-manager process? > That's a way off, though. I guess it depends how many more settings we > need to cope with... surely we're nearing the limit of the number of > things you can set on the X server? The keyboard bell and a few GTK/XSettings is what comes to my mind. I would like to see some Qt support for application font and colour scheme settings e.g. Not hard, but couldn't motivate myself so far. > If not, your modules idea does sound like a possible plan. Maybe having a > '~/.config/rox.sourceforge.net/ROX-Session/plugins.d' directory is the > answer? That would be usefull in any case. |
From: Ken H. <ke...@ha...> - 2006-05-21 22:34:46
|
Guido Schimmels wrote: > On Sun, 21 May 2006 19:14:29 +0100 > Thomas Leonard <ta...@ec...> wrote: > > >> On Tue, 16 May 2006 07:03:34 -0700, Ken Hayber wrote: >> [...] >> >>> ROX-Session currently has to do a lot of things with these settings. >>> Wouldn't a more modular approach be better? Should Session call >>> external modules (part of the configlets but with no UI?) to actually >>> save/restore these settings? >>> >> Really, ROX-Session shouldn't be involved in this process at all. What we >> actually want is a decent configuration system that the configlets and the >> windowing system talk to directly. >> > > A question about xsettings. Have those to be "hold" by a process and become > invalid when this process stops or are the settings kept in the X server independently? > What I mean, does the XSettings system really need a running xsettings-manager > process? > > >> That's a way off, though. I guess it depends how many more settings we >> need to cope with... surely we're nearing the limit of the number of >> things you can set on the X server? >> > > The keyboard bell and a few GTK/XSettings is what comes to my mind. > I would like to see some Qt support for application font and colour scheme settings e.g. > Not hard, but couldn't motivate myself so far. > > > >> If not, your modules idea does sound like a possible plan. Maybe having a >> '~/.config/rox.sourceforge.net/ROX-Session/plugins.d' directory is the >> answer? >> > > That would be usefull in any case. > So we'd need a plugin api that does something like this... Startup: 1) during load_settings() iterate through the plugins.d and import each file. 2) call plugin.register() to register which XSettings (or ROX settings?) this plugin handles. 3) for each setting in the xml file, call the plugin's set function for that setting passing the saved value. On Notify/Update (?) 1) call the plugin's set function again, passing the new value. Saving works the same as it does now? (e.g. the plugin does not have to be involved?) Do we need a get function? Should the configlets register a plugin (copy/link to the plugins.d) when first run? Or do we want a separate package for UI and plugin? Is there a point to having the plugin with no UI? |
From: Thomas L. <ta...@ec...> - 2006-05-27 18:54:38
|
On Sun, 21 May 2006 21:45:35 +0000, Guido Schimmels wrote: > On Sun, 21 May 2006 19:14:29 +0100 > Thomas Leonard <ta...@ec...> wrote: [...] >> Really, ROX-Session shouldn't be involved in this process at all. What >> we actually want is a decent configuration system that the configlets >> and the windowing system talk to directly. > > A question about xsettings. Have those to be "hold" by a process and > become invalid when this process stops or are the settings kept in the X > server independently? What I mean, does the XSettings system really need a > running xsettings-manager process? The spec says that applications should revert to defaults when the settings manager exits. >> That's a way off, though. I guess it depends how many more settings we >> need to cope with... surely we're nearing the limit of the number of >> things you can set on the X server? > > The keyboard bell and a few GTK/XSettings is what comes to my mind. I > would like to see some Qt support for application font and colour scheme > settings e.g. Not hard, but couldn't motivate myself so far. Does the Qt stuff use XSettings? Things that can be set with gconf or similar (what does KDE use?) don't need to involve ROX-Session at all. -- Dr Thomas Leonard http://rox.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Guido S. <__g...@we...> - 2006-05-28 09:19:47
|
On Sat, 27 May 2006 19:57:48 +0100 Thomas Leonard <ta...@ec...> wrote: > On Sun, 21 May 2006 21:45:35 +0000, Guido Schimmels wrote: > > On Sun, 21 May 2006 19:14:29 +0100 > > Thomas Leonard <ta...@ec...> wrote: > > A question about xsettings. Have those to be "hold" by a process and > > become invalid when this process stops or are the settings kept in the X > > server independently? What I mean, does the XSettings system really need a > > running xsettings-manager process? > > The spec says that applications should revert to defaults when the > settings manager exits. Ok, so a running process is needed. > >> That's a way off, though. I guess it depends how many more settings we > >> need to cope with... surely we're nearing the limit of the number of > >> things you can set on the X server? > > > > The keyboard bell and a few GTK/XSettings is what comes to my mind. I > > would like to see some Qt support for application font and colour scheme > > settings e.g. Not hard, but couldn't motivate myself so far. > > Does the Qt stuff use XSettings? Things that can be set with gconf or > similar (what does KDE use?) don't need to involve ROX-Session at all. According to freedesktop.org only gtk is using xsettings really, so it's not really a standard in a practical sense. Qt uses ~/.qt/qtrc analagous to ~/.gtkrc, altough qtrc is ini-style. Qt ships with qtconfig, a C++ GUI config tool for ~/.qt/qtrc. But qtrc is ignored/overruled in favour of KDE's KConf settings, when running from within the KDE session manager. Same like gtkrc is ignored within a Gnome session. But for ROX users ~/.qt/qtrc is still relevant for plain Qt apps at least. |