summaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorSpencer Janssen <sjanssen@cse.unl.edu>2007-03-20 08:18:12 +0100
committerSpencer Janssen <sjanssen@cse.unl.edu>2007-03-20 08:18:12 +0100
commit7ec2d9b39eb3ca3331e22be3d415c1ef8047bffc (patch)
treed1410657508caa0c545bc73c410819c67aedd36a /TODO
parentbb8a7cffd5473e6b9185576e6b84e5f47d3441ca (diff)
downloadmetatile-7ec2d9b39eb3ca3331e22be3d415c1ef8047bffc.tar
metatile-7ec2d9b39eb3ca3331e22be3d415c1ef8047bffc.zip
Initial tiling support.
darcs-hash:20070320071812-a5988-5f091f18a418d6aaf940b800530e0c6a7c4bc312
Diffstat (limited to 'TODO')
-rw-r--r--TODO21
1 files changed, 8 insertions, 13 deletions
diff --git a/TODO b/TODO
index cf0bedf..8d56c22 100644
--- a/TODO
+++ b/TODO
@@ -2,6 +2,8 @@
- tiling
- Refactor to make user configuration reasonable. There should be one
file (Config.hs) with all the knobs a user can twist.
+ - Code clean up after tiling and StackSet changes
+ - Make sure the quickchecks make sense with the new StackSet
- think about the statusbar/multithreading.
Three shared TVars:
@@ -21,16 +23,9 @@
redraws whenever it finds a change.
- tiling:
- - StackSet currently holds one stack, it needs to hold two. One stack
- contains focus info, the top of that stack is always the window that
- is in the foreground and has focus.
-
- The other stack keeps track of window layout order. In tiling mode,
- the first window in the stack is in the master area. In both tiling
- and full screen mode, window cycling follows the order in this stack.
-
- - Layout calculation: a simple function from number of windows to list
- of coordinates.
-
- - state components, key combos, etc. for changing the current layout
- scheme
+ - Layout calculation: the current algorithm is crude, windows overlap
+ - make focus remain between workspace switches
+ - change focus in the StackSet structure on EnterNotify
+ - operations to change window order (like dwm's mod+enter)
+ - add 'ratio' to XState, add bindings to change it on the fly
+ - borders (low priority, maybe wait until 0.2)