Go to file
Fernando Tarlá Cardoso Lemos c88c3e3ab2 Default to a file in /tmp for the restart state.
The file is now created in /tmp using the process PID and the
username of the user running i3. The restart state file is only
loaded when restarting (the --restart option is appended to the
command line prior to the restart). That means that renaming the
old state file with the ".old" extension is no longer needed.

This "--restart" switch is supposed to be only used by i3. The
"-L" switch can be used to load a layout (and not delete it
afterwards). We unlink the state file after we load it so that
we don't keep cruft in /tmp or try to restart from an old config
file if restart_state is set.
2010-12-27 13:33:03 +01:00
debian libXcursor support (themed cursors). 2010-11-28 13:01:45 +01:00
docs Info about client.background for the user guide. 2010-11-13 20:08:19 +01:00
i3-input Fix numlock state 2010-03-24 03:28:38 +01:00
i3-msg i3-msg: s/tree/get_tree for consistency, add new types to error message 2010-11-21 21:39:09 +01:00
include Default to a file in /tmp for the restart state. 2010-12-27 13:33:03 +01:00
man remove superflous newlines (breaks asciidoc) 2010-03-21 01:55:02 +01:00
src Default to a file in /tmp for the restart state. 2010-12-27 13:33:03 +01:00
testcases Bugfix: Correctly attach floating Cons to a different workspace, extend testcase 2010-11-29 20:39:56 +01:00
tests Separate font stuff to font.c, beautify Makefile 2009-02-08 11:25:32 +01:00
website website: add userguide 2009-06-26 13:49:18 +02:00
.gitignore update .gitignore 2010-11-28 20:19:26 +01:00
CMDMODE docs: merge spelling and grammar fixes by sasha (Thanks!) 2010-03-21 01:50:10 +01:00
common.mk libXcursor support (themed cursors). 2010-11-28 13:01:45 +01:00
DEPENDS libXcursor support (themed cursors). 2010-11-28 13:01:45 +01:00
dump-asy.pl perl: use get_tree instead of get_workspaces 2010-11-21 21:42:28 +01:00
GOALS Add GOALS file with anti-autotools 2009-02-09 20:56:29 +01:00
gtk-tree-watch.pl perl: use get_tree instead of get_workspaces 2010-11-21 21:42:28 +01:00
i3-wsbar Add initial version of i3-wsbar 2010-03-24 19:13:19 +01:00
i3.config add shortcut to default config for tiling/floating toggle 2010-11-21 17:04:35 +01:00
i3.desktop Add a .desktop-file containing xsession information for freedesktop compliant login managers 2009-04-19 22:29:04 +02:00
i3.welcome docs: merge spelling and grammar fixes by sasha (Thanks!) 2010-03-21 01:50:10 +01:00
LICENSE Add vim hints, copyright notice to each file, add LICENSE, retab! everything 2009-02-14 02:33:31 +01:00
logo.svg Add logo to git. Thanks to steckdenis, yellowiscool and farvardin! 2009-08-04 01:40:05 +02:00
Makefile remove i3-wsbar from 'make install', not supported at the moment 2010-12-06 13:20:37 +01:00
PACKAGE-MAINTAINER docs: merge spelling and grammar fixes by sasha (Thanks!) 2010-03-21 01:50:10 +01:00
pseudo-doc.doxygen Put documentation for each function in the header files, doxygen-compatible 2009-04-07 19:02:07 +02:00
README.tree first step of the big refactoring ("tree" branch). 2010-04-13 13:17:39 +02:00
RELEASE-NOTES-3.a-bf1 Add release notes to git, welcome 3.a-bf1 :-) 2009-05-03 17:24:07 +02:00
RELEASE-NOTES-3.b debian: update changelog 2009-06-26 04:42:58 +02:00
RELEASE-NOTES-3.c Add release notes for 3.γ 2009-08-19 14:00:49 +02:00
RELEASE-NOTES-3.d Update changelog / release-notes 2009-11-09 20:54:16 +01:00
TODO Update TODO file 2009-04-19 20:45:28 +02:00

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.