2009-05-01 19:29:29 +02:00
|
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
|
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
|
|
|
|
<head>
|
|
|
|
|
<title>i3status – Generates a status line for dzen2 or wmii</title>
|
|
|
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
|
|
|
<style type="text/css">
|
|
|
|
|
body {
|
|
|
|
|
text-align: justify;
|
|
|
|
|
max-width: 800px;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
li {
|
|
|
|
|
margin-bottom: 10px;
|
|
|
|
|
}
|
|
|
|
|
</style>
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
|
|
|
|
|
<h1>i3status</h1>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
i3status is a small program (around 500 SLOC) for filling dzen2 or wmii’s status
|
|
|
|
|
bar via its 9P pseudo filesystem. It is designed to be very efficient by issuing
|
|
|
|
|
a very small number of systemcalls (as the bar should be updated every second or
|
|
|
|
|
at your specified interval). This ensures that even under high load, your status
|
2009-06-17 21:52:31 +02:00
|
|
|
|
bar is updated correctly and it saves a little bit of battery life by not spawning
|
|
|
|
|
new processes every second like shell scripts do.
|
2009-05-01 19:29:29 +02:00
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h2>Releases</h2>
|
|
|
|
|
|
|
|
|
|
<ul>
|
2009-06-17 21:52:31 +02:00
|
|
|
|
<li><a href="/i3status/i3status-1.1.tar.bz2">i3status-1.1.tar.bz2</a>
|
|
|
|
|
(<a href="/i3status/i3status-1.1.tar.bz2.asc">GPG signature</a>, 2009-06-17)</li>
|
2009-05-01 19:34:03 +02:00
|
|
|
|
<li><a href="/i3status/i3status-1.0.tar.bz2">i3status-1.0.tar.bz2</a></li>
|
2009-05-01 19:29:29 +02:00
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h2>Development</h2>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
i3status is currently developed at <a href="http://code.stapelberg.de/git/i3status" title="cgit">
|
|
|
|
|
http://code.stapelberg.de/git/i3status</a>. Checkouts of the master branch are intended to
|
|
|
|
|
be stable and working all the time. Integration of new features happens in a separate branch.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h2>Contact</h2>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
Contact us at <a href="irc://irc.twice-irc.de/i3" title="#i3 on irc.twice-irc.de">
|
|
|
|
|
irc://irc.twice-irc.de/i3</a> (or, #i3 on irc.twice-irc.de, for those without proper URL
|
|
|
|
|
handling setup). Feel free to ask questions, please don’t ask to ask and please
|
|
|
|
|
think before you ask :-).
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h2>License</h2>
|
|
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
Copyright © 2008-2009 Michael Stapelberg and contributors
|
|
|
|
|
All rights reserved.
|
|
|
|
|
|
|
|
|
|
Redistribution and use in source and binary forms, with or without modification,
|
|
|
|
|
are permitted provided that the following conditions are met:
|
|
|
|
|
|
|
|
|
|
* Redistributions of source code must retain the above copyright notice, this
|
|
|
|
|
list of conditions and the following disclaimer.
|
|
|
|
|
|
|
|
|
|
* Redistributions in binary form must reproduce the above copyright notice, this
|
|
|
|
|
list of conditions and the following disclaimer in the documentation and/or other
|
|
|
|
|
materials provided with the distribution.
|
|
|
|
|
|
|
|
|
|
* Neither the name of Michael Stapelberg nor the names of contributors
|
|
|
|
|
may be used to endorse or promote products derived from this software without
|
|
|
|
|
specific prior written permission.
|
|
|
|
|
|
|
|
|
|
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
|
|
|
|
|
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
|
|
|
|
|
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
|
|
|
|
|
SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
|
|
|
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
|
|
|
|
|
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
|
|
|
|
|
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
|
|
|
|
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
|
|
|
|
|
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
|
|
|
|
|
DAMAGE.
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|