mirrors/labwc
1
0
Fork 0
mirror of https://github.com/labwc/labwc.git synced 2025-10-29 05:40:24 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
labwc/docs/themerc

127 lines
4 KiB
Text
Raw Normal View History

theme: support theme setting override ...by reading <config-dir>/themerc-override where <config-dir> is normally $HOME/.config/labwc can be other locations as described in labwc-config(5) and can also be specified by the command line option -C. The reason for supporting theme override is to give users more fine- grained control of settings without making local copies and modifying themes.
2022-12-05 21:46:16 +00:00
# This file contains all themerc options with default values
#
# System-wide and local themes can be overridden by creating a copy of this
# file and renaming it to $HOME/.config/labwc/themerc-override. Be careful
# though - if you only want to override a small number of specific options,
# make sure all other lines are commented out or deleted.
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
# general
border.width: 1
theme: add window.titlebar.padding.{width,height} ...to replace padding.{width,height} to minimize breaking changes with the visual appearance of the titlebar. With the diverging labwc specification for the titlebar (listed below) we have to choose between (a) not supporting the padding.{width,height} option which exist in many extant Openbox themes to keep titlebar height (almost) the same; or (b) making the allocated button areas much smaller and not keeping the default hover going all the way to the edges. All in all it just seems a lot simpler and cleaner to break this link to the openbox spec. Examples of previous change driving the requirement for this change: - SVG and PNG support which often results in large icons with hover effects. - Theme option window.button.{height,width} - Larger default areas for icons (26x26) In way of an example, Numix theme sets a padding.height of 6 which would have resulted in a titlebar 12px taller without this change.
2024-10-08 17:52:57 +01:00
#
docs: replace two 'we's with passive forms To match the common style in docs/
2024-10-21 23:35:49 +03:00
# The global padding.{width,height} of openbox are not supported because
# the default labwc button geometry deviates from that of openbox
theme: add window.titlebar.padding.{width,height} ...to replace padding.{width,height} to minimize breaking changes with the visual appearance of the titlebar. With the diverging labwc specification for the titlebar (listed below) we have to choose between (a) not supporting the padding.{width,height} option which exist in many extant Openbox themes to keep titlebar height (almost) the same; or (b) making the allocated button areas much smaller and not keeping the default hover going all the way to the edges. All in all it just seems a lot simpler and cleaner to break this link to the openbox spec. Examples of previous change driving the requirement for this change: - SVG and PNG support which often results in large icons with hover effects. - Theme option window.button.{height,width} - Larger default areas for icons (26x26) In way of an example, Numix theme sets a padding.height of 6 which would have resulted in a titlebar 12px taller without this change.
2024-10-08 17:52:57 +01:00
#
window.titlebar.padding.width: 0
window.titlebar.padding.height: 0
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
# window border
theme: set default values of window.*.border.color to #aaaaaa This makes the colors of titlebar and window borders different, but will let menu.border.color (which will be supported soon) inherit window.active.border.color just like Openbox does, without making the menu borders around a selected menu item invisible.
2024-11-24 14:39:35 +09:00
window.active.border.color: #aaaaaa
window.inactive.border.color: #aaaaaa
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
ToggleKeybinds per window
2023-03-05 10:35:56 +01:00
# ToggleKeybinds status indicator
window.active.indicator.toggled-keybind.color: #ff0000
docs/themerc: add missing theme options
2021-10-20 19:52:17 +01:00
# window titlebar background
use the GTK+ 3 notebook header color as the default active title color
2023-11-28 08:22:54 +02:00
window.active.title.bg.color: #e1dedb
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
window.inactive.title.bg.color: #f6f5f4
docs: document gradients (v2: small fixes)
2025-06-14 12:36:51 -04:00
window.*.title.bg: Solid
# Vertical and SplitVertical gradients are supported for window.*.title.bg
# with the following additional color fields. See labwc-theme(5) for examples.
#
# window.*.title.bg.colorTo:
# window.*.title.bg.color.splitTo:
# window.*.title.bg.colorTo.splitTo:
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
docs/themerc: add missing theme options
2021-10-20 19:52:17 +01:00
# window titlebar text
window.active.label.text.color: #000000
window.inactive.label.text.color: #000000
theme: change window.label.text.justify default to center It just looks better :)
2022-04-22 17:54:20 +01:00
window.label.text.justify: center
docs/themerc: add missing theme options
2021-10-20 19:52:17 +01:00
theme: add button padding and spacing (#2127) While at it, separate corner width from button width. Both are independed and having them separately improves readability.
2024-09-09 17:43:38 +02:00
# window button width and spacing
theme: allow to set window button size (#1965) This commit introduces new option "window.button.width". Despite the name it currently affects both width and height.
2024-07-20 11:33:57 +03:00
window.button.width: 26
theme: tidy up documentation
2024-10-13 20:43:18 +01:00
window.button.height: 26
theme: add button padding and spacing (#2127) While at it, separate corner width from button width. Both are independed and having them separately improves readability.
2024-09-09 17:43:38 +02:00
window.button.spacing: 0
theme: allow to set window button size (#1965) This commit introduces new option "window.button.width". Despite the name it currently affects both width and height.
2024-07-20 11:33:57 +03:00
theme: add circle button hover effect (#2127)
2024-09-09 17:44:03 +02:00
# window button hover effect
theme: replace *.hover.bg.shape with *.hover.bg.corner-radius
2024-10-12 15:06:23 +09:00
window.button.hover.bg.corner-radius: 0
theme: add circle button hover effect (#2127)
2024-09-09 17:44:03 +02:00
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
# window buttons
window.active.button.unpressed.image.color: #000000
themerc: fix syntax inconsistency
2021-03-04 20:30:23 +00:00
window.inactive.button.unpressed.image.color: #000000
theme: set sane values if no theme found
2020-08-21 19:54:28 +01:00
ssd: add window drop-shadows (#1648) Add optional drop-shadows to windows using server-side decoration. Shadows can be enabled/disabled rc.xml and their appearance configured in themerc. The default is no shadows to preserve current behaviour. The shadows are drawn in fixed corner and edge buffers shared between all windows, the edges are scaled to size depending on the size of each window. Two sets of buffers are used to give the different appearances for active and inactive windows. I use separate corner/edge buffers for a few reasons: - It avoids needing to store a separate large shadow buffer per window - It avoids needing to redraw the shadows when the window is being resized - Compositing the shadows onto the desktop should be faster as there are overall fewer pixels to blend, and scaling up the edge buffers only requires reading a tiny buffer which is then replicated.
2024-04-22 19:27:53 +01:00
# window drop-shadows
window.active.shadow.size: 60
window.inactive.shadow.size: 40
window.active.shadow.color: #00000060
window.inactive.shadow.color: #00000040
docs: update theme documentation .. to reflect that its now possible to change the color of the menu button
2022-12-23 18:20:49 +01:00
# Note that "menu", "iconify", "max", "close" buttons colors can be defined
theme: document setting iconify/close/max colors separately
2021-08-22 19:11:54 +01:00
# individually by inserting the type after the button node, for example:
#
# window.active.button.iconify.unpressed.image.color: #333333
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
# menu
docs/themerc: add menu.width.{min,max} + menu.items.padding.{x,y} ...to reflect additions introduced by f0666ba and d00327b Move menu.overlap.* to the menu section for a more logical grouping
2022-12-08 20:38:31 +00:00
menu.overlap.x: 0
menu.overlap.y: 0
menu.width.min: 20
menu.width.max: 200
menu: support borders This commit adds following theme configurations: menu.border.width: 1 menu.border.color: #aaaaaa
2024-11-24 14:40:40 +09:00
menu.border.width: 1
menu.border.color: #aaaaaa
themerc: fix syntax inconsistency
2021-03-04 20:30:23 +00:00
menu.items.bg.color: #fcfbfa
menu.items.text.color: #000000
use the GTK+ 3 notebook header color as the default active title color
2023-11-28 08:22:54 +02:00
menu.items.active.bg.color: #e1dedb
theme: update built-in theme colors Use #dddad6 for active title/border and #f6f5f4 for inactive. It matches default GTK colors reasonably well.
2021-04-10 19:30:39 +01:00
menu.items.active.text.color: #000000
docs/themerc: add menu.width.{min,max} + menu.items.padding.{x,y} ...to reflect additions introduced by f0666ba and d00327b Move menu.overlap.* to the menu section for a more logical grouping
2022-12-08 20:38:31 +00:00
menu.items.padding.x: 7
menu.items.padding.y: 4
menu: support <separator /> Add theme options: - menu.separator.width - menu.separator.padding.width - menu.separator.padding.height - menu.separator.color Support separator lines defined by <separator /> Note that separator labels (with text) defined by <separator label="" /> are not supported.
2022-06-22 21:07:25 +01:00
menu.separator.width: 1
menu.separator.padding.width: 6
menu.separator.padding.height: 3
menu.separator.color: #888888
menu: support titles ...defined by `<separator label="">`. Also add the theme option `menu.title.bg.color: #589bda` The following will be added in separate commits - menu.title.bg.border.color: #7cb6ec - menu.title.text.color: #ffffff - menu.title.text.justify: center
2024-05-09 21:20:15 +01:00
menu.title.bg.color: #589bda
menu: add title theme options (#2097) Add theme options `menu.title.text.color` and `menu.title.text.justify`. Add font place MenuHeader: `<font place="MenuHeader">` Add `Oblique` font style ``` <theme> <font> <slant>Oblique</slant> </font> </theme> ```
2024-08-21 12:27:07 -05:00
menu.title.text.color: #ffffff
menu.title.text.justify: Center
docs/themerc: add missing theme options
2021-10-20 19:52:17 +01:00
# on screen display (window-cycle dialog)
themerc: fix default value of `osd.bg.color`
2024-04-14 21:04:52 +09:00
osd.bg.color: #e1dedb
theme: implement osd.border.color and osd.border.width http://openbox.org/wiki/Help:Themes#osd.border.color http://openbox.org/wiki/Help:Themes#osd.border.width
2022-05-31 19:14:58 +02:00
osd.border.color: #000000
osd.border.width: 1
docs/themerc: add missing theme options
2021-10-20 19:52:17 +01:00
osd.label.text.color: #000000
theme: add window-switcher width/padding ...and calculate item-height based on font-height Add theme options - osd.window-switcher.width - osd.window-switcher.item.padding.x - osd.window-switcher.item.padding.y Issue #879
2023-04-24 21:31:28 +01:00
osd: support percent values for window switcher width Add ability to set width with percentage of monitor instead of just pixels. With this the OSD sizes itself properly on both my 4k and 2k monitors. example: 50% or 75% instead of 600, max 100%
2024-03-26 05:12:19 -05:00
# width can be set as percent (of screen width)
# example 50% or 75% instead of 600, max 100%
theme: add window-switcher width/padding ...and calculate item-height based on font-height Add theme options - osd.window-switcher.width - osd.window-switcher.item.padding.x - osd.window-switcher.item.padding.y Issue #879
2023-04-24 21:31:28 +01:00
osd.window-switcher.width: 600
osd: support percent values for window switcher width Add ability to set width with percentage of monitor instead of just pixels. With this the OSD sizes itself properly on both my 4k and 2k monitors. example: 50% or 75% instead of 600, max 100%
2024-03-26 05:12:19 -05:00
theme: add option osd.window-switcher.item.active.border.width ...and change default values for the variables below to keep the window-switcher look the same as it was at the last release. osd.window-switcher.padding = 4 osd.window-switcher.item.padding.y = 1 osd.window-switcher.item.active.border.width = 2
2023-07-01 14:56:13 +02:00
osd.window-switcher.padding: 4
theme: add window-switcher width/padding ...and calculate item-height based on font-height Add theme options - osd.window-switcher.width - osd.window-switcher.item.padding.x - osd.window-switcher.item.padding.y Issue #879
2023-04-24 21:31:28 +01:00
osd.window-switcher.item.padding.x: 10
theme: add option osd.window-switcher.item.active.border.width ...and change default values for the variables below to keep the window-switcher look the same as it was at the last release. osd.window-switcher.padding = 4 osd.window-switcher.item.padding.y = 1 osd.window-switcher.item.active.border.width = 2
2023-07-01 14:56:13 +02:00
osd.window-switcher.item.padding.y: 1
osd.window-switcher.item.active.border.width: 2
osd: add osd.window-switcher.item.icon.size This allows users to make the icon in window switcher bigger (or smaller) than the font size, which enables more Openbox-like appearance. Example configuration: osd.window-switcher.item.icon.size: 50 This commit also makes the icon smaller than the font size if the width allocated with <windowSwitcher><fields><field width=""> is smaller than that.
2025-04-01 16:53:15 +09:00
# The icon size the same as the font size by default
# osd.window-switcher.item.icon.size: 50
osd: add theme settings for window-switcher preview Adds theme settings like: osd.window-switcher.preview.border.width: 2 osd.window-switcher.preview.border.color: #ffffff,#00a2ff,#ffffff
2024-04-15 20:22:44 +09:00
osd.window-switcher.preview.border.width: 1
osd.window-switcher.preview.border.color: #dddda6,#000000,#dddda6
Add theme option to configure boxes from workspace OSD This allows to configure width and height of "boxes" displayed in the workspace OSD. A setting of `0` disables the boxes.
2023-12-11 12:41:33 +03:00
osd.workspace-switcher.boxes.width: 20
osd.workspace-switcher.boxes.height: 20
osd: add osd.workspace-switcher.boxes.border.width
2025-04-06 15:05:04 +04:00
osd.workspace-switcher.boxes.border.width: 2
overlay: add theme setting `snapping.preview.[region|edge].fill` This settings allows user to choose whether to draw a filled rectangle or an outlined rectangle as the preview for window snapping.
2024-04-14 02:24:36 +09:00
overlay: allow to draw both/either of filled/outlined rectangle Filled/outlined rectangles shown as snapping overlay are now enabled/disabled independently with `snapping.overlay.[region|edge].bg.enabled` and `snapping.overlay.[region|edge].border.enabled`. To keep the default behavior, `*.bg.enabled` is yes and `*.border.enabled` is no for hardware-based renderers, while `*.bg.enabled` is no and `*.border.enabled` is yes for software-based (pixman) renderer. Users can now use a filled rectangle as an overlay even with pixman renderer. However, this may severely impact performance when used with translucent `snapping.overlay.[region|edge].bg.color`. This commit includes a refactor to use substruct `theme_snapping_overlay` inside `theme` in order to pass it to `create_overlay_rect()` in a cleaner way. Breaking changes is: - `snapping.overlay.[region|edge].fill` is now removed.
2024-04-21 02:30:31 +09:00
# Default values for following options change depending on the rendering
# backend. For software-based renderers, *.bg.enabled is "no" and
# *.border.enabled is "yes" if not set. For hardware-based renderers,
# *.bg.enabled is "yes" and *.border.enabled is "no" if not set.
# Setting *.bg.enabled to "yes" for software-based renderer with translucent
# background color may severely impact performance.
#
# snapping.overlay.region.bg.enabled:
# snapping.overlay.edge.bg.enabled:
# snapping.overlay.region.border.enabled:
# snapping.overlay.edge.border.enabled:
overlay: s/preview/overlay/ Replace "preview" in rc.xml and themerc with "overlay" since "preview" sounds like it shows the window content. Breaking changes are: - `snapping.preview.*` in themerc is now replaced with `snapping.overlay`. - `<snapping><preview>` in rc.xml is now replaced with `<snapping><overlay>`.
2024-04-21 02:22:28 +09:00
snapping.overlay.region.bg.color: #8080b380
snapping.overlay.edge.bg.color: #8080b380
snapping.overlay.region.border.width: 1
snapping.overlay.edge.border.width: 1
snapping.overlay.region.border.color: #dddda6,#000000,#dddda6
snapping.overlay.edge.border.color: #dddda6,#000000,#dddda6
Reference in a new issue Copy permalink