As of yesterday, QuickTile requires the Python bindings for
libwnck. What advantages does this bring? Well, here’s a changelog for the more significant of the recent commits:
0.2.1 (changes made not long after this post):
- Redesigned the help output with better explanations of what the commands do.
- Bugfix for toggling horizontal/vertical-only maximization.
- Added commands for:
- Switching workspaces (virtual desktops) or sending windows to them.
- Toggling various common window states like always-on-top/bottom.
- Triggering keyboard-driven move/resize.
- Applications like Wine and OpenOffice/LibreOffice which change the window gravity no longer mess up positioning. (Fixes #3)
- QuickTile now announces itself to the window manager as a pager-like utility. (Probably removes the need for a workaround for #5)
- Lots of code pruned out since it’s now handled more cleanly by
- A cleaner internal architecture (though there’s still work to be done)
0.1.6 (in testing since last weekend):
- Proper handling for desktops where panels or monitor sizes render the usable region non-rectangular. (Fixes #4)
This should also mean a much faster rate of development because…
- It was becoming prohibitively complicated to use
python-xlibto reinvent functionality already present in
- Each piece of
libwnckfunctionality reinvented via
python-xlibwas an additional hurdle to eventually supporting Python 3.
libwnckoffers Glib events like
window-openedwhich should greatly simplify some planned features.
Plus, given that QuickTile is a GTK+ app which deals with window management and
libwnck is the GTK+ library for building such apps, I really should have been using it from the beginning anyway.
This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.