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-config(5): clarify applicability of element/attribute (#1655)

Browse source 
Co-authored-by: Andrew J. Hesford <ajh@sideband.org>
This commit is contained in:
Johan Malm 2024-03-24 21:32:27 +00:00 • committed by GitHub
parent 11b6836a38
commit e79bbd3022
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 20 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

21
docs/labwc-config.5.scd
View file

@ -98,7 +98,26 @@ Configuration must be wrapped in a <labwc_config> root-element like this:
*labwc* parses XML in an element/attribute agnostic way. This is a design
decision to increase config file flexibility and keep code simple. In practical
terms, this means that `<a><b>c</b></a>` is equivalent to `<a b="c" />`.
terms, this means that `<a><b>c</b></a>` is usually equivalent to `<a b="c" />`.
However, there are some caveats:
1. In menu.xml, the attributes *id*, *label* and *execute* must be
expressed as attributes rather than as separate child elements.
2. Ordering of attributes can sometimes be singificant. For example,
when setting fonts via attributes rather than children,
*<font place="ActiveWindow" name="..." size="..." />*
will set a font for active window titles, while
*<font name="..." size="..." place="ActiveWindow" />*
will set a font as if *place* were unspecified, because *name* and
*size* will be processed before *place*.
In general, it is recommended that attributes not be used to collapse more than
one level of the configuration hierarchy.
The following three are therefore treated the same: