Guile Really-Improved 3 Window Manager Fork of i3-wm with guile configuration
Go to file
Michael Stapelberg feaa161d2c testcases: explicitly mark the (short) config files as v4
i3 won’t call i3-migrate-config and thus won’t add a call to i3bar this way.
It’s not necessary and can interfere with some tests sometimes.
2011-07-15 01:37:54 +02:00
debian debian: fix build-deps for recent debian systems 2011-06-10 13:00:24 +02:00
docs patch to allow exec_always in configure file 2011-07-12 18:23:14 +02:00
i3-config-wizard
i3-input Makefile: respect and use LIBS (Thanks Kacper) 2011-07-13 13:28:31 +02:00
i3-msg
i3-nagbar
include
man
render-tree
src
testcases testcases: explicitly mark the (short) config files as v4 2011-07-15 01:37:54 +02:00
tests
website
yajl-fallback/yajl Make code compatible with yajl 2.0 *and* 1.0 2011-04-27 19:52:53 +02:00
.gitignore
CMDMODE
DEPENDS libXcursor support (themed cursors). 2010-11-28 13:01:45 +01:00
GOALS Add GOALS file with anti-autotools 2009-02-09 20:56:29 +01:00
LICENSE Add vim hints, copyright notice to each file, add LICENSE, retab! everything 2009-02-14 02:33:31 +01:00
Makefile
PACKAGE-MAINTAINER
README.tree
RELEASE-NOTES-3.a-bf1
RELEASE-NOTES-3.b
RELEASE-NOTES-3.c
RELEASE-NOTES-3.d
RELEASE-NOTES-tree-pr1 add release notes for tree-pr3 2011-05-28 22:12:47 +02:00
RELEASE-NOTES-tree-pr2 add release notes for tree-pr3 2011-05-28 22:12:47 +02:00
RELEASE-NOTES-tree-pr3
TODO
common.mk
dump-asy.pl
gtk-tree-watch.pl
i3-migrate-config-to-v4.pl
i3-wsbar
i3.config
i3.config.keycodes
i3.desktop
i3.welcome
logo.svg
pseudo-doc.doxygen

README.tree

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

README file for the "tree" branch of i3
=======================================

This is a *massive* refactoring of i3. It was driven by thinking about whether
a different data structure could make things easier (for users and developers).
The old data structure of a table provided relatively flexible layouts but was
*very* hard to implement.

The new data structure is a tree. You can have horizontally and vertically split
containers. Each container can contain either nothing yet (waiting for a window
or for the user to put more containers in it), one or more containers or exactly
one window. RandR Outputs and workspaces are not treated specially, but they
are just containers inside the tree.

This structure allows for easy serialization, meaning multiple things:
- we can store and reload the layout for inplace restarts (this is already working)
- we can store parts of the layout and load them at any position in our tree
  (partly working)
  - we can load a layout specifying the physical positions of RandR outputs
    for pathologic screen setups
  - we can load a default layout for each workspace to specify the position
    of dock clients
- we can use test-driven development to a much higher degree because we have
  access to the whole tree

Ripping out the core data structures of i3 and replacing them of course has
some side-effects, which I will describe here (the list may not be complete,
new side-effects may not be known yet):
- Empty containers are allowed. They can swallow windows based on certain
  criteria. We can implement session-saving this way.
- Assignments (put windows on certain workspaces, put workspaces on certain
  outputs) are just special cases of the point above.
- Window decorations are now always rendered on the parent window. This means
  we dont have to carry around ugly Stack_Windows any more.
- Operations always (?) operate on containers, so you can make a container
  (containing multiple windows) fullscreen or floating (for example) and no
  longer just single windows.
- All X11 requests are now pushed to X11 in a separate step (rendering is one
  step, updating X11 another). This makes talking to X11 a lot less error-prone
  and allows for simpler code.

======================
SOME WORDS OF WARNING:
======================

The current state of the branch is not nearly the quality you know of i3. It
is in flux, changes and crashes are to be expected. Many features do not work
yet. It is only suitable if you want to help developing or have a look at what
is coming. Do *NOT* use it for production! You have been warned.