It currently doesn't appear to be possible to do otherwise, as

* tabGroupChanged is called for all clients in the tabgroup (at least
  once it's built)

* client.tabGroup is always undefined

This avoids an infinite loop (fortunately it'd be recursive, so the
stack would kill it)

Remove some unused or commented lines, fix a minor typo

This is now pseudo-animated, which is much nicer than an outline anyway

This didn't actually work before, but now we can handle clients getting
borders and some other stuff better

(Also simplify code)

Remove an additional layout.activate and movestep handling (only in
tilingmanager) as they do _nothing_

Defaults to Meta+U

This means you can now resize it, close everything, and it will keep the
width ratio

This only applies to the focus hotkeys

This includes error checking and initializing variables to proper values

This also introduces a proper method to add clients to a tile and remove
clients from it which
allows us to do sanity checking

Previously, it was possible to go down from tile 0 to tile 1, but not up
from 1 to 0.

Now, don't allow going down from tile 0 (as it's not actually down).

This is literally a one-line change.

* Enable resize animations
* Fix resizing bladelayout
* Fix panel adjusting (with a workaround)

We always seem to get the full area when we ask for a desktop that's not
the first (0).

These may be janky, but offer useful feedback.

Turns out it really _was_ needed.

It's better to be notified when something goes wrong than for it to be
ignored silently.

This is completely unnecessary.

This means a huge speedup when you do silly things like make a client
fullscreen and not fullscreen fifty times.

The issue was that we never got a tile when the signals were
launched (this could have caused other issues as well).

This currently does nothing useful (the outline is shown, but flickers
terribly), so don't waste the users CPU.

The former was broken in a previous commit, the latter is now properly
introduced (as shaded windows still report the same geometry, we handle
them as we do fullscreen windows - not).

Until now, the windows would leave a hole the height of the strut

For now it's the same in all layouts anyway (and untested, since kwin
doesn't seem to hand the new area)

It is _strongly_ recommended for now to use FocusUnderMouse with this,
as it's otherwise almost impossible to tell which window is focussed.

Should also fix e.g. Firefox resizing.