From 28a029a4990d2a84f9d6a0b890eba812ea503998 Mon Sep 17 00:00:00 2001 From: Perberos Date: Thu, 1 Dec 2011 23:52:01 -0300 Subject: moving from https://github.com/perberos/mate-desktop-environment --- src/marco.schemas.in.in | 573 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 573 insertions(+) create mode 100644 src/marco.schemas.in.in (limited to 'src/marco.schemas.in.in') diff --git a/src/marco.schemas.in.in b/src/marco.schemas.in.in new file mode 100644 index 00000000..acd342b4 --- /dev/null +++ b/src/marco.schemas.in.in @@ -0,0 +1,573 @@ + + + + + + + /schemas/apps/marco/general/mouse_button_modifier + /apps/marco/general/mouse_button_modifier + marco + string + <Alt> + + Modifier to use for modified window click actions + + Clicking a window while holding down this modifier key + will move the window (left click), resize the window + (middle click), or show the window menu (right click). + The middle and right click operations may be swapped + using the "resize_with_right_button" key. + Modifier is expressed as "<Alt>" or "<Super>" + for example. + + + + + + /schemas/apps/marco/general/resize_with_right_button + /apps/marco/general/resize_with_right_button + marco + bool + true + + Whether to resize with the right button + + Set this to true to resize with the right button and show a menu + with the middle button while holding down the key given in + "mouse_button_modifier"; set it to false to make it work the + opposite way around. + + + + + + /schemas/apps/marco/general/button_layout + /apps/marco/general/button_layout + marco + string + menu:minimize,maximize,close + + Arrangement of buttons on the titlebar + + Arrangement of buttons on the titlebar. The + value should be a string, such as + "menu:minimize,maximize,spacer,close"; the colon separates the + left corner of the window from the right corner, and + the button names are comma-separated. Duplicate buttons + are not allowed. Unknown button names are silently ignored + so that buttons can be added in future marco versions + without breaking older versions. + A special spacer tag can be used to insert some space between + two adjacent buttons. + + + + + + /schemas/apps/marco/general/focus_mode + /apps/marco/general/focus_mode + marco + string + click + + Window focus mode + + The window focus mode indicates how windows are activated. + It has three possible values; "click" means windows must + be clicked in order to focus them, "sloppy" means windows + are focused when the mouse enters the window, and "mouse" means + windows are focused when the mouse enters the window and + unfocused when the mouse leaves the window. + + + + + + /schemas/apps/marco/general/focus_new_windows + /apps/marco/general/focus_new_windows + marco + string + smart + + Control how new windows get focus + + This option provides additional control over how newly created + windows get focus. It has two possible values; "smart" applies + the user's normal focus mode, and "strict" results in windows + started from a terminal not being given focus. + + + + + + /schemas/apps/marco/general/raise_on_click + /apps/marco/general/raise_on_click + marco + bool + true + + Whether raising should be a side-effect of other user + interactions + + Setting this option to false can lead to buggy behavior, so + users are strongly discouraged from changing it from the default + of true. + + Many actions (e.g. clicking in the client area, moving or resizing the window) + normally raise the window as a side-effect. Setting this option to false, which + is strongly discouraged, will decouple raising from other user actions, and + ignore raise requests generated by applications. See + http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6. + Even when this option is false, windows can + still be raised by an alt-left-click anywhere on the window, a + normal click on the window decorations, or by special messages + from pagers, such as activation requests from tasklist applets. + This option is currently disabled in click-to-focus mode. + + Note that the list of ways to raise windows when raise_on_click + is false does not include programmatic requests from + applications to raise windows; such requests will be ignored + regardless of the reason for the request. If you are an + application developer and have a user complaining that your + application does not work with this setting disabled, tell them + it is _their_ fault for breaking their window manager and that + they need to change this option back to true or live with the + "bug" they requested. + + + + + + /schemas/apps/marco/general/action_double_click_titlebar + /apps/marco/general/action_double_click_titlebar + marco + string + toggle_maximize + + Action on title bar double-click + + This option determines the effects of double-clicking on the + title bar. Current valid options are + 'toggle_shade', which will shade/unshade the window, + 'toggle_maximize' which will maximize/unmaximize the window, + 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' + which will maximize/unmaximize the window in that direction only, + 'minimize' which will minimize the window, + 'shade' which will roll the window up, + 'menu' which will display the window menu, + 'lower' which will put the window behind all the others, + and 'none' which will not do anything. + + + + + + /schemas/apps/marco/general/action_middle_click_titlebar + /apps/marco/general/action_middle_click_titlebar + marco + string + lower + + Action on title bar middle-click + + This option determines the effects of middle-clicking on the + title bar. Current valid options are + 'toggle_shade', which will shade/unshade the window, + 'toggle_maximize' which will maximize/unmaximize the window, + 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' + which will maximize/unmaximize the window in that direction only, + 'minimize' which will minimize the window, + 'shade' which will roll the window up, + 'menu' which will display the window menu, + 'lower' which will put the window behind all the others, + and 'none' which will not do anything. + + + + + + /schemas/apps/marco/general/action_right_click_titlebar + /apps/marco/general/action_right_click_titlebar + marco + string + menu + + Action on title bar right-click + + This option determines the effects of right-clicking on the + title bar. Current valid options are + 'toggle_shade', which will shade/unshade the window, + 'toggle_maximize' which will maximize/unmaximize the window, + 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' + which will maximize/unmaximize the window in that direction only, + 'minimize' which will minimize the window, + 'shade' which will roll the window up, + 'menu' which will display the window menu, + 'lower' which will put the window behind all the others, + and 'none' which will not do anything. + + + + + + /schemas/apps/marco/general/auto_raise + /apps/marco/general/auto_raise + marco + bool + false + + Automatically raises the focused window + + If set to true, and the focus mode is either "sloppy" or "mouse" + then the focused window will be automatically raised after a + delay specified by the auto_raise_delay key. This is not related + to clicking on a window to raise it, nor to entering a window + during drag-and-drop. + + + + + + /schemas/apps/marco/general/auto_raise_delay + /apps/marco/general/auto_raise_delay + marco + int + 500 + + Delay in milliseconds for the auto raise option + + The time delay before raising a window if auto_raise is set to + true. The delay is given in thousandths of a second. + + + + + + /schemas/apps/marco/general/theme + /apps/marco/general/theme + marco + string + Spidey-Left + + Current theme + + The theme determines the appearance of window borders, + titlebar, and so forth. + + + + + + /schemas/apps/marco/general/titlebar_uses_system_font + /apps/marco/general/titlebar_uses_system_font + marco + bool + false + + Use standard system font in window titles + + If true, ignore the titlebar_font + option, and use the standard application font for window + titles. + + + + + + /schemas/apps/marco/general/titlebar_font + /apps/marco/general/titlebar_font + marco + string + Sans Bold 10 + + Window title font + + A font description string describing a font for window + titlebars. The size from the description will only be used if the + titlebar_font_size option is set to 0. Also, this option is + disabled if the titlebar_uses_desktop_font option is set to true. + + + + + + /schemas/apps/marco/general/num_workspaces + /apps/marco/general/num_workspaces + marco + int + 4 + + Number of workspaces + + Number of workspaces. Must be more than zero, and has a fixed + maximum to prevent making the desktop unusable by accidentally + asking for too many workspaces. + + + + + + /schemas/apps/marco/general/visual_bell + /apps/marco/general/visual_bell + marco + bool + false + + Enable Visual Bell + + Turns on a visual indication when an application or the system + issues a 'bell' or 'beep'; useful for the hard-of-hearing and for + use in noisy environments. + + + + + + /schemas/apps/marco/general/audible_bell + /apps/marco/general/audible_bell + marco + bool + true + + System Bell is Audible + + Determines whether applications or the system can generate + audible 'beeps'; may be used in conjunction with 'visual bell' to + allow silent 'beeps'. + + + + + + /schemas/apps/marco/general/visual_bell_type + /apps/marco/general/visual_bell_type + marco + string + fullscreen + + Visual Bell Type + + Tells Marco how to implement the visual indication that the + system bell or another application 'bell' indicator has been + rung. Currently there are two valid values, "fullscreen", which + causes a fullscreen white-black flash, and "frame_flash" which + causes the titlebar of the application which sent the bell signal + to flash. If the application which sent the bell is unknown (as + is usually the case for the default "system beep"), the currently + focused window's titlebar is flashed. + + + + + + /schemas/apps/marco/general/compositing_manager + /apps/marco/general/compositing_manager + marco + bool + false + + Compositing Manager + + Determines whether Marco is a compositing manager. + + + + + + /schemas/apps/marco/workspace_names/name + /apps/marco/workspace_names/name_1 + /apps/marco/workspace_names/name_2 + /apps/marco/workspace_names/name_3 + /apps/marco/workspace_names/name_4 + /apps/marco/workspace_names/name_5 + /apps/marco/workspace_names/name_6 + /apps/marco/workspace_names/name_7 + /apps/marco/workspace_names/name_8 + /apps/marco/workspace_names/name_9 + /apps/marco/workspace_names/name_10 + /apps/marco/workspace_names/name_11 + /apps/marco/workspace_names/name_12 + /apps/marco/workspace_names/name_13 + /apps/marco/workspace_names/name_14 + /apps/marco/workspace_names/name_15 + /apps/marco/workspace_names/name_16 + marco + string + + + Name of workspace + + The name of a workspace. + + + + + + /schemas/apps/marco/general/reduced_resources + /apps/marco/general/reduced_resources + marco + bool + false + + If true, trade off usability for less resource usage + + If true, marco will give the user less feedback by using + wireframes, avoiding animations, or other means. This is a + significant reduction in usability for many users, but may allow + legacy applications to continue working, and may also be a + useful tradeoff for terminal servers. However, the wireframe + feature is disabled when accessibility is on. + + + + + + + + /schemas/apps/marco/global_keybindings/run_command + /apps/marco/global_keybindings/run_command_1 + /apps/marco/global_keybindings/run_command_2 + /apps/marco/global_keybindings/run_command_3 + /apps/marco/global_keybindings/run_command_4 + /apps/marco/global_keybindings/run_command_5 + /apps/marco/global_keybindings/run_command_6 + /apps/marco/global_keybindings/run_command_7 + /apps/marco/global_keybindings/run_command_8 + /apps/marco/global_keybindings/run_command_9 + /apps/marco/global_keybindings/run_command_10 + /apps/marco/global_keybindings/run_command_11 + /apps/marco/global_keybindings/run_command_12 + marco + string + disabled + + Run a defined command + + The keybinding that runs the correspondingly-numbered + command in /apps/marco/keybinding_commands + + The format looks like "<Control>a" or + "<Shift><Alt>F1". + + The parser is fairly liberal and allows lower or upper case, + and also abbreviations such as "<Ctl>" and + "<Ctrl>". If you set the option to the special string + "disabled", then there will be no keybinding for this + action. + + + + + + /schemas/apps/marco/keybinding_commands/command + /apps/marco/keybinding_commands/command_1 + /apps/marco/keybinding_commands/command_2 + /apps/marco/keybinding_commands/command_3 + /apps/marco/keybinding_commands/command_4 + /apps/marco/keybinding_commands/command_5 + /apps/marco/keybinding_commands/command_6 + /apps/marco/keybinding_commands/command_7 + /apps/marco/keybinding_commands/command_8 + /apps/marco/keybinding_commands/command_9 + /apps/marco/keybinding_commands/command_10 + /apps/marco/keybinding_commands/command_11 + /apps/marco/keybinding_commands/command_12 + marco + string + + + Commands to run in response to keybindings + + The /apps/marco/global_keybindings/run_command_N + keys define keybindings that correspond to these commands. + Pressing the keybinding for run_command_N will + execute command_N. + + + + + + /schemas/apps/marco/keybinding_commands/command_screenshot + /apps/marco/keybinding_commands/command_screenshot + marco + string + mate-screenshot + + The screenshot command + + The /apps/marco/global_keybindings/run_command_screenshot + key defines a keybinding which causes the command specified + by this setting to be invoked. + + + + + + /schemas/apps/marco/keybinding_commands/command_window_screenshot + /apps/marco/keybinding_commands/command_window_screenshot + marco + string + mate-screenshot --window + + The window screenshot command + + The /apps/marco/global_keybindings/run_command_window_screenshot + key defines a keybinding which causes the command specified + by this setting to be invoked. + + + + + + + + + + + /schemas/apps/marco/general/application_based + /apps/marco/general/application_based + marco + bool + false + + (Not implemented) Navigation works in terms of applications not windows + + If true, then Marco works in terms of applications rather than + windows. The concept is a bit abstract, but in general an + application-based setup is more like the Mac and less like + Windows. When you focus a window in application-based mode, all + the windows in the application will be raised. Also, in + application-based mode, focus clicks are not passed through to + windows in other applications. Application-based mode is, + however, largely unimplemented at the moment. + + + + + + /schemas/apps/marco/general/disable_workarounds + /apps/marco/general/disable_workarounds + marco + bool + false + + Disable misfeatures that are required by old or broken + applications + + Some applications disregard specifications in ways that result in + window manager misfeatures. This option puts Marco in a + rigorously correct mode, which gives a more consistent user + interface, provided one does not need to run any misbehaving + applications. + + + + + + + + + + -- cgit v1.2.1