个人工具

“UbuntuHelp:Openbox”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
(New page: {{From|https://help.ubuntu.com/community/Openbox}} {{Languages|php5}} '''Openbox is a lightweight window manager using [http://www.freedesktop.org/ freedesktop] standards.''' It can be u...)
 
 
(未显示2个用户的14个中间版本)
第1行: 第1行:
 
{{From|https://help.ubuntu.com/community/Openbox}}
 
{{From|https://help.ubuntu.com/community/Openbox}}
{{Languages|php5}}
+
{{Languages|UbuntuHelp:Openbox}}
 
+
'''Openbox is a lightweight window manager using [http://www.freedesktop.org/ freedesktop] standards.''' It can be used either as a replacement for the default Gnome window manager -- [[UbuntuHelp:Metacity|Metacity]] -- or as a standalone desktop environment.
 
+
'''Openbox is a lightweight window manager using [http://www.freedesktop.org/ freedesktop] standards.''' It can be used either as a replacement for the default Gnome window manager -- [[UbuntuHelp:Metacity]] -- or as a standalone desktop environment.
+
 
+
 
== What is Openbox? ==
 
== What is Openbox? ==
 
 
To answer that question, it's important to know the difference between a ''window manager'' and a ''desktop environment''.
 
To answer that question, it's important to know the difference between a ''window manager'' and a ''desktop environment''.
 
 
A ''window manager'' is the program which draws on your screen the "box" in which the program is run. A window manager controls how your program window works, looks and acts. It decides what window decorations to use and gives you a way to move the windows, hide them, resize them, minimize them and close them. It controls what buttons you push to do those things, and what keys you press to make those things happen.
 
A ''window manager'' is the program which draws on your screen the "box" in which the program is run. A window manager controls how your program window works, looks and acts. It decides what window decorations to use and gives you a way to move the windows, hide them, resize them, minimize them and close them. It controls what buttons you push to do those things, and what keys you press to make those things happen.
 
 
On the other hand, a ''desktop environment'' minds the entire desktop. It provides a taskbar, a system tray, a login manager, additional menus or perhaps screensavers and desktop icons. It might include a file manager, a text editor or some other accessory programs, too.
 
On the other hand, a ''desktop environment'' minds the entire desktop. It provides a taskbar, a system tray, a login manager, additional menus or perhaps screensavers and desktop icons. It might include a file manager, a text editor or some other accessory programs, too.
 
 
Openbox is a ''window manager'', not a ''desktop environment''. Openbox is only responsible for maintaining the windows you open on your screen -- nothing else. That means installing Openbox won't give you easy menu access to wallpaper options, a taskbar or system panel, or most of those other doo-dads. It does, however, give you a framework to build incorporate other programs that do those things -- and usually with a greater degree of freedom over the style and interface.
 
Openbox is a ''window manager'', not a ''desktop environment''. Openbox is only responsible for maintaining the windows you open on your screen -- nothing else. That means installing Openbox won't give you easy menu access to wallpaper options, a taskbar or system panel, or most of those other doo-dads. It does, however, give you a framework to build incorporate other programs that do those things -- and usually with a greater degree of freedom over the style and interface.
 
 
Openbox can be used alone, without a desktop environment, or it can be used to replace the window manager in a complete desktop environment. Either way is acceptable.
 
Openbox can be used alone, without a desktop environment, or it can be used to replace the window manager in a complete desktop environment. Either way is acceptable.
 
 
=== Features and benefits ===
 
=== Features and benefits ===
 
 
* '''Minimal overhead''', which makes it ideal for lightweight systems, older hardware or speed demons;
 
* '''Minimal overhead''', which makes it ideal for lightweight systems, older hardware or speed demons;
 
* '''Few dependencies''', which again is appealing to lightweight or minimal systems;
 
* '''Few dependencies''', which again is appealing to lightweight or minimal systems;
第28行: 第18行:
 
* Multi-head '''Xinerama support''' for dual monitor output;
 
* Multi-head '''Xinerama support''' for dual monitor output;
 
* And above all, '''SPEED'''.
 
* And above all, '''SPEED'''.
 
 
=== Disadvantages ===
 
=== Disadvantages ===
 
 
* Sparse, which some people find appealing but others dislike;
 
* Sparse, which some people find appealing but others dislike;
 
* It can take a while to set up, and even once it is set up, changing a style or theme can be additional work;
 
* It can take a while to set up, and even once it is set up, changing a style or theme can be additional work;
第37行: 第25行:
 
* Requires some maintenance, since it doesn't "set itself up;"
 
* Requires some maintenance, since it doesn't "set itself up;"
 
* Some simple tasks, such as automounting CDROMs or attaching digital cameras, will require additional steps.
 
* Some simple tasks, such as automounting CDROMs or attaching digital cameras, will require additional steps.
 
 
== Installing ==
 
== Installing ==
 
 
Openbox is in the ''universe'' repository; make sure your [[UbuntuHelp:AddingRepositoriesHowto| additional repositories]] are enabled before proceeding any further.
 
Openbox is in the ''universe'' repository; make sure your [[UbuntuHelp:AddingRepositoriesHowto| additional repositories]] are enabled before proceeding any further.
 
 
Either install Openbox from the command line,
 
Either install Openbox from the command line,
 
+
<pre><nowiki>
  <pre><nowiki>
+
 
sudo aptitude install openbox obconf
 
sudo aptitude install openbox obconf
</nowiki></code>
+
</nowiki></pre>
 
+
 
or through the Synaptic Package Manager; mark the ''openbox'' and ''obconf'' packages for installation and apply the changes.
 
or through the Synaptic Package Manager; mark the ''openbox'' and ''obconf'' packages for installation and apply the changes.
 
 
== Openbox on Gnome ==
 
== Openbox on Gnome ==
 
 
Use these instructions only if you're converting an existing Gnome desktop to Openbox.
 
Use these instructions only if you're converting an existing Gnome desktop to Openbox.
 
 
=== Replacing Metacity in Gnome ===
 
=== Replacing Metacity in Gnome ===
 
 
To replace Metacity on a Gnome installation, type this command into a terminal window:
 
To replace Metacity on a Gnome installation, type this command into a terminal window:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
openbox --replace
 
openbox --replace
</nowiki></code>
+
</nowiki></pre>
 
+
 
If you wish to keep Openbox as your default window manager, just save your session on logout.
 
If you wish to keep Openbox as your default window manager, just save your session on logout.
 
 
=== Select the session ===
 
=== Select the session ===
 
 
When you reach the GDM login, clicking on the "Session" button should give you Openbox as an option. Click it to start Openbox after your login.
 
When you reach the GDM login, clicking on the "Session" button should give you Openbox as an option. Click it to start Openbox after your login.
 
 
== Openbox by itself ==
 
== Openbox by itself ==
 
 
Starting Openbox on its own is an easy task. Edit your ''~/.xinitrc'' file and add this line to trigger Openbox when X starts.
 
Starting Openbox on its own is an easy task. Edit your ''~/.xinitrc'' file and add this line to trigger Openbox when X starts.
 
+
<pre><nowiki>
<pre><nowiki>
+
exec openbox-session
exec openbox
+
</nowiki></pre>
</nowiki></code>
+
 
+
 
Of course, without some additional programs and accessories, there's very little to see in a pure Openbox installation. Keep reading for more ideas.
 
Of course, without some additional programs and accessories, there's very little to see in a pure Openbox installation. Keep reading for more ideas.
 
 
== Configuration ==
 
== Configuration ==
 
 
=== menu.xml and rc.xml ===
 
=== menu.xml and rc.xml ===
 
 
Openbox uses two main configuration files: '''rc.xml''', which sets keybindings, desktop names and window behavior; and '''menu.xml''', which contains the instructions for the right-click menu. As you might have guessed, both files are written in XML and can be edited in any text editor program. If you make a mistake and your file is no longer valid XML, Openbox will revert to the default configuration files in /etc/xdg/openbox/.
 
Openbox uses two main configuration files: '''rc.xml''', which sets keybindings, desktop names and window behavior; and '''menu.xml''', which contains the instructions for the right-click menu. As you might have guessed, both files are written in XML and can be edited in any text editor program. If you make a mistake and your file is no longer valid XML, Openbox will revert to the default configuration files in /etc/xdg/openbox/.
 
 
Here's an example of what's inside the menu.xml file.
 
Here's an example of what's inside the menu.xml file.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
<item label="Program_Name">
 
<item label="Program_Name">
 
<action name="Execute">
 
<action name="Execute">
第94行: 第60行:
 
</action>
 
</action>
 
</item>
 
</item>
</nowiki></code>
+
</nowiki></pre>
 
+
 
As you can see, the menus are neatly nested so they can be easily followed. Each entry has an opening tag and a closing tag, and each is clearly readable. rc.xml has a similar structure.
 
As you can see, the menus are neatly nested so they can be easily followed. Each entry has an opening tag and a closing tag, and each is clearly readable. rc.xml has a similar structure.
 
 
For more information about how to hand-edit Openbox's XML files, read over the [http://icculus.org/openbox/ Openbox Web site].
 
For more information about how to hand-edit Openbox's XML files, read over the [http://icculus.org/openbox/ Openbox Web site].
 
 
==== ObMenu ====
 
==== ObMenu ====
 
 
If you're not keen on editing an XML file, there's [http://obmenu.sourceforge.net/ ObMenu]. This is a very small Python program that will allow you to modify your menu with a simple GUI, and save the results back into your menu.xml file. It's fast, easy and you don't have to worry about typos in your menu.xml file.
 
If you're not keen on editing an XML file, there's [http://obmenu.sourceforge.net/ ObMenu]. This is a very small Python program that will allow you to modify your menu with a simple GUI, and save the results back into your menu.xml file. It's fast, easy and you don't have to worry about typos in your menu.xml file.
 
+
Obmenu has been included in the repositories. To install open a terminal and type:
To install it, download the ObMenu package from [http://obmenu.sourceforge.net/download.html here], and decompress it. Next, install its dependencies.
+
<pre><nowiki>
 
+
sudo aptitude install obmenu
<pre><nowiki>
+
</nowiki></pre>
sudo aptitude install python2.5 python-glade2 python-gtk2
+
The command "obmenu" runs the program.
</nowiki></code>
+
 
+
Now enter this command to install the program:
+
 
+
<pre><nowiki>
+
sudo python setup.py install
+
</nowiki></code>
+
 
+
If all goes well (and it probably will), you should be able to bring up the ObMenu interface by entering the ''obmenu'' command in a terminal.
+
 
+
 
== Customizing ==
 
== Customizing ==
 
 
Openbox might just be a window manager, but there are plenty of opportunities to add some flair.
 
Openbox might just be a window manager, but there are plenty of opportunities to add some flair.
 
 
=== Obconf ===
 
=== Obconf ===
 
 
Obconf is a handy program to customise Openbox. It allows for the selection of themes, some window behaviour, the number of desktops, and the dock. You can start Obconf with this command:
 
Obconf is a handy program to customise Openbox. It allows for the selection of themes, some window behaviour, the number of desktops, and the dock. You can start Obconf with this command:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
obconf
 
obconf
</nowiki></code>
+
</nowiki></pre>
 
+
 
'''Note:''' Edgy (Ubuntu 6.10) users should be aware of a small discrepancy in Obconf that might prevent it from running. You can correct that with these commands ...
 
'''Note:''' Edgy (Ubuntu 6.10) users should be aware of a small discrepancy in Obconf that might prevent it from running. You can correct that with these commands ...
 
+
<pre><nowiki>
<pre><nowiki>
+
 
cd /usr/lib
 
cd /usr/lib
 
sudo ln libobparser.so.0.4.0 libobparser.so.1
 
sudo ln libobparser.so.0.4.0 libobparser.so.1
 
sudo ln libobrender.so.0.4.0 libobrender.so.1
 
sudo ln libobrender.so.0.4.0 libobrender.so.1
</nowiki></code>
+
</nowiki></pre>
 
+
 
Entering ''obconf'' in an X terminal window should now trigger the Obconf dialogue.
 
Entering ''obconf'' in an X terminal window should now trigger the Obconf dialogue.
 
 
==== Themes ====
 
==== Themes ====
 
 
A variety of default themes are available in the repositories; you can install them via Synaptic, or through a terminal command:
 
A variety of default themes are available in the repositories; you can install them via Synaptic, or through a terminal command:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install openbox-themes
 
sudo aptitude install openbox-themes
</nowiki></code>
+
</nowiki></pre>
 
+
 
A number of third-party sites also offer themes as compressed packages. Download the one you like, then decompress it into the ''~/.themes'' folder.
 
A number of third-party sites also offer themes as compressed packages. Download the one you like, then decompress it into the ''~/.themes'' folder.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
tar -xzvf compressed-theme-package-that-you-downloaded.tar.gz -C ~/.themes/
 
tar -xzvf compressed-theme-package-that-you-downloaded.tar.gz -C ~/.themes/
</nowiki></code>
+
</nowiki></pre>
 
+
 
Don't forget the trailing slash. Now you can use Obconf to select your theme.
 
Don't forget the trailing slash. Now you can use Obconf to select your theme.
 
 
==== Modifying themes ====
 
==== Modifying themes ====
 
 
The better part of a theme package is contained in a text file called ''themerc'' inside some nested folders in ''~/.themes''. If you want to fine-tune a theme (such as, make the letters bigger, or change the width of a window handle, or pick a different color), find the correct file in your ''~/.themes'' folder and edit it as you like.
 
The better part of a theme package is contained in a text file called ''themerc'' inside some nested folders in ''~/.themes''. If you want to fine-tune a theme (such as, make the letters bigger, or change the width of a window handle, or pick a different color), find the correct file in your ''~/.themes'' folder and edit it as you like.
 
 
When you save it, you can reselect the theme with Obconf, and your changes will take effect.
 
When you save it, you can reselect the theme with Obconf, and your changes will take effect.
 
 
=== Wallpaper ===
 
=== Wallpaper ===
 
 
==== feh ====
 
==== feh ====
 
 
A number of programs can handle the responsibility of showing a background image; the most common is a funny little program called ''feh''.
 
A number of programs can handle the responsibility of showing a background image; the most common is a funny little program called ''feh''.
 
 
feh is actually a lightweight image viewer with a number of options, but perhaps the most popular is the ability to draw a desktop background. Pick a wallpaper image and try this command in a terminal.
 
feh is actually a lightweight image viewer with a number of options, but perhaps the most popular is the ability to draw a desktop background. Pick a wallpaper image and try this command in a terminal.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
feh --bg-scale /path/to/your/background/image.jpg
 
feh --bg-scale /path/to/your/background/image.jpg
</nowiki></code>
+
</nowiki></pre>
 
+
 
Feh can handle other file types than just jpg. Once you've picked a wallpaper, feh stores the name in a file called ''.fehbg''. That means you can tell it to restore the wallpaper on the next boot by checking to see what's inside that file. Add this line to your ''~/.xinitrc'' file.
 
Feh can handle other file types than just jpg. Once you've picked a wallpaper, feh stores the name in a file called ''.fehbg''. That means you can tell it to restore the wallpaper on the next boot by checking to see what's inside that file. Add this line to your ''~/.xinitrc'' file.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
eval `cat $HOME/.fehbg` &
 
eval `cat $HOME/.fehbg` &
</nowiki></code>
+
</nowiki></pre>
 
+
===== Nitrogen =====
 +
If you perfer a graphical method for choosing between many background images, perhaps nitrogen is a good option. Nitrogen allows you to choose from many background images from a preset directory, you should add any wallpapers you wish to choose from to this directory.
 +
To use nitrogen, you should add
 +
<pre><nowiki>
 +
nitrogen /path/to/backgroundfiles/
 +
</nowiki></pre>
 +
to your menu.xml file (or alternatively add it to your menu using obmenu.)
 +
Next you must add
 +
<pre><nowiki>
 +
nitrogen --restore
 +
</nowiki></pre>
 +
to your ~/.config/openbox/autostart.sh (You can create this file if it does not exist)
 +
Now you can use your nitrogen entry in your menu to change your wallpaper and the changes will be restored on login.
 
===== Random wallpaper =====
 
===== Random wallpaper =====
 
 
One neat trick available with feh is a random wallpaper on each boot. Make a directory in your home folder called "wallpapers", then put a few background images in it. Then copy this text into a file called ''wallpaper.sh'', and save it anywhere.
 
One neat trick available with feh is a random wallpaper on each boot. Make a directory in your home folder called "wallpapers", then put a few background images in it. Then copy this text into a file called ''wallpaper.sh'', and save it anywhere.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
#!/bin/bash
 
#!/bin/bash
WALLPAPERS="~/wallpapers"
+
WALLPAPERS="$HOME/path_to_your_wallpapers"
ALIST=( `ls -w1 ~/wallpapers` )
+
ALIST=( `ls -w1 $WALLPAPERS` )
RANGE=${#ALIST[@]}
+
RANGE=${#ALIST[*]}
let "number = $RANDOM"
+
SHOW=$(( $RANDOM % $RANGE ))
let LASTNUM="`cat $WALLPAPERS/.last` + $number"
+
let "number = $LASTNUM % $RANGE"
+
echo $number > $WALLPAPERS/.last
+
 
+
feh --bg-scale $WALLPAPERS/${ALIST[$number]}
+
</nowiki></code>
+
  
 +
feh --bg-scale $WALLPAPERS/${ALIST[$SHOW]}
 +
</nowiki></pre>
 
Next make the script executable.
 
Next make the script executable.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
chmod +x wallpaper.sh
 
chmod +x wallpaper.sh
</nowiki></code>
+
</nowiki></pre>
 
+
 
Now add that program to your ~/.xinitrc file, like this.
 
Now add that program to your ~/.xinitrc file, like this.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
./wallpaper.sh
 
./wallpaper.sh
</nowiki></code>
+
</nowiki></pre>
 
+
 
When you log in, the script should be executed, and feh will pick a new wallpaper for your amusement.
 
When you log in, the script should be executed, and feh will pick a new wallpaper for your amusement.
 
 
==== Other options ====
 
==== Other options ====
 
 
feh isn't the only program that can handle drawing a background image. Here are some others.
 
feh isn't the only program that can handle drawing a background image. Here are some others.
 
 
* xsetbg
 
* xsetbg
 
* imagemagick
 
* imagemagick
 
+
* nitrogen
 
Additionally, some file managers have the option of managing your wallpaper.
 
Additionally, some file managers have the option of managing your wallpaper.
 
 
* rox-filer
 
* rox-filer
 
* PCManFM
 
* PCManFM
 
* Nautilus, if started without the --no-desktop option, will draw over the background image
 
* Nautilus, if started without the --no-desktop option, will draw over the background image
 
 
=== Desktop icons ===
 
=== Desktop icons ===
 
 
==== iDesk ====
 
==== iDesk ====
 
 
You can add customizable, clickable icons to your desktop with [http://idesk.sourceforge.net/wiki/index.php/Main_Page iDesk]. iDesk is available in the Ubuntu repositories, and is installable from the command line with
 
You can add customizable, clickable icons to your desktop with [http://idesk.sourceforge.net/wiki/index.php/Main_Page iDesk]. iDesk is available in the Ubuntu repositories, and is installable from the command line with
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install idesk
 
sudo aptitude install idesk
</nowiki></code>
+
</nowiki></pre>
 
+
 
Consult the [http://idesk.sourceforge.net/ iDesk wiki] for instructions on how to configure and use iDesk. For icon sets, you may wish to search the repositories, or download them from third-party customization sites, such as [http://www.gnome-look.org Gnome-Look.org] and similar locations.
 
Consult the [http://idesk.sourceforge.net/ iDesk wiki] for instructions on how to configure and use iDesk. For icon sets, you may wish to search the repositories, or download them from third-party customization sites, such as [http://www.gnome-look.org Gnome-Look.org] and similar locations.
 
 
==== Rox-Filer ====
 
==== Rox-Filer ====
 
 
Rox-filer is a file manager, but in addition to handling wallpaper, it also has a ''pinboard'' option, and can manage desktop icons. Install rox-filer with this command:
 
Rox-filer is a file manager, but in addition to handling wallpaper, it also has a ''pinboard'' option, and can manage desktop icons. Install rox-filer with this command:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install rox-filer
 
sudo aptitude install rox-filer
</nowiki></code>
+
</nowiki></pre>
 
+
 
You can set up the pinboard through Rox's menus.
 
You can set up the pinboard through Rox's menus.
 
 
=== Taskbars and pagers ===
 
=== Taskbars and pagers ===
 
 
Some people prefer to use a taskbar or pager to keep track of running programs. Here's a list of applications you can add to your Openbox installation that will handle that task for you.
 
Some people prefer to use a taskbar or pager to keep track of running programs. Here's a list of applications you can add to your Openbox installation that will handle that task for you.
 
+
==== Taskbars ====
* bbpager
+
* [http://wiki.ubuntuusers.de/Pypanel pypanel] ('''Note:''' For Ubuntu 6.10 users, the PyPanel included in the repositories is often reported as broken. Look [http://www.ubuntuforums.org/showthread.php?t=327514 here] for a possible way to fix it.)
* pypanel ('''Note:''' For Ubuntu 6.10 users, the PyPanel included in the repositories is often reported as broken. Look [http://www.ubuntuforums.org/showthread.php?t=327514 here] for a possible way to fix it.)
+
* [http://wiki.ubuntuusers.de/GNOME_Panel gnome-panel]
* gnome-panel
+
* [http://freshmeat.net/projects/fspanel/ fspanel]
* fspanel
+
* [http://wiki.ubuntuusers.de/fbpanel fbpanel]
* fbpanel
+
* [http://freshmeat.net/projects/perlpanel/ perlpanel]
* perlpanel
+
* [http://wiki.ubuntuusers.de/Xfce_Panel xfce4-panel]
* xfce4-panel
+
* [http://code.google.com/p/tint2/ tint2]
 
+
==== Pagers ====
 +
* [http://bbtools.sourceforge.net/index.php bbpager]
 +
* [http://code.google.com/p/neap/ neap]
 
=== System monitors ===
 
=== System monitors ===
 
 
If you're looking for a way to display system information, try these nifty programs.
 
If you're looking for a way to display system information, try these nifty programs.
 
 
* gkrellm, which has a number of floating or docked graphical meters and displays
 
* gkrellm, which has a number of floating or docked graphical meters and displays
 
* adesklets, for similar graphical displays
 
* adesklets, for similar graphical displays
 
* conky, a highly configurable text and graphic output that draws directly to your desktop
 
* conky, a highly configurable text and graphic output that draws directly to your desktop
 
 
If you're working on Openbox in conjunction with a Gnome installation, you might also look into ''gdesklets'', which features some very polished monitors and meters for desktop display.
 
If you're working on Openbox in conjunction with a Gnome installation, you might also look into ''gdesklets'', which features some very polished monitors and meters for desktop display.
 
 
=== GTK themes ===
 
=== GTK themes ===
 
 
Program GUIs might look ugly if you're working on a pure Openbox system. Install gtk-theme-switch and the gtk2-engines package to give yourself a few more appealing options.
 
Program GUIs might look ugly if you're working on a pure Openbox system. Install gtk-theme-switch and the gtk2-engines package to give yourself a few more appealing options.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install gtk-theme-switch gtk2-engines
 
sudo aptitude install gtk-theme-switch gtk2-engines
</nowiki></code>
+
</nowiki></pre>
 
+
 
Bring up the configuration menu with this command, from a terminal or the Openbox right-click menu.
 
Bring up the configuration menu with this command, from a terminal or the Openbox right-click menu.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
switch2
 
switch2
</nowiki></code>
+
</nowiki></pre>
 
+
 
Be sure to search the repositories for other engines that aren't included in the gtk2-engines package.
 
Be sure to search the repositories for other engines that aren't included in the gtk2-engines package.
 
 
You can also try installing a Gnome package that will manage some of the settings for you.
 
You can also try installing a Gnome package that will manage some of the settings for you.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install gnome-settings-daemon
 
sudo aptitude install gnome-settings-daemon
</nowiki></code>
+
</nowiki></pre>
 
+
 
If you prefere an XFCE look, try
 
If you prefere an XFCE look, try
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install xfce-mcs-manager
 
sudo aptitude install xfce-mcs-manager
</nowiki></code>
+
</nowiki></pre>
 
+
Either program will run, depending on what's installed, from openbox autostart.sh.
Both of those programs can be added to your Openbox menu, or started from a terminal.
+
 
+
 
=== Automounting ===
 
=== Automounting ===
 
 
To automount external volumes -- like CDs and USB drives -- you will need a volume manager. Here is the Gnome application that handles that:
 
To automount external volumes -- like CDs and USB drives -- you will need a volume manager. Here is the Gnome application that handles that:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install gnome-volume-manager
 
sudo aptitude install gnome-volume-manager
</nowiki></code>
+
</nowiki></pre>
 
+
 
Kubuntu and Xubuntu share the ivman application, which is installable with:
 
Kubuntu and Xubuntu share the ivman application, which is installable with:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install ivman
 
sudo aptitude install ivman
</nowiki></code>
+
</nowiki></pre>
 
+
 
=== Screensaver ===
 
=== Screensaver ===
 
 
If you're building an Openbox desktop with Gnome already installed, you'll probably already have ''gnome-screensaver'' in place. Pure Openbox fans might want to install ''xscreensaver'', which is more customizable and has a wider variety of screensavers involved.
 
If you're building an Openbox desktop with Gnome already installed, you'll probably already have ''gnome-screensaver'' in place. Pure Openbox fans might want to install ''xscreensaver'', which is more customizable and has a wider variety of screensavers involved.
 
 
Without K/X/Ubuntu in place, installing xscreensaver needs a couple of extra commands:
 
Without K/X/Ubuntu in place, installing xscreensaver needs a couple of extra commands:
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo mkdir /usr/share/backgrounds
 
sudo mkdir /usr/share/backgrounds
 
sudo aptitude install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra
 
sudo aptitude install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra
</nowiki></code>
+
</nowiki></pre>
 
+
 
The first command sets up a default directory that xscreensaver will look for when it runs. If you don't create that directory, you'll get a string of error messages the first time you set the preferences.
 
The first command sets up a default directory that xscreensaver will look for when it runs. If you don't create that directory, you'll get a string of error messages the first time you set the preferences.
 
 
The second command installs xscreensaver and its optional files. xscreensaver in Ubuntu is packaged with several screensaver options enabled, but not installed. As a result, you might see brief error messages when the daemon picks an enabled screensaver that it can't find. Adding those packages puts the missing screensavers in place, which is easier than disabling the absent ones.
 
The second command installs xscreensaver and its optional files. xscreensaver in Ubuntu is packaged with several screensaver options enabled, but not installed. As a result, you might see brief error messages when the daemon picks an enabled screensaver that it can't find. Adding those packages puts the missing screensavers in place, which is easier than disabling the absent ones.
 
 
Now add this command to your ''~/.xinitrc'' file, to start the xscreensaver daemon on boot.
 
Now add this command to your ''~/.xinitrc'' file, to start the xscreensaver daemon on boot.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
xscreensaver --no-splash
 
xscreensaver --no-splash
</nowiki></code>
+
</nowiki></pre>
 
+
 
You can access the xscreensaver preferences panel by running ''xscreensaver-demo'' from the Openbox menu or from a terminal window.
 
You can access the xscreensaver preferences panel by running ''xscreensaver-demo'' from the Openbox menu or from a terminal window.
 
 
=== Run dialogue ===
 
=== Run dialogue ===
 
 
Some people find it convenient to invoke a run dialogue program, which is usually triggered with ALT+F2. You'll need to change the keybinding in the rc.xml file in order to regain that function.
 
Some people find it convenient to invoke a run dialogue program, which is usually triggered with ALT+F2. You'll need to change the keybinding in the rc.xml file in order to regain that function.
 
 
If you are using XFCE components, changing rc.xml to point at ''xfrun4'' might solve the problem. If not, consider installing the ''gmrun'' program.
 
If you are using XFCE components, changing rc.xml to point at ''xfrun4'' might solve the problem. If not, consider installing the ''gmrun'' program.
 
+
<pre><nowiki>
<pre><nowiki>
+
 
sudo aptitude install gmrun
 
sudo aptitude install gmrun
</nowiki></code>
+
</nowiki></pre>
 
+
 
Change your rc.xml file to point to ''gmrun''; you don't have to add it to your ''.xinitrc'' file, though.
 
Change your rc.xml file to point to ''gmrun''; you don't have to add it to your ''.xinitrc'' file, though.
 
+
== Other window managers ==
== Other lightweight window managers ==
+
 
+
 
=== To replace Metacity ===
 
=== To replace Metacity ===
 
+
As an alternative to [[UbuntuHelp:Metacity|Metacity]], consider these window managers.
As an alternative to [[UbuntuHelp:Metacity]], consider these window managers.
+
* xfwm4: This is the default window manager for the XFCE4 desktop environment, and is a very comprehensive substitute. Instructions on replacing [[UbuntuHelp:Metacity|Metacity]] with XFCE4 are found [http://www.ubuntuforums.org/showthread.php?t=88393 here].
 
+
* compiz: Compiz is a modern window manager that has many effects, such as animations, decoration opacity and provides its own composite manager.
* xfwm4: This is the default window manager for the XFCE4 desktop environment, and is a very comprehensive substitute. Instructions on replacing [[UbuntuHelp:Metacity]] with XFCE4 are found [http://www.ubuntuforums.org/showthread.php?t=88393 here].
+
* E17: Enlightenment provides a full desktop environment, based around speed and attractiveness. This includes the window manager and a desktop shell.
* Fluxbox: Fluxbox is a very attractive, very lightweight window manager that is highly customizable and has a very strong following. To replace [[UbuntuHelp:Metacity]] with [[UbuntuHelp:Fluxbox]], check [http://www.ubuntuforums.org/showthread.php?t=63734 this thread] in the forums.
+
 
+
 
=== Standalone ===
 
=== Standalone ===
 
 
Here are some alternatives to Openbox for standalone window managers and desktop environments.
 
Here are some alternatives to Openbox for standalone window managers and desktop environments.
 
+
* [[UbuntuHelp:FVWM|FVWM]]: FVWM is a traditional window manager with a long history in the Linux community. It is highly customizable, very flexible and has a very slim profile.
* [[UbuntuHelp:FVWM]]: FVWM is a traditional window manager with a long history in the Linux community. It is highly customizable, very flexible and has a very slim profile.
+
* [[UbuntuHelp:FVWM-Crystal|FVWM-Crystal]]: FVWM is set of configuration files that sits atop of FVWM, and is installable as a complete desktop environment with integrated audio controls, screensaver options and wallpaper control. It's also one of the prettiest options available to older hardware.
* [[UbuntuHelp:FVWM-Crystal]]: FVWM is set of configuration files that sits atop of FVWM, and is installable as a complete desktop environment with integrated audio controls, screensaver options and wallpaper control. It's also one of the prettiest options available to older hardware.
+
* [[UbuntuHelp:Fluxbox|Fluxbox]]: Fluxbox is a window manager intended to be lightweight and fast, it is based on the Blackbox 0.61.1 code. If you find you enjoy working with Fluxbox, the [http://www.fluxbuntu.org/ Fluxbuntu] project might be for you.
* [[UbuntuHelp:Fluxbox]]: Fluxbox is a window manager intended to be lightweight, fast and beautiful. It achieves all of those things, and more. If you find you enjoy working with Fluxbox, the [http://www.fluxbuntu.org/ Fluxbuntu] project might be for you.
+
* [[UbuntuHelp:IceWM|IceWM]]: [[UbuntuHelp:IceWM|IceWM]] is likewise a clean and svelte window manager, but keeps a "traditional" desktop look that some users prefer.
* [[UbuntuHelp:IceWM]]: IceWM is likewise a clean and svelte window manager, but keeps a "traditional" desktop look that some users prefer.
+
* [[UbuntuHelp:Blackbox|Blackbox]]: Blackbox served as the basis for Openbox, although Openbox has been completely rewritten in past years. Blackbox is still available, and still a popular option.
* [[UbuntuHelp:Blackbox]]: Blackbox served as the basis for Openbox, although Openbox has been completely rewritten in past years. Blackbox is still available, and still a popular option.
+
 
* XFCE: XFCE serves as the underpinnings for [http://www.xubuntu.org/ Xubuntu], a fully supported Ubuntu variant complete with an office suite, networking interfaces, e-mail clients, and more. The project began as an option to run Ubuntu on older hardware, but has matured into a complete system on par with Kubuntu or Ubuntu. Visit their home page for more information about the project.
 
* XFCE: XFCE serves as the underpinnings for [http://www.xubuntu.org/ Xubuntu], a fully supported Ubuntu variant complete with an office suite, networking interfaces, e-mail clients, and more. The project began as an option to run Ubuntu on older hardware, but has matured into a complete system on par with Kubuntu or Ubuntu. Visit their home page for more information about the project.
 
 
== External links ==
 
== External links ==
 
 
=== Openbox ===
 
=== Openbox ===
 
+
* [http://icculus.org/openbox/ Openbox web site]
* [http://icculus.org/openbox/docs.php?page=toc.html Openbox Web site]
+
* [http://icculus.org/openbox/index.php/Help:Contents Openbox documentation wiki]
 
* [http://www.ubuntuforums.org/showthread.php?t=75471 An Openbox howto on ubuntuforums.org]
 
* [http://www.ubuntuforums.org/showthread.php?t=75471 An Openbox howto on ubuntuforums.org]
* [https://wiki.ubuntu.com/CustomXSession XSession Wiki page]
+
* [[UbuntuWiki:CustomXSession|XSession|Wiki page]]
 
* [http://www.ubuntuforums.org/showthread.php?t=103806 How to build an Oubuntu! desktop]
 
* [http://www.ubuntuforums.org/showthread.php?t=103806 How to build an Oubuntu! desktop]
 
 
=== Openbox themes ===
 
=== Openbox themes ===
 
 
* [http://themes.freshmeat.net/browse/1087/ Freshmeat]
 
* [http://themes.freshmeat.net/browse/1087/ Freshmeat]
* [http://www.boxwhore.org/ boxwhore]
+
* [http://www.box-look.org/index.php?xcontentmode=7402 box-look.org]
 
+
 
=== A sample .xsession file ===
 
=== A sample .xsession file ===
 
 
* [http://www.ubuntuforums.org/showthread.php?t=23998 An example from ubuntuforums.org]
 
* [http://www.ubuntuforums.org/showthread.php?t=23998 An example from ubuntuforums.org]
 
 
=== Other programs ===
 
=== Other programs ===
 
 
* [http://www.linuxbrit.co.uk/feh/ feh Web site]
 
* [http://www.linuxbrit.co.uk/feh/ feh Web site]
 +
* [http://projects.l3ib.org/nitrogen/ nitrogen Web site]
 
* [http://www.muhri.net gkrellm themes]
 
* [http://www.muhri.net gkrellm themes]
 
 
=== Other sites of interest ===
 
=== Other sites of interest ===
 
 
* [http://en.wikipedia.org/wiki/Openbox Wikipedia article on Openbox]
 
* [http://en.wikipedia.org/wiki/Openbox Wikipedia article on Openbox]
 
* [http://gentoo-wiki.com/HOWTO_Openbox Openbox in the Gentoo Linux wiki]
 
* [http://gentoo-wiki.com/HOWTO_Openbox Openbox in the Gentoo Linux wiki]
 
----
 
----
CategoryDocumentation CategoryCleanup
+
-- I'm still of the mind that this page should be split out, with Openbox on Gnome taking the bulk of the previous material, and this staying closer to a "pure Openbox on Ubuntu" explanation. Edit: Scratch that. Openbox+Gnome material can shift to [[UbuntuHelp:ReplaceMetacityWithOpenbox|ReplaceMetacityWithOpenbox]], and link to there from here. -- K.Mandla
 
+
 
+
-- I'm still of the mind that this page should be split out, with Openbox on Gnome taking the bulk of the previous material, and this staying closer to a "pure Openbox on Ubuntu" explanation. Edit: Scratch that. Openbox+Gnome material can shift to ReplaceMetacityWithOpenbox, and link to there from here. -- K.Mandla
+
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2010年5月19日 (三) 23:47的最新版本


Openbox is a lightweight window manager using freedesktop standards. It can be used either as a replacement for the default Gnome window manager -- Metacity -- or as a standalone desktop environment.

What is Openbox?

To answer that question, it's important to know the difference between a window manager and a desktop environment. A window manager is the program which draws on your screen the "box" in which the program is run. A window manager controls how your program window works, looks and acts. It decides what window decorations to use and gives you a way to move the windows, hide them, resize them, minimize them and close them. It controls what buttons you push to do those things, and what keys you press to make those things happen. On the other hand, a desktop environment minds the entire desktop. It provides a taskbar, a system tray, a login manager, additional menus or perhaps screensavers and desktop icons. It might include a file manager, a text editor or some other accessory programs, too. Openbox is a window manager, not a desktop environment. Openbox is only responsible for maintaining the windows you open on your screen -- nothing else. That means installing Openbox won't give you easy menu access to wallpaper options, a taskbar or system panel, or most of those other doo-dads. It does, however, give you a framework to build incorporate other programs that do those things -- and usually with a greater degree of freedom over the style and interface. Openbox can be used alone, without a desktop environment, or it can be used to replace the window manager in a complete desktop environment. Either way is acceptable.

Features and benefits

  • Minimal overhead, which makes it ideal for lightweight systems, older hardware or speed demons;
  • Few dependencies, which again is appealing to lightweight or minimal systems;
  • Mouse-wheel scrolling of the desktops, for quick access to multiple workspaces;
  • A customisable right-click menu and customisable keybindings written as XML files;
  • Piped menus, where the output of one menu script is piped back into the Openbox menu and used in another (imagine the possibilities!);
  • Plenty of themes, which are all customizable through text files;
  • Written in C;
  • Multi-head Xinerama support for dual monitor output;
  • And above all, SPEED.

Disadvantages

  • Sparse, which some people find appealing but others dislike;
  • It can take a while to set up, and even once it is set up, changing a style or theme can be additional work;
  • Doesn't handle some obvious features, like wallpaper or a taskbar;
  • Relies on outside programs to handle some simple tasks;
  • Requires some maintenance, since it doesn't "set itself up;"
  • Some simple tasks, such as automounting CDROMs or attaching digital cameras, will require additional steps.

Installing

Openbox is in the universe repository; make sure your additional repositories are enabled before proceeding any further. Either install Openbox from the command line,

sudo aptitude install openbox obconf

or through the Synaptic Package Manager; mark the openbox and obconf packages for installation and apply the changes.

Openbox on Gnome

Use these instructions only if you're converting an existing Gnome desktop to Openbox.

Replacing Metacity in Gnome

To replace Metacity on a Gnome installation, type this command into a terminal window:

openbox --replace

If you wish to keep Openbox as your default window manager, just save your session on logout.

Select the session

When you reach the GDM login, clicking on the "Session" button should give you Openbox as an option. Click it to start Openbox after your login.

Openbox by itself

Starting Openbox on its own is an easy task. Edit your ~/.xinitrc file and add this line to trigger Openbox when X starts.

exec openbox-session

Of course, without some additional programs and accessories, there's very little to see in a pure Openbox installation. Keep reading for more ideas.

Configuration

menu.xml and rc.xml

Openbox uses two main configuration files: rc.xml, which sets keybindings, desktop names and window behavior; and menu.xml, which contains the instructions for the right-click menu. As you might have guessed, both files are written in XML and can be edited in any text editor program. If you make a mistake and your file is no longer valid XML, Openbox will revert to the default configuration files in /etc/xdg/openbox/. Here's an example of what's inside the menu.xml file.

<item label="Program_Name">
	<action name="Execute">
		<execute>
			Program_Command
		</execute>
	</action>
</item>

As you can see, the menus are neatly nested so they can be easily followed. Each entry has an opening tag and a closing tag, and each is clearly readable. rc.xml has a similar structure. For more information about how to hand-edit Openbox's XML files, read over the Openbox Web site.

ObMenu

If you're not keen on editing an XML file, there's ObMenu. This is a very small Python program that will allow you to modify your menu with a simple GUI, and save the results back into your menu.xml file. It's fast, easy and you don't have to worry about typos in your menu.xml file. Obmenu has been included in the repositories. To install open a terminal and type:

sudo aptitude install obmenu

The command "obmenu" runs the program.

Customizing

Openbox might just be a window manager, but there are plenty of opportunities to add some flair.

Obconf

Obconf is a handy program to customise Openbox. It allows for the selection of themes, some window behaviour, the number of desktops, and the dock. You can start Obconf with this command:

obconf

Note: Edgy (Ubuntu 6.10) users should be aware of a small discrepancy in Obconf that might prevent it from running. You can correct that with these commands ...

cd /usr/lib
sudo ln libobparser.so.0.4.0 libobparser.so.1
sudo ln libobrender.so.0.4.0 libobrender.so.1

Entering obconf in an X terminal window should now trigger the Obconf dialogue.

Themes

A variety of default themes are available in the repositories; you can install them via Synaptic, or through a terminal command:

sudo aptitude install openbox-themes

A number of third-party sites also offer themes as compressed packages. Download the one you like, then decompress it into the ~/.themes folder.

tar -xzvf compressed-theme-package-that-you-downloaded.tar.gz -C ~/.themes/

Don't forget the trailing slash. Now you can use Obconf to select your theme.

Modifying themes

The better part of a theme package is contained in a text file called themerc inside some nested folders in ~/.themes. If you want to fine-tune a theme (such as, make the letters bigger, or change the width of a window handle, or pick a different color), find the correct file in your ~/.themes folder and edit it as you like. When you save it, you can reselect the theme with Obconf, and your changes will take effect.

Wallpaper

feh

A number of programs can handle the responsibility of showing a background image; the most common is a funny little program called feh. feh is actually a lightweight image viewer with a number of options, but perhaps the most popular is the ability to draw a desktop background. Pick a wallpaper image and try this command in a terminal.

feh --bg-scale /path/to/your/background/image.jpg

Feh can handle other file types than just jpg. Once you've picked a wallpaper, feh stores the name in a file called .fehbg. That means you can tell it to restore the wallpaper on the next boot by checking to see what's inside that file. Add this line to your ~/.xinitrc file.

eval `cat $HOME/.fehbg` &
Nitrogen

If you perfer a graphical method for choosing between many background images, perhaps nitrogen is a good option. Nitrogen allows you to choose from many background images from a preset directory, you should add any wallpapers you wish to choose from to this directory. To use nitrogen, you should add

nitrogen /path/to/backgroundfiles/

to your menu.xml file (or alternatively add it to your menu using obmenu.) Next you must add

nitrogen --restore

to your ~/.config/openbox/autostart.sh (You can create this file if it does not exist) Now you can use your nitrogen entry in your menu to change your wallpaper and the changes will be restored on login.

Random wallpaper

One neat trick available with feh is a random wallpaper on each boot. Make a directory in your home folder called "wallpapers", then put a few background images in it. Then copy this text into a file called wallpaper.sh, and save it anywhere.

#!/bin/bash
WALLPAPERS="$HOME/path_to_your_wallpapers"
ALIST=( `ls -w1 $WALLPAPERS` )
RANGE=${#ALIST[*]}
SHOW=$(( $RANDOM % $RANGE ))

feh --bg-scale $WALLPAPERS/${ALIST[$SHOW]}

Next make the script executable.

chmod +x wallpaper.sh

Now add that program to your ~/.xinitrc file, like this.

./wallpaper.sh

When you log in, the script should be executed, and feh will pick a new wallpaper for your amusement.

Other options

feh isn't the only program that can handle drawing a background image. Here are some others.

  • xsetbg
  • imagemagick
  • nitrogen

Additionally, some file managers have the option of managing your wallpaper.

  • rox-filer
  • PCManFM
  • Nautilus, if started without the --no-desktop option, will draw over the background image

Desktop icons

iDesk

You can add customizable, clickable icons to your desktop with iDesk. iDesk is available in the Ubuntu repositories, and is installable from the command line with

sudo aptitude install idesk

Consult the iDesk wiki for instructions on how to configure and use iDesk. For icon sets, you may wish to search the repositories, or download them from third-party customization sites, such as Gnome-Look.org and similar locations.

Rox-Filer

Rox-filer is a file manager, but in addition to handling wallpaper, it also has a pinboard option, and can manage desktop icons. Install rox-filer with this command:

sudo aptitude install rox-filer

You can set up the pinboard through Rox's menus.

Taskbars and pagers

Some people prefer to use a taskbar or pager to keep track of running programs. Here's a list of applications you can add to your Openbox installation that will handle that task for you.

Taskbars

Pagers

System monitors

If you're looking for a way to display system information, try these nifty programs.

  • gkrellm, which has a number of floating or docked graphical meters and displays
  • adesklets, for similar graphical displays
  • conky, a highly configurable text and graphic output that draws directly to your desktop

If you're working on Openbox in conjunction with a Gnome installation, you might also look into gdesklets, which features some very polished monitors and meters for desktop display.

GTK themes

Program GUIs might look ugly if you're working on a pure Openbox system. Install gtk-theme-switch and the gtk2-engines package to give yourself a few more appealing options.

sudo aptitude install gtk-theme-switch gtk2-engines

Bring up the configuration menu with this command, from a terminal or the Openbox right-click menu.

switch2

Be sure to search the repositories for other engines that aren't included in the gtk2-engines package. You can also try installing a Gnome package that will manage some of the settings for you.

sudo aptitude install gnome-settings-daemon

If you prefere an XFCE look, try

sudo aptitude install xfce-mcs-manager

Either program will run, depending on what's installed, from openbox autostart.sh.

Automounting

To automount external volumes -- like CDs and USB drives -- you will need a volume manager. Here is the Gnome application that handles that:

sudo aptitude install gnome-volume-manager

Kubuntu and Xubuntu share the ivman application, which is installable with:

sudo aptitude install ivman

Screensaver

If you're building an Openbox desktop with Gnome already installed, you'll probably already have gnome-screensaver in place. Pure Openbox fans might want to install xscreensaver, which is more customizable and has a wider variety of screensavers involved. Without K/X/Ubuntu in place, installing xscreensaver needs a couple of extra commands:

sudo mkdir /usr/share/backgrounds
sudo aptitude install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra

The first command sets up a default directory that xscreensaver will look for when it runs. If you don't create that directory, you'll get a string of error messages the first time you set the preferences. The second command installs xscreensaver and its optional files. xscreensaver in Ubuntu is packaged with several screensaver options enabled, but not installed. As a result, you might see brief error messages when the daemon picks an enabled screensaver that it can't find. Adding those packages puts the missing screensavers in place, which is easier than disabling the absent ones. Now add this command to your ~/.xinitrc file, to start the xscreensaver daemon on boot.

xscreensaver --no-splash

You can access the xscreensaver preferences panel by running xscreensaver-demo from the Openbox menu or from a terminal window.

Run dialogue

Some people find it convenient to invoke a run dialogue program, which is usually triggered with ALT+F2. You'll need to change the keybinding in the rc.xml file in order to regain that function. If you are using XFCE components, changing rc.xml to point at xfrun4 might solve the problem. If not, consider installing the gmrun program.

sudo aptitude install gmrun

Change your rc.xml file to point to gmrun; you don't have to add it to your .xinitrc file, though.

Other window managers

To replace Metacity

As an alternative to Metacity, consider these window managers.

  • xfwm4: This is the default window manager for the XFCE4 desktop environment, and is a very comprehensive substitute. Instructions on replacing Metacity with XFCE4 are found here.
  • compiz: Compiz is a modern window manager that has many effects, such as animations, decoration opacity and provides its own composite manager.
  • E17: Enlightenment provides a full desktop environment, based around speed and attractiveness. This includes the window manager and a desktop shell.

Standalone

Here are some alternatives to Openbox for standalone window managers and desktop environments.

  • FVWM: FVWM is a traditional window manager with a long history in the Linux community. It is highly customizable, very flexible and has a very slim profile.
  • FVWM-Crystal: FVWM is set of configuration files that sits atop of FVWM, and is installable as a complete desktop environment with integrated audio controls, screensaver options and wallpaper control. It's also one of the prettiest options available to older hardware.
  • Fluxbox: Fluxbox is a window manager intended to be lightweight and fast, it is based on the Blackbox 0.61.1 code. If you find you enjoy working with Fluxbox, the Fluxbuntu project might be for you.
  • IceWM: IceWM is likewise a clean and svelte window manager, but keeps a "traditional" desktop look that some users prefer.
  • Blackbox: Blackbox served as the basis for Openbox, although Openbox has been completely rewritten in past years. Blackbox is still available, and still a popular option.
  • XFCE: XFCE serves as the underpinnings for Xubuntu, a fully supported Ubuntu variant complete with an office suite, networking interfaces, e-mail clients, and more. The project began as an option to run Ubuntu on older hardware, but has matured into a complete system on par with Kubuntu or Ubuntu. Visit their home page for more information about the project.

External links

Openbox

Openbox themes

A sample .xsession file

Other programs

Other sites of interest


-- I'm still of the mind that this page should be split out, with Openbox on Gnome taking the bulk of the previous material, and this staying closer to a "pure Openbox on Ubuntu" explanation. Edit: Scratch that. Openbox+Gnome material can shift to ReplaceMetacityWithOpenbox, and link to there from here. -- K.Mandla