Take for example the slideshow theme engine. In many cases it makes sense to have multiple themes for the same theme engine. And in the case where no one set of defaults will work it is now possible to simply provide a related theme of a different name. It demands that themes simply work and that the defaults make sense. So, why use a design that separates the theme from the theme engine? There are many reasons for this approach. So, perhaps, a better question is how does one create a new theme for a pre-existing theme engine? For that please see the related section in this FAQ. Each gnome-screensaver theme is a combination of a "hack" (or theme engine) and a set of options. A gnome-screensaver theme is not directly equivalent to the xscreensaver concept of a "hack". We are trying to take a different approach. Why doesn't the screensaver preferences tool allow me to change the settings for the theme? desktop files using the migrate-xscreensaver-config.sh script in the data directory of the gnome-screensaver sources has since been removed, see. Xscreensaver XML configuration files can be converted into. Gnome-screensaver uses standard desktop entry (.desktop) files to define the screensaver themes. How come my xscreensaver "hacks" don't show up in the gnome-screensaver configuration tool? Any screensaver theme engines that support using the environment variable XSCREENSAVER_WINDOW should work without modification.Īctually, that seems to no longer be the case in GNOME3, after commit 76d2c9ff6acf4a98bfa1569a62fafe14e89f413e gnome-screensaver only seems to support blanking. The actual code paths through these libraries are quite small and very well tested.Ĭan I use xscreensaver "hacks" with gnome-screensaver? These libraries are a result of using DBUS, GTK+, and GConf. gnome-screensaver links to many more libraries than does xscreensaver. The screensaver daemon is currently using the GTK+ implementation of the XEmbed protocol. This way there is no transfer of grabs to cause a race condition. It maintains a keyboard grab on the toplevel window at all times. gnome-screensaver runs the screen lock password dialog in a separate process and embeds the interface using XEmbed. translation into many languages by the GNOME Translation Project.integration with the desktop (themes, fonts, toolkit). a separation between the screensaver theme engine and the theme settings. a secure separation of user input processing and authentication from the screen locking window.allowing a system administrator to set a mandatory policy for any setting.switching users directly from the unlock dialog.a desktop neutral and standard way to install and manage screensaver themes.a desktop neutral control interface via DBus.It simplifies and streamlines the experience for the user and provides more capability for the system administrator and vendor. It is designed to integrate well with the desktop and provide a control interface that is desktop neutral. Gnome-screensaver is a new screensaver that can replace xscreensaver. Why gnome-screensaver, what happened to xscreensaver?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |