| 1 |
neysx 09/01/29 17:50:20 |
| 2 |
|
| 3 |
Added: openbox.xml |
| 4 |
Log: |
| 5 |
#256693 initial commit |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/doc/en/openbox.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openbox.xml?rev=1.1&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openbox.xml?rev=1.1&content-type=text/plain |
| 12 |
|
| 13 |
Index: openbox.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version="1.0" encoding="UTF-8"?> |
| 16 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 17 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openbox.xml,v 1.1 2009/01/29 17:50:20 neysx Exp $ --> |
| 18 |
|
| 19 |
<guide disclaimer="draft"> |
| 20 |
<title>The Openbox Configuration HOWTO</title> |
| 21 |
|
| 22 |
<author title="Author"> |
| 23 |
<mail link="kalos"/> |
| 24 |
</author> |
| 25 |
|
| 26 |
<abstract> |
| 27 |
This guide shows you how to install the Openbox window manager, and references |
| 28 |
many potential programs to be used in conjunction with an Openbox session. |
| 29 |
</abstract> |
| 30 |
|
| 31 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 32 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 33 |
<license/> |
| 34 |
|
| 35 |
<version>1</version> |
| 36 |
<date>2009-01-29</date> |
| 37 |
|
| 38 |
<chapter> |
| 39 |
<title>Introduction</title> |
| 40 |
|
| 41 |
<section> |
| 42 |
<title>What is Openbox?</title> |
| 43 |
<body> |
| 44 |
|
| 45 |
<p> |
| 46 |
So, you've installed <uri link="/doc/en/xorg-config.xml">The X Server</uri> and |
| 47 |
realised that TWM just isn't going to cut it for your needs. You may have also |
| 48 |
had some experience with big desktop environments like <uri |
| 49 |
link="/proj/en/desktop/kde/kde-config.xml">KDE</uri>, <uri |
| 50 |
link="/doc/en/gnome-config.xml">GNOME</uri>, and <uri |
| 51 |
link="/doc/en/xfce-config.xml">Xfce</uri>. One component of those larger |
| 52 |
desktop suites is called the window manager (or WM for short). A window manager |
| 53 |
is responsible for the appearance and placement of the containers (or |
| 54 |
"windows") inside which programs run. Openbox is a minimalistic, |
| 55 |
no-frills-attached window manager. |
| 56 |
</p> |
| 57 |
|
| 58 |
</body> |
| 59 |
</section> |
| 60 |
<section> |
| 61 |
<title>Why should I use it?</title> |
| 62 |
<body> |
| 63 |
|
| 64 |
<p> |
| 65 |
Openbox, unlike the larger desktop environments, depends on very few libraries. |
| 66 |
For that reason, it can provide a lightweight graphic environment that runs |
| 67 |
very quickly, even on older hardware. Whether your hardware is old or new, |
| 68 |
Openbox also provides a highly customisable and unobtrusive working |
| 69 |
environment. That means that if you don't want or need a panel, taskbar, clock, |
| 70 |
or any other program, that choice is yours! |
| 71 |
</p> |
| 72 |
|
| 73 |
</body> |
| 74 |
</section> |
| 75 |
</chapter> |
| 76 |
|
| 77 |
<chapter> |
| 78 |
<title>Installation and configuration</title> |
| 79 |
|
| 80 |
<section> |
| 81 |
<title>Initial installation</title> |
| 82 |
<body> |
| 83 |
|
| 84 |
<p> |
| 85 |
After you have emerged xorg-x11 and configured all of your |
| 86 |
<path>xorg.conf</path> settings, installing Openbox can be done in one simple |
| 87 |
command: |
| 88 |
</p> |
| 89 |
|
| 90 |
<pre caption="Installing Openbox"> |
| 91 |
<comment>(Use <i>emerge -av openbox</i> to preview which packages will be installed)</comment> |
| 92 |
# <i>emerge openbox</i> |
| 93 |
</pre> |
| 94 |
|
| 95 |
<p> |
| 96 |
Just like with other window managers and desktop environments, you will need to |
| 97 |
tell the X Server to load Openbox automatically, by adding it to your |
| 98 |
<path>.xinitrc</path>. |
| 99 |
</p> |
| 100 |
|
| 101 |
<pre caption="Adding Openbox to your .xinitrc"> |
| 102 |
# <i>echo "exec openbox-session" >> ~/.xinitrc</i> |
| 103 |
</pre> |
| 104 |
|
| 105 |
<p> |
| 106 |
This will automatically start your Openbox session when you type <c>startx</c> |
| 107 |
at the terminal. |
| 108 |
</p> |
| 109 |
|
| 110 |
<impo> |
| 111 |
As each user has his or her own <path>.xinitrc</path>, you need to make sure to |
| 112 |
issue that command as <e>your user</e>, not as root. |
| 113 |
</impo> |
| 114 |
|
| 115 |
<note> |
| 116 |
You can also replace the KDE, GNOME, or Xfce default window manager with |
| 117 |
Openbox by following the <uri link="#inside-desktop-env">Openbox inside desktop |
| 118 |
environments</uri> directions. |
| 119 |
</note> |
| 120 |
|
| 121 |
<p> |
| 122 |
Now that you have emerged Openbox and added it to your <path>.xinitrc</path>, |
| 123 |
go ahead and issue the <c>startx</c> command to see Openbox in action. As you |
| 124 |
can see, the desktop is simply a cluttered mess! In following with the Openbox |
| 125 |
philosophy, what you will see is a barebones environment from which you can |
| 126 |
build your desktop completely to your liking. |
| 127 |
</p> |
| 128 |
|
| 129 |
<p> |
| 130 |
Since you're looking at nothing more than a black screen, you may be wondering |
| 131 |
where the menu is. If you click your right mouse button, you will notice that a |
| 132 |
menu pops up in the location of your cursor. This menu is nothing more than an |
| 133 |
example to illustrate the style of an Openbox menu. Since it <e>is</e> just an |
| 134 |
example, none of the items in the menu will work unless you have actually |
| 135 |
emerged those programs. In the next section, you will see how to create your |
| 136 |
own menu that contains links to <e>your</e> programs. |
| 137 |
</p> |
| 138 |
|
| 139 |
</body> |
| 140 |
</section> |
| 141 |
<section> |
| 142 |
<title>Menu configuration</title> |
| 143 |
<body> |
| 144 |
|
| 145 |
<p> |
| 146 |
Since the default Openbox menu is essentially useless to you for the reasons |
| 147 |
mentioned above, it's time that we create one that will work. Everything in the |
| 148 |
Openbox menu is written in the appropriately named <path>menu.xml</path> file, |
| 149 |
which can be in the user-specific location of |
| 150 |
<path>~/.config/openbox/menu.xml</path>, or in the system-wide location of |
| 151 |
<path>/etc/xdg/openbox/menu.xml</path>. By default, the only |
| 152 |
<path>menu.xml</path> file that is created is the system-wide one which applies |
| 153 |
to all users on the system. |
| 154 |
</p> |
| 155 |
|
| 156 |
<p> |
| 157 |
An easy way to get a basic menu file which you can modify is to use MenuMaker, |
| 158 |
which will generate a <path>menu.xml</path> file based on the programs which |
| 159 |
you currently have installed on your system. To do so, you must firstly emerge |
| 160 |
it: |
| 161 |
</p> |
| 162 |
|
| 163 |
<pre caption="Installing MenuMaker"> |
| 164 |
# <i>emerge menumaker</i> |
| 165 |
</pre> |
| 166 |
|
| 167 |
<p> |
| 168 |
Once it is installed, you need to tell it that you want a menu specifically |
| 169 |
using the Openbox XML syntax: |
| 170 |
</p> |
| 171 |
|
| 172 |
<pre caption="Using MenuMaker to generate a basic Openbox menu.xml"> |
| 173 |
# <i>mmaker -v OpenBox3</i> |
| 174 |
</pre> |
| 175 |
|
| 176 |
<p> |
| 177 |
The generated menu will be located at |
| 178 |
<path>/root/.config/openbox/menu.xml</path>. You can then copy the file, and |
| 179 |
overwrite either your user-specific <path>menu.xml</path> or the system-wide |
| 180 |
one (both mentioned above): |
| 181 |
</p> |
| 182 |
|
| 183 |
<pre caption="Overwriting the default menu.xml files"> |
| 184 |
<comment>(Creating or overwriting your user-specific menu)</comment> |
| 185 |
# <i>mv /root/.config/openbox/menu.xml /home/$USER/.config/openbox/menu.xml</i> |
| 186 |
|
| 187 |
OR |
| 188 |
|
| 189 |
<comment>(Overwriting your system-wide menu)</comment> |
| 190 |
# <i>mv /root/.config/openbox/menu.xml /etc/xdg/openbox/menu.xml</i> |
| 191 |
</pre> |
| 192 |
|
| 193 |
<impo> |
| 194 |
It is a good idea to use MenuMaker to generate a default menu, as it will have |
| 195 |
the Openbox root-menu items. These items include a virtual desktop switcher, |
| 196 |
and the commands to restart and exit your Openbox session. |
| 197 |
</impo> |
| 198 |
|
| 199 |
<p> |
| 200 |
When you open up the <path>menu.xml</path> file in your favourite editor (nano, |
| 201 |
for example), you will notice that the XML tags used are very human-readable |
| 202 |
and easily understandable. You may choose to modify the default file to fit |
| 203 |
your needs, or you may want to write it from scratch (don't worry, it's really |
| 204 |
not that difficult). The basic syntax for the menu XML is as follows: |
| 205 |
</p> |
| 206 |
|
| 207 |
<pre caption="Editing the menu.xml file"><![CDATA[ |
| 208 |
<?xml version="1.0" encoding="UTF-8"?> |
| 209 |
<openbox_menu> |
| 210 |
<separator label="<i>NAME_OF_SEPARATOR</i>"> |
| 211 |
<menu id="<i>IDENTIFIER</i>" label="<i>NAME_OF_MENU</i>"> |
| 212 |
<item label="<i>NAME_OF_PROGRAM</i>"> |
| 213 |
<action name="execute"><execute><i>/LOCATION/OF/BINARY</i></execute></action> |
| 214 |
</item> |
| 215 |
</menu> |
| 216 |
</openbox_menu> |
| 217 |
]]></pre> |
| 218 |
|
| 219 |
<p> |
| 220 |
Simply replace anything in <c>BLUE CAPS</c> with your information. |
| 221 |
</p> |
| 222 |
|
| 223 |
</body> |
| 224 |
</section> |
| 225 |
|
| 226 |
<section> |
| 227 |
<title>Openbox theme and behaviour configuration</title> |
| 228 |
<body> |
| 229 |
|
| 230 |
<p> |
| 231 |
Aside from being minimalistic and lightweight, Openbox is also surprisingly |
| 232 |
customisable and flexible. As a user, you can easily change various settings |
| 233 |
related to theme, appearance, window placement, docking, and more. There are |
| 234 |
two options for configuring these settings within Openbox. You may either |
| 235 |
manually edit the <path>~/.config/openbox/rc.xml</path> file, or you may want a |
| 236 |
GUI to help you quickly change settings. |
| 237 |
</p> |
| 238 |
|
| 239 |
<p> |
| 240 |
If you want to manually edit the <path>rc.xml</path> file, you simply open up |
| 241 |
your favourite text editor and start making changes. You might want to make a |
| 242 |
backup of the original file just in case, and store it in a location like |
| 243 |
<path>~/.config/openbox/rc.xml.default</path>. There are plenty of comments |
| 244 |
within the document itself that should help you with editing. Alternatively, |
| 245 |
you may want to look at the <uri |
| 246 |
link="http://icculus.org/openbox/index.php/Help:Contents#Configuration">Openbox |
| 247 |
configuration guides</uri>. |
| 248 |
</p> |
| 249 |
|
| 250 |
<p> |
| 251 |
If manually editing the <path>rc.xml</path> file doesn't sound like your cup of |
| 252 |
tea, you may want to use the GTK+ application to manage your themes and |
| 253 |
behaviours in Openbox. The application that you will use is called ObConf, and |
| 254 |
can be installed on your system just as easily as was Openbox itself. |
| 255 |
</p> |
| 256 |
|
| 257 |
<pre caption="Installing ObConf"> |
| 258 |
# <i>emerge obconf</i> |
| 259 |
</pre> |
| 260 |
|
| 261 |
<p> |
| 262 |
You can then open the configurator by typing <c>obconf</c> in your terminal. |
| 263 |
Next, you can go and add an entry for ObConf into your <path>menu.xml</path> so |
| 264 |
it will show up in your Openbox menu. |
| 265 |
</p> |
| 266 |
|
| 267 |
</body> |
| 268 |
</section> |
| 269 |
<section> |
| 270 |
<title>Autostart configuration</title> |
| 271 |
<body> |
| 272 |
|
| 273 |
<p> |
| 274 |
As mentioned above, you don't see a whole lot when you issue the <c>startx</c> |
| 275 |
command for the first time after installing Openbox. In addition to customising |
| 276 |
your menus and changing the behaviour of the window manager, you will probably |
| 277 |
want to have some programs automatically start with your Openbox session. There |
| 278 |
is an easily-editable <path>autostart.sh</path> script that allows you to do |
| 279 |
just that. Just like with the <path>menu.xml</path> file, there are two |
| 280 |
different locations of the <path>autostart.sh</path> script--the system-wide |
| 281 |
(<path>/etc/xdg/openbox/autostart.sh</path>), and the user-defined |
| 282 |
(<path>~/.config/openbox/autostart.sh</path>). |
| 283 |
</p> |
| 284 |
|
| 285 |
<p> |
| 286 |
In the default <path>autostart.sh</path>, you will notice a bunch of lines |
| 287 |
calling for programs like the gnome-settings-daemon, XDG, and others. These |
| 288 |
lines will generate errors upon logout if you don't have the programs installed |
| 289 |
and configured. The easiest thing to do when getting started with Openbox is to |
| 290 |
just comment out these lines by using the # symbol.</p> |
| 291 |
|
| 292 |
<pre caption="Commenting out lines in autostart.sh"> |
| 293 |
# Run XDG autostart things. By default don't run anything desktop-specific |
| 294 |
# DESKTOP_ENV="" |
| 295 |
# if which /usr/lib/openbox/xdg-autostart >/dev/null; then |
| 296 |
# /usr/lib/openbox/xdg-autostart $DESKTOP_ENV |
| 297 |
# fi |
| 298 |
</pre> |
| 299 |
|
| 300 |
<p> |
| 301 |
In the above example, the comment symbol (#) was added before each line. The |
| 302 |
commenting method is preferred to just deleting the lines because you may want |
| 303 |
to add support for some of those startup items at a later time. Thus, leaving |
| 304 |
the default lines in place could ease that process. |
| 305 |
</p> |
| 306 |
|
| 307 |
<p> |
| 308 |
Adding your own programs to the <path>autostart.sh</path> script is as easy as |
| 309 |
writing in the program name for many applications. For instance, if you have |
| 310 |
Conky (a lightweight system monitor) installed, and want it to start |
| 311 |
automatically with your Openbox session, you simply add the following line to |
| 312 |
your <path>autostart.sh</path>: |
| 313 |
</p> |
| 314 |
|
| 315 |
<pre caption="Adding Conky to your autostart.sh"> |
| 316 |
conky & |
| 317 |
</pre> |
| 318 |
|
| 319 |
<p> |
| 320 |
The ampersand (&) after the command allows that application to load up in |
| 321 |
the background. You will most likely want to load all the applications in your |
| 322 |
<path>autostart.sh</path> script in the background because doing so will let |
| 323 |
Openbox and other programs load without the previous one finishing. |
| 324 |
</p> |
| 325 |
|
| 326 |
</body> |
| 327 |
</section> |
| 328 |
|
| 329 |
<section> |
| 330 |
<title>Setting the background</title> |
| 331 |
<body> |
| 332 |
|
| 333 |
<p> |
| 334 |
Some things that you might take for granted in bigger desktop environments are |
| 335 |
not included by default in Openbox. One such thing is setting your desktop |
| 336 |
background. In order to place an image as your wallpaper, you will need to |
| 337 |
emerge a program like feh or nitrogen. Feh is a simple image viewer that can |
| 338 |
also set the background, <e>and</e> it can easily be put into the autostart |
| 339 |
script. Once you have emerged feh, you can issue the following command to set |
| 340 |
the background: |
| 341 |
</p> |
| 342 |
|
| 343 |
<pre caption="Using feh to set the background image"> |
| 344 |
<comment>(feh has many other options instead of --bg-scale (which will scale the image |
| 345 |
to the screen dimensions). Consult the feh documentation.)</comment> |
| 346 |
$ <i>feh --bg-scale /path/to/image.jpg</i> |
| 347 |
</pre> |
| 348 |
|
| 349 |
<p> |
| 350 |
Once you have set the background manually, a file called <path>.fehbg</path> |
| 351 |
will be created in your home directory. This file simply contains the above |
| 352 |
command that you just entered in the terminal, and is automatically updated |
| 353 |
when you issue a different background command. Now, to set your background |
| 354 |
automatically upon login, you can add the following line to your |
| 355 |
<path>autostart.sh</path> script: |
| 356 |
</p> |
| 357 |
|
| 358 |
<pre caption="Using feh to set the background image"> |
| 359 |
source $HOME/.fehbg & |
| 360 |
</pre> |
| 361 |
|
| 362 |
</body> |
| 363 |
</section> |
| 364 |
</chapter> |
| 365 |
|
| 366 |
<chapter> |
| 367 |
<title>Programs to use with Openbox</title> |
| 368 |
<section> |
| 369 |
<title>This list</title> |
| 370 |
<body> |
| 371 |
|
| 372 |
<p> |
| 373 |
The following is a list of some programs which you might want to use within |
| 374 |
your Openbox environment. While the list contains numerous terminal emulators, |
| 375 |
file managers, panels, and more, it should by no means be considered |
| 376 |
exhaustive. If none of the programs listed fit your needs, please check the |
| 377 |
appropriate categories in Portage for more options. |
| 378 |
</p> |
| 379 |
|
| 380 |
</body> |
| 381 |
</section> |
| 382 |
<section> |
| 383 |
|
| 384 |
<title>Terminal emulators</title> |
| 385 |
<body> |
| 386 |
|
| 387 |
<ul> |
| 388 |
<li> |
| 389 |
<uri link="http://packages.gentoo.org/package/x11-terms/evilvte"> EvilVTE</uri> |
| 390 |
is an extremely lightweight terminal emulator based on (you guessed it) VTE. It |
| 391 |
supports tabs, multiple encodings, as well as an easy and extensible |
| 392 |
configuration file. |
| 393 |
</li> |
| 394 |
<li> |
| 395 |
<uri link="http://packages.gentoo.org/package/x11-terms/mrxvt">Mrxvt</uri> is a |
| 396 |
multi-tabbed rxvt clone with XFT, transparent background and CJK support. It |
| 397 |
also features session support for each tab. |
| 398 |
</li> |
| 399 |
<li> |
| 400 |
<uri link="http://packages.gentoo.org/package/x11-terms/aterm">Aterm</uri> |
| 401 |
supports transparency and backwards compatibility with rxvt. It was originally |
| 402 |
designed for the AfterStep window manager, but easily integrates with other |
| 403 |
environments. |
| 404 |
</li> |
| 405 |
<li> |
| 406 |
<uri link="http://packages.gentoo.org/package/x11-terms/eterm">Eterm</uri> is a |
| 407 |
terminal based on vt102 and designed to be a more feature-rich replacement for |
| 408 |
xterm. |
| 409 |
</li> |
| 410 |
<li> |
| 411 |
<uri |
| 412 |
link="http://packages.gentoo.org/package/x11-terms/rxvt-unicode">Rxvt-unicode</uri> |
| 413 |
is a clone of rxvt that supports Unicode, daemons, embedded perl, and multiple |
| 414 |
fonts simultaneously. |
| 415 |
</li> |
| 416 |
<li> |
| 417 |
<uri |
| 418 |
link="http://packages.gentoo.org/package/x11-terms/terminal">Terminal</uri> is |
| 419 |
the VTE-based default for the Xfce desktop environment. It is a little on the |
| 420 |
bloated side for use with Openbox, as it pulls in many libraries for Xfce. |
| 421 |
</li> |
| 422 |
</ul> |
| 423 |
</body> |
| 424 |
</section> |
| 425 |
|
| 426 |
<section> |
| 427 |
<title>Desktop management</title> |
| 428 |
<body> |
| 429 |
|
| 430 |
<ul> |
| 431 |
<li> |
| 432 |
Though <uri |
| 433 |
link="http://packages.gentoo.org/package/x11-misc/pcmanfm">PCManFM</uri> is |
| 434 |
mainly a file manager, it also gives you the option to manage the desktop |
| 435 |
background (instead of using feh or nitrogen) and draw desktop icons. It should |
| 436 |
be noted that with the current release (0.5), it is not readily possible to get |
| 437 |
rid of the default "My Documents" icon on the desktop. |
| 438 |
</li> |
| 439 |
<li> |
| 440 |
<uri link="http://packages.gentoo.org/package/x11-misc/idesk">iDesk</uri> is a |
| 441 |
simple program used to draw desktop icons. It supports shadowed and |
| 442 |
anti-aliased fonts, PNG images, "snap-to-grid" placement, and changing the |
| 443 |
desktop background. |
| 444 |
</li> |
| 445 |
</ul> |
| 446 |
|
| 447 |
</body> |
| 448 |
</section> |
| 449 |
<section> |
| 450 |
<title>Panels</title> |
| 451 |
<body> |
| 452 |
|
| 453 |
<ul> |
| 454 |
<li> |
| 455 |
Currently not in the official tree, <uri |
| 456 |
link="http://code.google.com/p/tint2/">Tint2</uri> is a simple panel and |
| 457 |
taskbar specifically made for Openbox3 (based on the ttm code). It supports |
| 458 |
colour/transparency, a clock, and drag and drop between virtual desktops. |
| 459 |
Currently, it is not available in the official Portage tree, but is available |
| 460 |
in overlays. |
| 461 |
</li> |
| 462 |
<li> |
| 463 |
<uri link="http://packages.gentoo.org/package/x11-misc/pypanel">PyPanel</uri> |
| 464 |
is an easily customised panel written in Python and C. It features |
| 465 |
transparency, shading, tinting, location and layout configuration, font type, |
| 466 |
autohiding, application launcher, clock, and more. |
| 467 |
</li> |
| 468 |
<li> |
| 469 |
<uri link="http://packages.gentoo.org/package/lxde-base/lxpanel">LXPanel</uri> |
| 470 |
is the default panel and taskbar from LXDE. It features a launcher, menu, |
| 471 |
clock, and a GUI-based configurator. It is feature-rich while depending on very |
| 472 |
few packages, making it a good choice for a lean system. |
| 473 |
</li> |
| 474 |
<li> |
| 475 |
<uri |
| 476 |
link="http://packages.gentoo.org/package/xfce-base/xfce4-panel">Xfce4-panel</uri> |
| 477 |
is the default panel from the Xfce desktop environment. It supports application |
| 478 |
launchers, detachable menus, a pager, tasklist, clock, and more. It does, |
| 479 |
however, require a few of the Xfce libraries which are not dependencies of some |
| 480 |
other panels. |
| 481 |
</li> |
| 482 |
</ul> |
| 483 |
|
| 484 |
</body> |
| 485 |
</section> |
| 486 |
<section> |
| 487 |
<title>File Managers</title> |
| 488 |
<body> |
| 489 |
|
| 490 |
<ul> |
| 491 |
<li> |
| 492 |
<uri link="http://packages.gentoo.org/package/x11-misc/pcmanfm">PCManFM</uri> |
| 493 |
is the lightweight filemanager from LXDE. It supports tabbed browsing, drag and |
| 494 |
drop, thumnails for images, bookmarks, volume management, searching, and more. |
| 495 |
It also provides supports for managing the desktop background and drawing |
| 496 |
desktop icons (both optionally). |
| 497 |
</li> |
| 498 |
<li> |
| 499 |
<uri link="http://packages.gentoo.org/package/xfce-base/thunar">Thunar</uri> is |
| 500 |
the standard file manager from Xfce. It features a bulk renamer, |
| 501 |
user-customisable actions, and an extension framework. Since it depends on many |
| 502 |
Xfce libraries, it isn't as lightweight as PCManFM, but it's still slimmed down |
| 503 |
by comparison to other file managers like Nautilus (from GNOME), and Konqueror |
| 504 |
(from KDE). |
| 505 |
</li> |
| 506 |
<li> |
| 507 |
<uri |
| 508 |
link="http://packages.gentoo.org/package/gnome-base/nautilus">Nautilus</uri> is |
| 509 |
the powerful file manager from the GNOME desktop environment. It features |
| 510 |
volume management, thumbnails for images, searching, and some system |
| 511 |
configuration. As it depends on many of the GNOME libraries for proper |
| 512 |
function, it can seem a heavy compared to some of the other file managers. |
| 513 |
</li> |
| 514 |
<li> |
| 515 |
<uri link="http://packages.gentoo.org/package/app-misc/gentoo">Gentoo</uri> (no |
| 516 |
relation to this glorious Linux distribution) is a two-pane style file manager |
| 517 |
based on GTK+ 1.x. It is incredibly lightweight, but lacks a majority of the |
| 518 |
features now prominent in modern file managers. It should definitely be |
| 519 |
considered for older hardware, or if you are wanting a barebones setup. |
| 520 |
</li> |
| 521 |
<li> |
| 522 |
<uri link="http://packages.gentoo.org/package/app-misc/emelfm2">emelFM2</uri> |
| 523 |
is another file manager in the vein of Midnight Commander. It features a |
| 524 |
three-pane window, and is requires GTK+ 2.6.x or higher. As with the Gentoo |
| 525 |
file manager (listed above), it is barebones and does not include many features |
| 526 |
prevalent in newer file managers. |
| 527 |
</li> |
| 528 |
</ul> |
| 529 |
</body> |
| 530 |
</section> |
| 531 |
<section> |
| 532 |
<title>Miscellaneous</title> |
| 533 |
<body> |
| 534 |
|
| 535 |
<ul> |
| 536 |
<li> |
| 537 |
<uri link="http://packages.gentoo.org/package/app-admin/conky">Conky</uri> is a |
| 538 |
lightweight system monitor that can natively display over 250 objects, |
| 539 |
including date and time, CPU usage, memory usage, IMAP/POP3 email, top |
| 540 |
processes, and even info from your music player. It is highly customisable both |
| 541 |
in appearance and data display. |
| 542 |
</li> |
| 543 |
<li> |
| 544 |
<uri link="http://packages.gentoo.org/package/media-gfx/feh">feh</uri> is a |
| 545 |
simple image viewer that runs from the terminal, but it also has many other |
| 546 |
features. It can display a slideshow of images, create an index print, |
| 547 |
dynamically zoom, and set the desktop background (detailed instructions |
| 548 |
above). |
| 549 |
</li> |
| 550 |
</ul> |
| 551 |
|
| 552 |
</body> |
| 553 |
</section> |
| 554 |
</chapter> |
| 555 |
|
| 556 |
<chapter id="inside-desktop-env"> |
| 557 |
<title>Openbox inside desktop environments</title> |
| 558 |
<section> |
| 559 |
<title>LXDE (default)</title> |
| 560 |
<body> |
| 561 |
|
| 562 |
<p> |
| 563 |
If installing each component of a working environment sounds like a little |
| 564 |
<e>too</e> much customisation, but you still want the flexibility of Openbox, |
| 565 |
you may want to look into a desktop environment that uses Openbox as its |
| 566 |
default window manager. That environment is <uri |
| 567 |
link="http://www.lxde.org/">LXDE</uri>, the Lightweight X Desktop Environment. |
| 568 |
Designed to require even less system resources than Xfce, it is built around |
| 569 |
Openbox and some of the packages mentioned above (like PCManFM and LXpanel). |
| 570 |
</p> |
| 571 |
|
| 572 |
</body> |
| 573 |
</section> |
| 574 |
<section> |
| 575 |
<title>Openbox inside GNOME</title> |
| 576 |
<body> |
| 577 |
|
| 578 |
<p> |
| 579 |
If you already have a GNOME environment installed, you may just want to replace |
| 580 |
the Metacity window manager with Openbox. Fortunately, this is quite a simple |
| 581 |
task! You will need to fire up your favourite editor, open your |
| 582 |
<path>~/.xinitrc</path> file, and put the following command inside it: |
| 583 |
</p> |
| 584 |
|
| 585 |
<pre caption="Adding an Openbox-GNOME session to your .xinitrc"> |
| 586 |
exec openbox-gnome-session |
| 587 |
</pre> |
| 588 |
|
| 589 |
<p> |
| 590 |
If you use GDM or another graphic login manager, you will see a new |
| 591 |
"GNOME/Openbox" option in your session menu. You can simply select that option |
| 592 |
instead of manually editing your <path>~/.xinitrc</path>. |
| 593 |
</p> |
| 594 |
|
| 595 |
<note> |
| 596 |
This method of using Openbox with GNOME has been tested with the GNOME 2.22 |
| 597 |
release. While it seems highly likely that it will work with GNOME 2.24 and |
| 598 |
above, it has not been thoroughly tested as of yet. |
| 599 |
</note> |
| 600 |
|
| 601 |
</body> |
| 602 |
</section> |
| 603 |
<section> |
| 604 |
<title>Openbox inside KDE</title> |
| 605 |
<body> |
| 606 |
|
| 607 |
<p> |
| 608 |
Say you have KDE installed and like it, but you want more flexibility with your |
| 609 |
window management than KWin offers. You can use Openbox as your window manager |
| 610 |
inside of KDE by simply editing your <path>~/.xinitrc</path> file, and |
| 611 |
replacing your current exec command with the following: |
| 612 |
</p> |
| 613 |
|
| 614 |
<pre caption="Adding an Openbox-KDE session to your .xinitrc"> |
| 615 |
exec openbox-kde-session |
| 616 |
</pre> |
| 617 |
|
| 618 |
<p> |
| 619 |
Now when you issue <c>startx</c> you will see KDE, but instead of KWin, you |
| 620 |
will have the customisability of the Openbox window manager. |
| 621 |
</p> |
| 622 |
|
| 623 |
<p> |
| 624 |
If you use KDM or another graphic login manager, you will see a new |
| 625 |
"KDE/Openbox" option in your session menu. You can simply select that option |
| 626 |
instead of manually editing your <path>~/.xinitrc</path>. |
| 627 |
</p> |
| 628 |
|
| 629 |
<note> |
| 630 |
This method of using Openbox with KDE has been tested with the KDE 3.x |
| 631 |
releases. While it seems highly likely that it will work with the KDE 4.x |
| 632 |
series, it has not been thoroughly tested as of yet. |
| 633 |
</note> |
| 634 |
|
| 635 |
</body> |
| 636 |
</section> |
| 637 |
<section> |
| 638 |
<title>Openbox inside Xfce</title> |
| 639 |
<body> |
| 640 |
|
| 641 |
<p> |
| 642 |
If you use Xfce4 and would like to replace xfwm4 with Openbox, you will need to |
| 643 |
go about it a little differently than with KDE or GNOME. Firstly, you need to |
| 644 |
start your normal Xfce session, and open up a terminal. From the terminal, |
| 645 |
issue the following command: |
| 646 |
</p> |
| 647 |
|
| 648 |
<pre caption="Killing xfwm4 and replacing it with Openbox"> |
| 649 |
$ <i>killall xfwm4 ; openbox & exit</i> |
| 650 |
</pre> |
| 651 |
|
| 652 |
<p> |
| 653 |
Secondly, you need to exit out of your Xfce session, and make sure to tick the |
| 654 |
checkbox that says "Save session for future login." This will keep Openbox as |
| 655 |
your default window manager. Thirdly, you will notice that you can't logout |
| 656 |
properly when using the default menu action. To fix this problem, open up your |
| 657 |
<path>menu.xml</path>, and locate this line: |
| 658 |
</p> |
| 659 |
|
| 660 |
<pre caption="Finding the exit action in menu.xml"><![CDATA[ |
| 661 |
<item label="Exit"> |
| 662 |
<action name="Exit"/> |
| 663 |
</item> |
| 664 |
</pre> |
| 665 |
<br /> |
| 666 |
and change it to this: |
| 667 |
<br /> |
| 668 |
<pre caption="Replacing the exit action in menu.xml"> |
| 669 |
<item label="Exit"> |
| 670 |
<action name="Execute"> |
| 671 |
<command>xfce4-session-logout</command> |
| 672 |
</action> |
| 673 |
</item> |
| 674 |
]]></pre> |
| 675 |
|
| 676 |
<note> |
| 677 |
With Xfce4, the root-menu provided by Xfdesktop will be used instead of the |
| 678 |
Openbox root-menu. |
| 679 |
</note> |
| 680 |
|
| 681 |
</body> |
| 682 |
</section> |
| 683 |
</chapter> |
| 684 |
|
| 685 |
<chapter> |
| 686 |
<title>Further documentation</title> |
| 687 |
|
| 688 |
<section> |
| 689 |
<title>External resources</title> |
| 690 |
<body> |
| 691 |
|
| 692 |
<p> |
| 693 |
While this document will easily take you through the inital installation and |
| 694 |
customisation of Openbox, it is by no means the only reference on the topic. |
| 695 |
There are several other resources that will aid you in creating your perfect |
| 696 |
Openbox setup. Some of them are listed below: |
| 697 |
</p> |
| 698 |
|
| 699 |
<ul> |
| 700 |
<li> |
| 701 |
On <uri link="http://icculus.org/openbox/index.php/Main_Page">The Official |
| 702 |
Openbox website</uri> you will find more detailed information regarding |
| 703 |
theming, creating menus (including pipe menus), autostart scripting, and much |
| 704 |
more. This site also has information regarding new releases, upgrades, and |
| 705 |
instructions on how you can contribute to development. |
| 706 |
</li> |
| 707 |
<li> |
| 708 |
The <uri link="http://urukrama.wordpress.com/openbox-guide/">Urukrama's Guide |
| 709 |
to Openbox</uri> blog contains a plethora of information about switching GTK+ |
| 710 |
themes, setting up keybindings, desktop effects, and other programs to use in |
| 711 |
conjunction with Openbox. Though the tutorial was originally written for use |
| 712 |
with Ubuntu, everything should be applicable to Gentoo (and other Linux |
| 713 |
distributions for that matter). |
| 714 |
</li> |
| 715 |
<li> |
| 716 |
<uri link="http://www.box-look.org/">Box-Look</uri> provides numerous themes, |
| 717 |
icons, wallpapers, fonts, and tools to be used with Openbox (as well as the |
| 718 |
other *box window managers like Fluxbox, Blackbox, PekWM, etc.) |
| 719 |
</li> |
| 720 |
</ul> |
| 721 |
|
| 722 |
</body> |
| 723 |
</section> |
| 724 |
</chapter> |
| 725 |
</guide> |
Archives