X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fwsbar.html;h=c7c1db24c19dacac5b5059760b2b79db1a1dc3df;hb=042e2f340396c784b0c2f9f61891f872024843f2;hp=7a3b822af196977c4e1f97c80305889d98d1411b;hpb=7423f7cfe6cc48d000918b9bdf42d387b94adffd;p=i3%2Fi3.github.io diff --git a/docs/wsbar.html b/docs/wsbar.html index 7a3b822..c7c1db2 100644 --- a/docs/wsbar.html +++ b/docs/wsbar.html @@ -2,15 +2,15 @@ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> - + - + i3: External workspace bars @@ -22,16 +22,17 @@ window.onload = function(){asciidoc.footnotes(); asciidoc.toc(2);}
@@ -64,10 +61,10 @@ Instead, you should disable the internal bar and use an external workspace bar specific screen. Also, you don’t want to place the workspace bar somewhere in your layout by hand. This is where dock mode comes in: When a program sets the appropriate hint (_NET_WM_WINDOW_TYPE_DOCK), it will be managed in dock -mode by i3. That means it will be placed at the bottom of the screen (while -other edges of the screen are possible in the NetWM standard, this is not yet -implemented in i3), it will not overlap any other window and it will be on -every workspace for the specific screen it was placed on initially.

+mode by i3. That means it will be placed at the bottom or top of the screen +(while other edges of the screen are possible in the NetWM standard, this is +not yet implemented in i3), it will not overlap any other window and it will be +on every workspace for the specific screen it was placed on initially.

@@ -77,8 +74,8 @@ every workspace for the specific screen it was placed on initially.

provide the bar program with the current workspaces and output (as in VGA-1, LVDS-1, …) configuration. In the other direction, the program has to be able to switch to specific workspaces.

-

By default, the IPC interface is enabled and places its UNIX socket in -~/.i3/ipc.sock.

+

By default, the IPC interface is enabled and you can get the path to the socket +by calling i3 --get-socketpath.

To learn more about the protocol which is used for IPC, see docs/ipc.

@@ -92,16 +89,16 @@ will be adjusted properly.

-

5. i3-wsbar, the reference implementation

+

5. i3-wsbar, an example implementation

-

Please keep in mind that i3-wsbar is just a reference implementation. It is -shipped with i3 to have a reasonable default. Thus, i3-wsbar is designed to -work well with dzen2 and there are no plans to make it more generic.

+

i3-wsbar used to be the reference implementation before we had i3bar. +Nowadays, it is not shipped with release tarballs, but you can still get it at +http://code.stapelberg.de/git/i3/tree/contrib/i3-wsbar

5.1. The big picture

The most common reason to use an external workspace bar is to integrate system -information such as what i3status provides into the workspace bar (to save -screen space). So, we have i3status or a similar program, which only provides +information such as what i3status or conky provide into the workspace bar. +So, we have i3status or a similar program, which only provides text output (formatted in some way). To display this text nicely on the screen, there are programs such as dzen2, xmobar and similar. We will stick to dzen2 from here on. So, we have the output of i3status, which needs to go into dzen2 @@ -133,8 +130,6 @@ bar which you will see should look exactly like the internal bar of i3.

i3status | i3-wsbar -c "dzen2 -x %x -dock"
-

It is recommended to place the above command in your i3 configuration file -to start it automatically with i3.