== Rule Evaluation
This is a bit unsharp. It does not seem clear to me that rules are
processed up to the first matching rule, ie. that if you have a blind rule
to eg. place windows centered (what is a dumb idea, since there's a legal
setting, just stressing the point here) that does no break other rules
below in the chain, eg. the focus prevention for xv or to keep certain
windows on top etc, while their window matching strategy is much stricter.
== Window Matching
-- Exact Match - case insensitive.
-- Substring Match - case insensitive.
This is imho error prone, my first (mis)read was "one's sensitive, the
This the case insensitivity is common i'd not point it for each strategy
but note that as a tip or below or whatever and omit the description,
unless ppl. need to be told what a substring is ;-)
"If the rule has not other attributes set, the rule is deleted."
^ "than apply
initially and force temporarily"
== Size & Position
"Ignore requested geometry
Toggle whether to accept or ignore the window's requested geometry and
ignore the global placement strategy."
"Toggle whether to accept or ignore the window's requested geometry. If a
window requests a geometry and that request is accepted (default) the
placement strategy is not invokes."
Or sth. like this.
"Obey geometry restrictions
Toggle whether to adhere to the window's requested aspect ratio."
... "and base increment, ie. the amount of pixels by that the window can
minimally be resized usually (1,1)" - or explain a base increment size
== Appearance & Fixes
"Ignore global shortcuts
Toggle whether to ignore global shortcuts while the window is active."
"such as defined in kcmshell4 keys" or similar, so ppl. know what a global
Change the window to another type and inherit the characteristics of that
"Warning: use with care., eg. splash screens are closed by KWin when you
Otherwise many thanks for taking this burden upon you, the interview was a
great way to get "weird developers X11/NETWM oriented talk" into human
language - anytime again.