X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fi3bar-protocol;h=cf86531cc5f399774e983770719245729693c17a;hb=e26fd91cf868824726d74db7388d05736e1fd7da;hp=ccc763460ced1db2108fcbee593c3840b111c736;hpb=f2b728ac5ec00d004f954f85077635668f21fbfd;p=i3%2Fi3 diff --git a/docs/i3bar-protocol b/docs/i3bar-protocol index ccc76346..cf86531c 100644 --- a/docs/i3bar-protocol +++ b/docs/i3bar-protocol @@ -6,7 +6,7 @@ August 2012 This document explains the protocol in which i3bar expects its input. It provides support for colors, urgency, shortening and easy manipulation. -== Rationale for chosing JSON +== Rationale for choosing JSON Before describing the protocol, let’s cover why JSON is a building block of this protocol. @@ -96,7 +96,7 @@ i3status and others will output single statuslines in one line, separated by You can find an example of a shell script which can be used as your +status_command+ in the bar configuration at -http://code.stapelberg.de/git/i3/tree/contrib/trivial-bar-script.sh?h=next +https://github.com/i3/i3/blob/next/contrib/trivial-bar-script.sh === Header in detail @@ -111,16 +111,14 @@ cont_signal:: processing. The default value (if none is specified) is SIGCONT. click_events:: - If specified and true i3bar will write a infinite array (same as above) + If specified and true i3bar will write an infinite array (same as above) to your stdin. === Blocks in detail full_text:: - The most simple block you can think of is one which just includes the - only required key, the +full_text+ key. i3bar will display the string - value parsed as - https://developer.gnome.org/pango/stable/PangoMarkupFormat.html[Pango markup]. + The +full_text+ will be displayed by i3bar on the status line. This is the + only required key. short_text:: Where appropriate, the +short_text+ (string) entry should also be provided. It will be used in case the status line needs to be shortened @@ -138,6 +136,10 @@ color:: when it is associated. Colors are specified in hex (like in HTML), starting with a leading hash sign. For example, +#ff0000+ means red. +background:: + Overrides the background color for this particular block. +border:: + Overrides the border color for this particular block. min_width:: The minimum width (in pixels) of the block. If the content of the +full_text+ key take less space than the specified min_width, the block @@ -174,8 +176,9 @@ separator_block_width:: is 9 pixels), since the separator line is drawn in the middle. markup:: A string that indicates how the text of the block should be parsed. Set to - +"pango"+ to use https://developer.gnome.org/pango/stable/PangoMarkupFormat.html[Pango markup] - (default). Set to +"none"+ to not use any markup. + +"pango"+ to use https://developer.gnome.org/pango/stable/PangoMarkupFormat.html[Pango markup]. + Set to +"none"+ to not use any markup (default). Pango markup only works + if you use a pango font. If you want to put in your own entries into a block, prefix the key with an underscore (_). i3bar will ignore all keys it doesn’t understand, and prefixing @@ -209,6 +212,8 @@ An example of a block which uses all possible entries follows: "full_text": "E: 10.0.0.1 (1000 Mbit/s)", "short_text": "10.0.0.1", "color": "#00ff00", + "background": "#1c1c1c", + "border": "#ee0000", "min_width": 300, "align": "right", "urgent": false, @@ -229,9 +234,14 @@ name:: instance:: Instance of the block, if set x, y:: - X11 root window coordinates where the click occured + X11 root window coordinates where the click occurred button:: X11 button ID (for example 1 to 3 for left/middle/right mouse button) +relative_x, relative_y:: + Coordinates where the click occurred, with respect to the top left corner + of the block +width, height:: + Width and height (in px) of the block *Example*: ------------------------------------------ @@ -240,6 +250,10 @@ button:: "instance": "eth0", "button": 1, "x": 1320, - "y": 1400 + "y": 1400, + "relative_x": 12, + "relative_y": 8, + "width": 50, + "height": 22 } ------------------------------------------