"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">\r
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
+<link rel="icon" type="image/x-icon" href="/favicon.ico">\r
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 8.6.4" />\r
+<meta name="generator" content="AsciiDoc 8.6.10" />\r
<title>i3: External workspace bars</title>\r
<link rel="stylesheet" href="/css/style.css" type="text/css" />\r
<link rel="stylesheet" href="/css/xhtml11.css" type="text/css" />\r
<script type="text/javascript">\r
/*<![CDATA[*/\r
-window.onload = function(){asciidoc.footnotes(); asciidoc.toc(2);}\r
+document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); asciidoc.toc(2);}, false);\r
/*]]>*/\r
</script>\r
<script type="text/javascript" src="/js/asciidoc-xhtml11.js"></script>\r
<body class="article">\r
\r
<div id="main">\r
- <h1 id="title">i3 - improved tiling WM</h1>\r
+ <a href="/"><h1 id="title">i3 - improved tiling WM</h1></a>\r
<ul id="nav">\r
<li><a style="border-bottom: 2px solid #fff" href="/docs">Docs</a></li>\r
<li><a href="/screenshots">Screens</a></li>\r
+ <li><a href="https://www.reddit.com/r/i3wm/">FAQ</a></li>\r
<li><a href="/contact">Contact</a></li>\r
- <li><a href="http://bugs.i3wm.org/">Bugs</a></li>\r
+ <li><a href="https://github.com/i3/i3/issues">Bugs</a></li>\r
</ul>\r
<br style="clear: both">\r
<div id="content">\r
<div id="header">\r
<h1>External workspace bars</h1>\r
<span id="author">Michael Stapelberg</span><br />\r
-<span id="email"><tt><<a href="mailto:michael+i3@stapelberg.de">michael+i3@stapelberg.de</a>></tt></span><br />\r
-<span id="revdate">May 2010</span>\r
-<div id="toc">
- <div id="toctitle">Table of Contents</div>
- <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+<span id="email"><tt><<a href="mailto:michael@i3wm.org">michael@i3wm.org</a>></tt></span><br />\r
+<span id="revdate">April 2013</span>\r
+<div id="toc">\r
+ <div id="toctitle">Table of Contents</div>\r
+ <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>\r
</div>\r
</div>\r
<div id="preamble">\r
<div class="sectionbody">\r
-<div class="paragraph"><p>This document describes why the internal workspace bar is minimal and how an\r
-external workspace bar can be used. It explains the concepts using <tt>i3-wsbar</tt>\r
-as the reference implementation.</p></div>\r
+<div class="paragraph"><p>i3 comes with i3bar by default, a simple bar that is sufficient for most users.\r
+In case you are unhappy with it, this document explains how to use a different,\r
+external workspace bar. Note that we do not provide support for external\r
+programs.</p></div>\r
</div>\r
</div>\r
<div class="sect1">\r
<div class="sectionbody">\r
<div class="paragraph"><p>The internal workspace bar of i3 is meant to be a reasonable default so that\r
you can use i3 without having too much hassle when setting it up. It is quite\r
-simple and intended to stay this way. So, there is no way to display your own\r
-information in this bar (unlike dwm, wmii, awesome, …).</p></div>\r
-<div class="paragraph"><p>We chose not to implement such a mechanism because that would be duplicating\r
-already existing functionality of tools such as dzen2, xmobar and similar.\r
-Instead, you should disable the internal bar and use an external workspace bar\r
-(which communicates with i3 through its IPC interface).</p></div>\r
+simple and intended to stay this way.</p></div>\r
</div>\r
</div>\r
<div class="sect1">\r
specific screen. Also, you don’t want to place the workspace bar somewhere\r
in your layout by hand. This is where dock mode comes in: When a program sets\r
the appropriate hint (_NET_WM_WINDOW_TYPE_DOCK), it will be managed in dock\r
-mode by i3. That means it will be placed at the bottom of the screen (while\r
-other edges of the screen are possible in the NetWM standard, this is not yet\r
-implemented in i3), it will not overlap any other window and it will be on\r
-every workspace for the specific screen it was placed on initially.</p></div>\r
+mode by i3. That means it will be placed at the bottom or top of the screen\r
+(while other edges of the screen are possible in the NetWM standard, this is\r
+not yet implemented in i3), it will not overlap any other window and it will be\r
+on every workspace for the specific screen it was placed on initially.</p></div>\r
</div>\r
</div>\r
<div class="sect1">\r
provide the bar program with the current workspaces and output (as in VGA-1,\r
LVDS-1, …) configuration. In the other direction, the program has to be able\r
to switch to specific workspaces.</p></div>\r
-<div class="paragraph"><p>By default, the IPC interface is enabled and places its UNIX socket in\r
-<tt>~/.i3/ipc.sock</tt>.</p></div>\r
+<div class="paragraph"><p>By default, the IPC interface is enabled and you can get the path to the socket\r
+by calling <tt>i3 --get-socketpath</tt>.</p></div>\r
<div class="paragraph"><p>To learn more about the protocol which is used for IPC, see <tt>docs/ipc</tt>.</p></div>\r
</div>\r
</div>\r
</div>\r
</div>\r
<div class="sect1">\r
-<h2 id="_i3_wsbar_the_reference_implementation">5. i3-wsbar, the reference implementation</h2>\r
+<h2 id="_i3_wsbar_an_example_implementation">5. i3-wsbar, an example implementation</h2>\r
<div class="sectionbody">\r
-<div class="paragraph"><p>Please keep in mind that <tt>i3-wsbar</tt> is just a reference implementation. It is\r
-shipped with i3 to have a reasonable default. Thus, <tt>i3-wsbar</tt> is designed to\r
-work well with dzen2 and there are no plans to make it more generic.</p></div>\r
+<div class="paragraph"><p><tt>i3-wsbar</tt> used to be the reference implementation before we had <tt>i3bar</tt>.\r
+Nowadays, it is not shipped with release tarballs, but you can still get it at\r
+<a href="https://github.com/i3/i3/blob/next/contrib/i3-wsbar">https://github.com/i3/i3/blob/next/contrib/i3-wsbar</a></p></div>\r
<div class="sect2">\r
<h3 id="_the_big_picture">5.1. The big picture</h3>\r
<div class="paragraph"><p>The most common reason to use an external workspace bar is to integrate system\r
-information such as what <tt>i3status</tt> provides into the workspace bar (to save\r
-screen space). So, we have <tt>i3status</tt> or a similar program, which only provides\r
+information such as what <tt>i3status</tt> or <tt>conky</tt> provide into the workspace bar.\r
+So, we have <tt>i3status</tt> or a similar program, which only provides\r
text output (formatted in some way). To display this text nicely on the screen,\r
there are programs such as dzen2, xmobar and similar. We will stick to dzen2\r
from here on. So, we have the output of i3status, which needs to go into dzen2\r
<div class="content">\r
<pre><tt>i3status | i3-wsbar -c "dzen2 -x %x -dock"</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p>It is recommended to place the above command in your i3 configuration file\r
-to start it automatically with i3.</p></div>\r
</div>\r
</div>\r
</div>\r
</div>\r
<div id="footnotes"><hr /></div>\r
-<div id="footer">\r
-<div id="footer-text">\r
-Last updated 2011-07-22 20:28:28 CEST\r
-</div>\r
+<div id="footer" lang="de">\r
+ © 2009-present Michael Stapelberg,\r
+ <a href="/impress.html">Impressum</a>,\r
+ <a href="https://github.com/i3/i3.github.io">Source</a>\r
</div>\r
</body>\r
</html>\r
projects / i3 / i3.github.io / blobdiff