https://wiki.archlinux.org/api.php?action=feedcontributions&user=Formode&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:34:19ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:AUR_helpers/Graphical&diff=85602Talk:AUR helpers/Graphical2009-11-28T07:54:23Z<p>Formode: Created page with 'GTKpacman is last updated in Febuary 2008.'</p>
<hr />
<div>GTKpacman is last updated in Febuary 2008.</div>Formodehttps://wiki.archlinux.org/index.php?title=Openbox&diff=79720Openbox2009-10-21T01:48:20Z<p>Formode: </p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|OpenBox (Česky)}}<br />
{{i18n_entry|English|Openbox}}<br />
{{i18n_entry|Español|Openbox (Español)}}<br />
{{i18n_entry|Français|Openbox (Français)}}<br />
{{i18n_entry|Italiano|Openbox_(Italiano)}}<br />
{{i18n_entry|Nederlands|Openbox_(Nederlands)}}<br />
{{i18n_entry|Русский|Openbox (Русский)}}<br />
{{i18n_entry|简体中文|Openbox(简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
== Introduction ==<br />
Openbox is a lightweight and highly configurable window manager with extensive standards support. Its features are well-documented at the [http://icculus.org/openbox/ official website]. This article will pertain to running Openbox under Arch Linux.<br />
<br />
== Installation ==<br />
Openbox is available from the standard repositories:<br />
# pacman -S openbox<br />
<br />
Once installed, pacman will direct you to copy the default {{Filename|menu.xml}} and {{Filename|rc.xml}} configuration files to <tt>~/.config/openbox/</tt>, for example: <br />
<br />
{{Note | Do this as a regular user, not as root.}}<br />
<br />
$ mkdir -p ~/.config/openbox/<br />
$ cp /etc/xdg/openbox/rc.xml ~/.config/openbox/rc.xml<br />
$ cp /etc/xdg/openbox/menu.xml ~/.config/openbox/menu.xml<br />
<br />
{{Filename|rc.xml}} is the core configuration file for Openbox. It is used to manage keyboard shortcuts, themes, virtual desktops and other features.<br />
<br />
{{Filename|menu.xml}} controls the Openbox application menu that appears when you click on your desktop. The default items are pretty sparse, but it's very easy to modify the menu structure to suit your needs. See the menu section below for more details, or visit the [http://icculus.org/openbox/ Openbox website].<br />
<br />
== Getting Started ==<br />
<br />
=== Using Openbox ===<br />
To run Openbox on its own, simply add the following to the bottom of {{Filename|~/.xinitrc}}:<br />
exec openbox-session<br />
<br />
If you have used another window manager before, such as Xfce, and Openbox wont start after logging out of X, try moving the autostart folder:<br />
mv ~/.config/autostart ~/.config/autostart-bak<br />
<br />
=== Using Openbox with GNOME ===<br />
<br />
==== GNOME 2.26 ====<br />
<br />
'''''Follow the next guide for GNOME 2.24. If it fails try this:'''''<br />
<br />
If after installing openbox and trying to log into the 'Gnome/openbox' session but it always fails then you can do the following as one way to achieve running openbox as your window manager every time you log into the 'Gnome' session from your login manager (xdm, gdm, kdm, entrance, slim, etc.)<br />
<br />
#Log into your Gnome only session (which would still be using metacity as its window manager) if you aren't already.<br />
#Install openbox if you have not done so already<br />
#Explore your menus to ''System &rarr; Preferences &rarr; Startup Applications'' (possibly named 'Session' for older versions of Gnome)<br />
#Open Startup Application, select '+ Add' and enter the text as seen in the box below whilst omitting the text behind the #.<br />
#Now hit the 'Add' button for that data entry window and make sure the checkbox beside your new entry is selected.<br />
#Thus log out of your gnome session and log back in and you should be running openbox as your window manager.<br />
#Enjoy!<br />
<br />
Name: Openbox Windox Manager # Can be changed<br />
Command: openbox --replace # Text should not be removed from this line, but possibly added to it<br />
Comment: Replaces metacity with openbox # Can be changed<br />
<br />
This creates an entry in a startup list which is executed by gnome everytime that particular user's gnome-session is started.<br />
<br />
==== GNOME 2.24 ====<br />
First, create {{Filename|/usr/share/applications/openbox.desktop}} containing the following:<br />
[Desktop Entry]<br />
Type=Application<br />
Encoding=UTF-8<br />
Name=OpenBox<br />
Exec=openbox<br />
NoDisplay=true<br />
# name of loadable control center module<br />
X-GNOME-WMSettingsModule=openbox<br />
# name we put on the WM spec check window<br />
X-GNOME-WMName=OpenBox<br />
Then, in gconf, set '''/desktop/gnome/session/required_components/windowmanager''' to '''openbox''':<br />
$ gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager openbox<br />
Finally, choose the '''GNOME''' session in the GDM sessions menu.<br />
<br />
==== GNOME 2.22 and previous ====<br />
# If you use GDM, select the "GNOME/Openbox" login option<br />
# If you use startx, add {{Codeline|exec openbox-gnome-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-gnome-session<br />
<br />
=== Using Openbox with KDE ===<br />
# If you use KDM, select the "KDE/Openbox" login option<br />
# If you use startx, add {{Codeline|exec openbox-kde-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-kde-session<br />
<br />
=== Using Openbox with Xfce4 ===<br />
Log into a normal Xfce4 session. From your terminal of choice, do:<br />
$ killall xfwm4 ; openbox & exit<br />
<br />
This will kill xfwm4, run Openbox, and close the terminal. <br />
<br />
Log out, making sure to check the "Save session for future logins" checkbox. On next login, Xfce4 will use Openbox as its WM. To be able to exit the session using xfce4-session, open your file {{Filename|~/.config/openbox/menu.xml}} (if it isn't there, copy it from {{Filename|/etc/xdg/openbox/menu.xml}}). <br />
<br />
Look for the entry:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Exit"><br />
<prompt>yes</prompt><br />
</action><br />
</item><br />
<br />
and change it to:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Execute"><br />
<prompt>yes</prompt><br />
<command>xfce4-session-logout</command><br />
</action><br />
</item><br />
<br />
Otherwise, using the "Exit" entry of the root-menu will cause Openbox to terminate its execution, leaving you without a window manager.<br />
<br />
If you have an issue changing between virtual desktops with the mouse wheel skipping over virtual desktops, open your {{Filename|~/.config/openbox/rc.xml}} file and move the mouse binds with actions "DesktopPrevious" and "DesktopNext" from the context "Desktop" to the context "Root" (you may need to define the Root context).<br />
<br />
If you want to use the Openbox root-menu instead of Xfce's, you may terminate Xfdesktop by running the following command in a terminal:<br />
$ xfdesktop --quit<br />
<br />
However, Xfdesktop manages the wallpaper and desktop icons, requiring you to use other utilities, such as ROX, for these functions.<br />
<br />
(When terminating Xfdesktop, the above issue with the virtual desktops is no longer a problem.)<br />
<br />
== Configuration ==<br />
<br />
=== Preferences ===<br />
Currently, there are two options for configuring the core Openbox preferences; manually edit the {{Filename|rc.xml}}, or use the ObConf tool.<br />
<br />
==== Setting Preferences Manually ====<br />
<br />
To configure Openbox manually, simply edit {{Filename|~/.config/openbox/rc.xml}} with your favorite text editor. The config file provides plenty of comments throughout, and [http://icculus.org/openbox/index.php/Help:Contents full documentation] is available at the official website.<br />
<br />
==== Setting Preferences with ObConf ====<br />
<br />
[http://icculus.org/openbox/index.php/ObConf:About ObConf] is GUI-based Openbox configuration tool, which can be used to set most preferences including themes, virtual desktops, window properties and desktop margins.<br />
<br />
To install ObConf, run:<br />
# pacman -S obconf<br />
<br />
{{Note | ObConf cannot be used to configure keyboard shortcuts and some other advanced features. For these modifications, you must edit {{Filename|rc.xml}} manually (see above).}}<br />
<br />
=== Menu Management ===<br />
<br />
The default Openbox menu includes a variety of applications to get you started, but you'll probably want to customize this at some point. There are a number of ways to do so:<br />
<br />
==== Manually ====<br />
Similar to the {{Filename|rc.xml}} file, you can edit {{Filename|~/.config/openbox/menu.xml}} with your favourite text editor. Although many of the settings are self-explanatory, [http://icculus.org/openbox/index.php/Help:Menus full documentation] is available.<br />
<br />
==== MenuMaker ====<br />
[http://menumaker.sourceforge.net/ MenuMaker] is a powerful tool that creates XML-based menus for a variety of Window Managers, including Openbox. MenuMaker will search your computer for executable programs and create an XML menu based on the results. It can be configured to exclude Legacy X, GNOME, KDE, or Xfce applications if the user desires.<br />
<br />
MenuMaker is available in the community repository:<br />
# pacman -S menumaker<br />
<br />
Once installed, you can generate a complete menu by running:<br />
$ mmaker -v OpenBox3<br />
<br />
By default, MenuMaker will not overwrite an existing menu.xml. To do so, run it with the -f (force) argument:<br />
<br />
$ mmaker -vf OpenBox3<br />
<br />
To see a full list of options, run {{Codeline|mmaker --help}}.<br />
<br />
This will give you a pretty thorough menu. Now you can modify the menu.xml by hand, or simply regenerate the list whenever you install new software.<br />
<br />
==== Obmenu ====<br />
Obmenu is a GUI-based menu editor for Openbox. For those who don't enjoy editing XML source code, this is probably the best option for you.<br />
<br />
It is available in the community repository:<br />
# pacman -S obmenu<br />
<br />
Once installed, simply run {{Codeline|obmenu}} and add or remove the desired applications.<br />
<br />
===== obm-xdg =====<br />
<tt>obm-xdg</tt> is a command-line tool that comes with Obmenu. It can generate a categorized sub-menu of installed GTK/GNOME applications.<br />
<br />
To use obm-xdg, add the following line to {{Filename|~/.config/openbox/menu.xml}}:<br />
<menu execute="obm-xdg" id="xdg-menu" label="xdg"/><br />
<br />
Then run {{Codeline|openbox --reconfigure}} to refresh the Openbox menu. You should now see a sub-menu labeled '''xdg''' in your menu.<br />
<br />
{{Note | If you do not have GNOME installed, then you need to install '''gnome-menus''' package for obm-xdg to work.}}<br />
<br />
===== Pipe Menus =====<br />
Openbox (and other WMs like WindowMaker and PekWM) allow you to write scripts that dynamically build menus on the fly. Some examples are system monitors, media player controls, and weather forecasts. Many examples can be found on the openbox [http://icculus.org/openbox/index.php/Openbox:Pipemenus site].<br />
<br />
Xyne has also created a file browser and brisbin33 has one for scanning for / connecting to wireless hot spots (requires netcfg). The relevant forum posts for these utilities are [http://bbs.archlinux.org/viewtopic.php?id=77197&p=1 here] and [http://bbs.archlinux.org/viewtopic.php?id=78290 here]<br />
<br />
===== Python based xdg menu script =====<br />
This script can be found in Fedora's Openbox package. You will only have to put the script somewhere and add a menu entry.<br />
<br />
Here is my paste: http://pastebin.com/f2f827625<br />
And here is the head: http://cvs.fedoraproject.org/viewvc/devel/openbox/xdg-menu?view=markup<br />
<br />
Download the one you like (maybe you'll prefer the head version of course). You can put the file anywhere, I used ~/Documents/build/xdg-menu (just modify the menu entry later according to YOUR filename/path.)<br />
<br />
Then open your menu.xml with your favourite text editor and add the following entry where you want the new menu (of course, you can modify the label however you want):<br />
<menu id="apps-menu" label="xdgmenu" execute="python /home/shiki/Documents/build/xdg-menu"/><br />
<br />
Save the file, and run: {{Codeline|openbox --reconfigure}}.<br />
=== Startup Programs ===<br />
Openbox features support for running programs at startup. This is provided by the "openbox-session" command.<br />
<br />
There are two ways to enable autostart:<br />
# If you use startx/xinit to log into your X session, edit {{Filename|~/.xinitrc}} and change the line that executes ''openbox'' to execute '''openbox-session''' instead.<br />
# If you log in with GDM/KDM, then select the ''Openbox'' session and it will automatically use autostart.<br />
<br />
Startup programs are managed in {{Filename|~/.config/openbox/autostart.sh}}. Full instructions and best practices for how to do this are available at the [http://icculus.org/openbox/index.php/Help:Autostart Openbox website].<br />
<br />
=== Per-application settings ===<br />
Openbox features per-application settings, allowing you to define rules for your programs. For example, you can:<br />
* load your web browser on a certain desktop<br />
* load your terminal without a window border<br />
* load your torrent client at a certain position on your screen<br />
<br />
These are defined in {{Filename|~/.config/openbox/rc.xml}}. As you might expect, the instructions are well-documented within the file itself. Full details can also be found here: http://icculus.org/openbox/index.php/Help:Applications<br />
<br />
=== Theming and Appearance ===<br />
With the exception of the Openbox Themes topic, the following section is intended for users who have configured Openbox to run as a standalone desktop, without the assistance of GNOME, KDE or Xfce.<br />
<br />
==== Openbox Themes ====<br />
Openbox themes control the appearance of window borders, including the titlebar and titlebar buttons. They also determine the appearance of the application menu and on-screen display (OSD). <br />
<br />
Additional themes are available from the standard repositories:<br />
<br />
# pacman -S openbox-themes<br />
<br />
This package is by no means definitive. You can download more themes at websites such as:<br />
*[http://www.box-look.org/index.php?xcontentmode=7402 box-look.org]<br />
*[http://customize.org/browse/tags/openbox customize.org]<br />
*http://www.minuslab.net/themes/<br />
*http://celo.wordpress.com/themes/<br />
*http://vault.openmonkey.com/pages/openbox<br />
*http://hewphoria.com/?p=submission&type=theme&cat=7<br />
<br />
Downloaded themes should be extracted to <tt>~/.themes</tt> and can be installed or selected with the [[Openbox#Preferences|ObConf]] tool.<br />
<br />
Creating new themes is fairly easy and again [http://icculus.org/openbox/index.php/Help:Themes well-documented].<br />
<br />
For a GUI theme editor, take a look at [http://xyne.archlinux.ca/info/obtheme ObTheme].<br />
<br />
==== Desktop Wallpaper ====<br />
<br />
Openbox itself does not include a way to change the wallpaper. This can be done easily with programs like [[Feh]] or [[Nitrogen]]. Other options include ImageMagick, hsetroot and xsetbg.<br />
<br />
==== GTK Themes ====<br />
====== GTK2/GTK+ ======<br />
GTK+ themes can be managed easily with the '''[[LXDE | lxappearance]]''', '''gtk-chtheme''', or '''switch2''' utilities. To install, run:<br />
# pacman -S lxappearance<br />
and/or<br />
# pacman -S gtk-chtheme<br />
and/or<br />
# pacman -S gtk-theme-switch2<br />
<br />
Now you can simply run {{Codeline|lxappearance}}, {{Codeline|gtk-chtheme}} or {{Codeline|switch2}} to set the desired theme.<br />
<br />
====== GTK1 ======<br />
For legacy GTK1 themes, install the '''gtk-theme-switch''' package:<br />
# pacman -S gtk-theme-switch<br />
Then run {{Codeline|switch}} to select a desired theme.<br />
<br />
==== GTK Fonts ====<br />
===== Manually edit the config file =====<br />
If you want to change the type and size of your fonts, add the following to {{Filename|~/.gtkrc.mine}}:<br />
style "user-font"<br />
{<br />
font_name = "[font-name] [size]"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "[font-name] [size]"<br />
<br />
where {{Codeline|[font-name] [size]}} is the desired font and point size. For example:<br />
style "user-font"<br />
{<br />
font_name = "DejaVu Sans 8"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "DejaVu Sans 8"<br />
<br />
Both {{Codeline|font_name}} and {{Codeline|gtk-font-name}} fields are required for backwards compatibility.<br />
===== Use GUI tools =====<br />
You can use '''gtk-chtheme''' or '''lxappearance''' to set GTK font settings. Please refer to the above section.<br />
<br />
==== GTK Icons ====<br />
First, extract the desired icon theme to <tt>/usr/share/icons</tt> (system-wide access) or <tt>~/.icons</tt> (local user access), then:<br />
===== Manually edit the config file =====<br />
Add the following to {{Filename|~/.gtkrc.mine}}: <br />
gtk-icon-theme-name = "[name-of-icon-theme]"<br />
<br />
where {{Codeline|[name-of-icon-theme]}} is the name of the icon theme directory. For example:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
Ensure {{Filename|~/.gtkrc-2.0}} is configured to parse {{Filename|~/.gtkrc.mine}}:<br />
<br />
# ~/.gtkrc-2.0<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
include "/usr/share/themes/Rezlooks-Gilouche/gtk-2.0/gtkrc"<br />
include "/home/username/.gtkrc.mine"<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
===== Use GUI tools =====<br />
You can use '''lxappearance''' to choose GTK icon themes. Please refer to the above section.<br />
<br />
==== Mouse cursor themes ====<br />
Extract the desired Xcursor theme to either <tt>/usr/share/icons</tt> (system-wide access) or <tt>~/.icons</tt> (local user access).<br />
<br />
Add this to {{Filename|~/.Xdefaults}}:<br />
Xcursor.theme: [name-of-cursor-theme]<br />
where {{Codeline|[name-of-cursor-theme]}} is the name of the cursor theme directory. For example:<br />
Xcursor.theme: Vanilla-DMZ-AA<br />
To change the size:<br />
Xcursor.size: [size]<br />
<br />
==== Desktop Icons ====<br />
Openbox does not provide a means to display icons on the desktop. PcmanFM, [http://rox.sourceforge.net ROX], [http://idesk.sourceforge.net iDesk], or even Nautilus (and the gnome-settings-daemon) can provide this function. <br />
<br />
ROX and PCmanFM have the additional advantage of being lightweight file managers.<br />
<br />
== Tips & Tricks ==<br />
=== Improve Fonts ===<br />
Improve the appearance of fonts for LCD monitors [http://wiki.archlinux.org/index.php/Fonts#Fonts_with_LCD_filter_enabled by following this guide.]<br />
<br />
Then, create {{Filename|~/.fonts.conf}} and add:<br />
<?xml version="1.0"?><br />
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"><br />
<fontconfig><br />
<match target="font" ><br />
<edit mode="assign" name="rgba" ><br />
<const>rgb</const><br />
</edit><br />
</match><br />
<match target="font" ><br />
<edit mode="assign" name="hinting"><br />
<bool>true</bool><br />
</edit><br />
</match><br />
<match target="font" ><br />
<edit mode="assign" name="hintstyle"><br />
<const>hintfull</const><br />
</edit><br />
</match> <br />
</fontconfig><br />
<br />
<br />
=== Recommended Programs ===<br />
<br />
There is list of [[Lightweight Software]] at Arch's wiki, most of them nicely fits with Openbox.<br />
<br />
==== Login Managers ====<br />
[http://slim.berlios.de/ SLiM] provides a lightweight and elegant graphical login solution for standalone Openbox configurations. Refer to Arch's [[SLiM]] wiki for detailed instructions.<br />
<br />
[http://qingy.sourceforge.net/ Qingy] is ultralight and very configurable graphical login. It support login to both console and X Windows sessions. It uses [http://www.directfb.org DirectFB], therefore it does not start X Windows unless you choose X Windows session. See article about [[Qingy]] at Arch's wiki.<br />
<br />
==== Composite Desktop ====<br />
[[Xcompmgr]] is a lightweight composite manager capable of rendering drop shadows, fading and simple window transparency within Openbox and other window managers.<br />
<br />
[http://aur.archlinux.org/packages.php?ID=30042 Cairo Comp Mgr] is an alternative.<br />
<br />
==== Transparency ====<br />
By using the program transset-df, it is virtually the same as [[transset]], (available by: pacman -S transset-df) you can enable transparancy of windows on the fly. For instance by editing the following in {{Filename|~/.config/openbox/rc.xml}} you can have your middle mouse scroll enable and disable transparency by scrolling down and up on the scroll button, respectively, while over the title bar (it is in the <mouse> section):<br />
<context name="Titlebar"><br />
<mousebind button="Left" action="Press"><br />
<action name="Focus"/><br />
<action name="Raise"/><br />
</mousebind><br />
<mousebind button="Left" action="Drag"><br />
<action name="Move"/><br />
</mousebind><br />
<mousebind button="Left" action="DoubleClick"><br />
<action name="ToggleMaximizeFull"/><br />
</mousebind><br />
<mousebind button="Middle" action="Press"><br />
<action name="Lower"/> <br />
<action name="FocusToBottom"/><br />
<action name="Unfocus"/><br />
</mousebind><br />
<mousebind button="Up" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --inc </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Down" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --dec </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Right" action="Press"><br />
<action name="Focus"/><br />
<action name="Raise"/><br />
<action name="ShowMenu"><br />
<menu>client-menu</menu><br />
</action><br />
</mousebind><br />
</context><br />
As of now, it only appears to work when no other actions are taken.<br />
<br />
==== Application Launchers ====<br />
===== dmenu =====<br />
Set-up dmenu as described in the [[dmenu]] wiki article. Then, add the following entry to the <keyboard> section {{Filename|~/.config/openbox/rc.xml}} to enable a shortcut to launch dmenu:<br />
<keybind key="W-space"><br />
<action name="Execute"><br />
<execute>dmenu_run</execute><br />
</action><br />
</keybind><br />
<br />
===== Gmrun =====<br />
[http://sourceforge.net/projects/gmrun gmrun] provides an excellent Run dialog box, similar to the Alt+F2 features found in Gnome and KDE:<br />
# pacman -S gmrun<br />
Add the following entry to the <keyboard> section {{Filename|~/.config/openbox/rc.xml}} to enable Alt+F2 functionality:<br />
<keybind key="A-F2"><br />
<action name="execute"><execute>gmrun</execute></action><br />
</keybind><br />
<br />
===== Bashrun =====<br />
[http://bashrun.sourceforge.net bashrun] provides a different, barebones approach to a run dialog, using a specialized bash session within a small xterm window. It is available in the community repository and can be launched through the Alt+F2 style approach mentioned previously. To make bashrun act more like a traditional run dialog, add the following entry to the <applications> section {{Filename|~/.config/openbox/rc.xml}}:<br />
<application name="bashrun"><br />
<desktop>all</desktop><br />
<decor>no</decor> # switch to yes if you prefer a bordered window<br />
<focus>yes</focus><br />
<skip_pager>yes</skip_pager><br />
<layer>above</layer><br />
</application><br />
<br />
===== Launchy =====<br />
[http://www.launchy.net/ Launchy] is a less minimalistic approach; it is skinnable and offers more functionality such as a calculator, checking the weather, etc. Originally for Windows, similar to Gnome Do.<br />
# pacman -S launchy<br />
It is launched by Ctrl+Space key combination.<br />
<br />
===== LXPanel =====<br />
[http://www.gnomefiles.org/app.php/LXPanel LXPanel] If LXPanel is used as a taskbar manager, the run utility from the LXPanel menu can be executed with {{Codeline|"lxpanelctl run"}}.<br />
<br />
===== gnome-panel =====<br />
The gnome-panel run dialog can be executed with <br />
gnome-panel-control --run-dialog<br />
<br />
==== File managers ====<br />
<br />
There are many possibilities, but the most popular lightweight file managers are:<br />
* [http://thunar.xfce.org Thunar]. Thunar supports auto-mount features and other plugins. <br />
# pacman -S thunar<br />
Thunar may be started in daemon mode for tighter desktop integration. For instance, inserting a USB pendrive will invoke a Thunar window to popup, with the drive contents listed in the window. <br />
<br />
To start Thunar in daemon mode, edit {{Filename|~/.config/openbox/autostart.sh}} and add:<br />
thunar --daemon &<br />
<br />
* [http://rox.sourceforge.net ROX] (ROX provides desktop icons)<br />
# pacman -S rox<br />
* [http://pcmanfm.sourceforge.net PCMan] (pcmanfm also provides desktop icons)<br />
# pacman -S pcmanfm<br />
For even lighter options, consider [http://www.obsession.se/gentoo/ Gentoo] or [http://emelfm.sourceforge.net/ emelFM], both of which use the familiar 'Midnight Commander' two pane layout (these two require Gtk 1.2.x).<br />
<br />
Of course, you can also use GNOME's Nautilus. Although slower than the above solutions, it has the additional advantage of VFS support (e.g. remote SSH, FTP and Samba connections).<br />
<br />
==== Clipboard Managers and copy/paste====<br />
You may wish to install a clipboard manager for feature rich copy/paste ability. '''xfce4-clipman-plugin, parcellite,''' or '''glipper-old''' may be installed via pacman. Add your choice to autostart.sh. From the terminal, Ctrl+Insert as copy and Shift+Insert as paste generally works as well. You may also copy from terminal with Ctrl+Shift+C, and paste with mouse middle click.<br />
==== Panels, Trays, and Pagers ====<br />
<br />
There are quite a lot of utilities available that provide a panel (taskbar), system tray, and pager to Openbox. The most common are:<br />
<br />
'''Panels'''<br />
* [http://wiki.archlinux.org/index.php/PyPanel PyPanel]<br />
* [http://nsf.110mb.com/bmpanel/ bmpanel]<br />
* [http://code.google.com/p/tint2/ Tint2]<br />
* [http://www.gnomefiles.org/app.php/LXPanel LXPanel]<br />
* [http://fbpanel.sourceforge.net fbpanel]<br />
* [http://perlpanel.org/ PerlPanel]<br />
* [http://www.chatjunkies.org/fspanel/ fspanel]<br />
* [http://www.xfce.org/projects/xfce4-panel/ xfce4-panel]<br />
* [http://developer.gnome.org/arch/gnome/corecomponents/panel/ gnome-panel]<br />
* [http://code.google.com/p/avant-window-navigator/ avant-window-navigator]<br />
* [http://developer.berlios.de/projects/cairo-dock/ cairo-dock]<br />
* [http://code.google.com/p/wbar/ wbar]<br />
<br />
'''Trays'''<br />
* [http://stalonetray.sourceforge.net/ Stalonetray]<br />
* [http://download.gna.org/fvwm-crystal/trayer/1.0/ Trayer]<br />
<br />
'''Pagers'''<br />
* [http://projects.l3ib.org/trac/visibility Visibility]<br />
* [http://bbtools.sourceforge.net/ bbpager]<br />
* [http://aur.archlinux.org/packages.php?ID=970 netwmpager]<br />
* [http://useperl.ru/ipager/index.en.html IPager]<br />
<br />
Make your choice and add it to your startup file.<br />
<br />
==== Pipe-menus ====<br />
<br />
Pipe-menus are small scripts that can return menu-items to create a dynamic feel of the Openbox menu.<br />
<br />
'''RSS-Reader'''<br />
* [http://primo-nordica.net/dezza/fasterfeeder.py FasterFeeder RSS Reader for Openbox]<br />
<br />
=== Get xprop values for per-app settings quickly ===<br />
If you use per-application settings frequently, you might find this bash alias handy:<br />
<br />
alias xp='xprop | grep "WM_WINDOW_ROLE\|WM_CLASS" && echo "WM_CLASS(STRING) = \"NAME\", \"CLASS\""'<br />
<br />
To use, run '''{{Codeline|xp}}''' and click on the running program that you'd like to define with per-app settings. The result will display only the info that Openbox requires, namely the WM_WINDOW_ROLE and WM_CLASS (name and class) values:<br />
<br />
[thayer@dublin:~] $ xp<br />
WM_WINDOW_ROLE(STRING) = "roster"<br />
WM_CLASS(STRING) = "gajim.py", "Gajim.py"<br />
WM_CLASS(STRING) = "NAME", "CLASS"<br />
<br />
=== Firefox/Gran Paradiso application rules === <br />
For whatever reason, Firefox and its open source equivalents will ignore application rules (e.g. <desktop>) unless {{Codeline|class&#61;"Firefox*"}} is used, regardless of what xprop reports as the actual WM_CLASS values.<br />
<br />
=== Linking the menu to a command ===<br />
Some people would want to link the Openbox main menu, or any other, to a command. This is useful for creating a menu button in a panel, for example. Although Openbox doesn't support this, a very simple script, xdotool, can simulate a keypress by running a command. Xdotool is [http://aur.archlinux.org/packages.php?do_Details=1&ID=14789&O=0&L=0&C=0&K=xdotool&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd available on AUR]. To use it, simply add the following code to the <keyboard> section of your {{Filename|rc.xml}}:<br />
<keybind key="A-C-q"><br />
<action name="ShowMenu"><br />
<menu>root-menu</menu><br />
</action><br />
</keybind><br />
Restart/reconfigure Openbox. You can now magically summon your menu at your cursor position by running the following command:<br />
# xdotool key ctrl+alt+q<br />
Of course, you can change the shortcut to your liking.<br />
<br />
=== Urxvt in the background === <br />
With Openbox, running a terminal as desktop background is easy. You won't need '''devilspie''' here.<br />
<br />
First you must enable transparency, open your {{Filename|.Xdefaults}} file (if it doesn't exist yet, create it in your home folder).<br />
URxvt*transparent:true<br />
URxvt*scrollBar:false<br />
URxvt*geometry:124x24 #I don't use the whole screen, if you want a full screen term don't bother with this and see below.<br />
URxvt*borderLess:true<br />
URxvt*foreground:Black #Font color. My wallpaper is White, you may wish to change this to White.<br />
<br />
Then edit your {{Filename|.config/openbox/rc.xml}} file:<br />
<application name="urxvt"><br />
<decor>no</decor><br />
<focus>yes</focus><br />
<position><br />
<x>center</x><br />
<y>20</y><br />
</position><br />
<layer>below</layer><br />
<desktop>all</desktop><br />
<maximized>true</maximized> #Only if you want a full size terminal.<br />
</application><br />
<br />
The ''magic'' comes from the {{Codeline|<layer>below</layer>}} line, which place the application under all others. Here Urxvt is displayed on all desktops, change it to your convenience.<br />
<br />
== Additional Resources ==<br />
* [http://icculus.org/openbox/ Openbox Website] &ndash; The official website<br />
* [http://planetob.openmonkey.com/ Planet Openbox] &ndash; Openbox news portal<br />
* [http://www.box-look.org/ Box-Look.org] &ndash; A good resource for themes and related artwork</div>Formodehttps://wiki.archlinux.org/index.php?title=E17&diff=79716E172009-10-20T21:47:52Z<p>Formode: </p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|E17}}<br />
{{i18n_entry|Русский|E17 (Русский)}}<br />
{{i18n_entry|Español|E17 (Español)}}<br />
{{i18n_entry|Italiano|E17 (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
E17 is the Development Release 17 (DR17) of the Enlightenment Desktop Environment.<br />
<br />
E17 is currently under heavy development, and is in the pre-alpha stages. Even though it is only young, E17 is still quite stable. Many people use it as a day-to-day Environment. <br />
<br />
New versions are available daily via SVN, but snapshots are also taken for easy installation. Below are instructions on how to install a SVN snapshot from the Arch community repositories.<br />
<br />
== Installing E17 from the community repository ==<br />
<br />
* First, edit your /etc/pacman.conf file and uncomment the community repositories by removing the hash at the start of that line; you should end up with something like the following:<br />
<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
* Next, sync, update, and upgrade using the new community repository:<br />
pacman -Syu<br />
* Install e17 group:<br />
pacman -S e17-svn<br />
* Install additional e17 modules and applications:<br />
pacman -S desktop-file-utils e17-extra-svn<br />
*Install additional fonts in order to avoid any trouble at the first start of e17<br />
pacman -S artwiz-fonts ttf-ms-fonts<br />
* If you need an e17 package which is not (yet) available in the [community] repo, see if it is available in the [http://aur.archlinux.org/ AUR].<br />
<br />
You are now ready. You can allow '''~/.xinitrc''' to start ''enlightenment'' for you:<br />
<br />
...<br />
# exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# ...or the Window Manager of your choice<br />
exec enlightenment_start<br />
<br />
If you want the ''entrance'' login manager (to replace [[KDM]]/[[GDM]]), you can either do this via:<br />
<br />
* '''/etc/rc.conf''' - You only get the login manager on startup; it will not be there if you CTRL+ALT+BACKSPACE<br />
<br />
...<br />
DAEMONS=(... entranced)<br />
...<br />
<br />
OR<br />
<br />
* '''/etc/inittab''' - The recommended way<br />
<br />
...<br />
## Only one of the following two lines can be uncommented!<br />
# Boot to console <br />
#id:3:initdefault: <br />
# Boot to X11 <br />
id:5:initdefault:<br />
<br />
...<br />
<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
#x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >& /dev/null<br />
#x:5:once:/bin/su johndoe -l -c "/bin/bash --login -c startx >/dev/null 2>&1"<br />
x:5:respawn:/usr/sbin/entranced --nodaemon >& /dev/null<br />
<br />
Enjoy!<br />
<br />
<br />
Note : e17 is still alpha software. At some point in the future things may not work as expected anymore. Although all packages are tested before added to the [community] repo, things may stop working for you. You are therefore encouraged to keep packages for the previous version on your computer, allowing you to downgrade if needed.<br />
<br />
If you find some unexpected behavior, there is a few things you can do. First try if the same behavior exists with the default theme. Second remove ~/.e (you may want to make a backup first). If you are sure you found a bug please report it directly upstream. If you are not sure if it is a bug in the software or in the package, report it on the [community] bug tracker.<br />
<br />
==== I want my e17 packages updated more often ====<br />
You can build your own Arch Linux e17 packages with a small python script called ArchE17. For more information and to download the latest version of the script, see [http://dev.archlinux.org/~ronald/e17.html http://dev.archlinux.org/~ronald/e17.html]<br />
<br />
== Installing E17 using easy_e17.sh ==<br />
'''This method is broken, the package no longer exists.'''<br />
<br />
The reason to use this method over the one mentioned before is mostly based on what you want to do, but I find it easier because the script (along with an extra tool) can give those who want more control over when E17 is updated than the aforementioned python script. It allows you to install components from E17's repository without having to go through and make a new PKGBUILD for it. With this script, when you uninstall this package, everything that was installed with the script is uninstalled. If you want to learn more about this script, see [http://ubuntuforums.org/showthread.php?t=916690 the thread for it on ubuntuforums.org].<br />
<br />
To install E17 using this script, add this repo to your /etc/pacman.conf:<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
Then, run:<br />
<br />
pacman -Sy easy-e17<br />
<br />
Alternatively, you can [http://aur.archlinux.org/packages.php?ID=22793 download the tarball from AUR], extract it to a new directory, and run makepkg. Then run as root pacman -U *.pkg.tar.gz.<br />
<br />
It will ask you a few questions and then install. You will need to put this in your .xinitrc in order to start E17:<br />
<br />
exec /opt/e17/bin/enlightenment_start<br />
<br />
It may be helpful to put /opt/e17/bin in your PATH, as then you won't have to add /opt/e17/bin in front of each program in order to run it. To do that, modify this line in /etc/profile:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin"<br />
<br />
So that it reads instead:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin:/opt/e17/bin"<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependancy problem. If it is, install the dependancy and continue installing e17 by running this command as root:<br />
<br />
easy_e17.sh -i<br />
<br />
To install one of the many applications from E17's svn repository, simply remove that program's name from /etc/easy_e17.conf, and then run this command as root (replacing name and name2 by the name of the program(s) you removed from easy_e17.conf):<br />
<br />
easy_e17.sh -i --only=''name'',''name2''<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
<br />
easy_e17.sh -u<br />
<br />
=== Update_e17.sh ===<br />
Another package, for OzOs's update_e17.sh script, is helpful when used in conjuntion with this script, as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. To install this, use either of the above meathods. The AUR page is located [http://aur.archlinux.org/packages.php?ID=23227 here].<br />
<br />
== Installing Themes ==<br />
More themes to customise the look of e17 are available from [http://exchange.enlightenment.org/ exchange.enlightenment.org].<br />
Make sure you also check out [http://www.e17-stuff.org e17-stuff.org].<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting /usr/bin/etk_prefs<br />
<br />
[http://aur.archlinux.org/packages.php?ID=7896 e17-themes] (aur package), can automate the download and install of lots of themes from exchange.enlightenment.org<br />
<br />
== Troubleshooting ==<br />
* If X complains about X cursors not being available, get the package 'libxcursor'.<br />
* If screenlock does not accept your password add the following to /etc/pam.d/enlightenment:<br />
auth required pam_unix_auth.so<br />
<br />
== External Links ==<br />
* [http://exchange.enlightenment.org/ Exchange.enlightenment.org, a new, integrated site that replaces the former get-e.org. get-e.org closed August, 2008.]<br />
* [http://e17-stuff.org/ e17-stuff.org, Themes, backgrounds, etc. are available here]</div>Formodehttps://wiki.archlinux.org/index.php?title=E17&diff=79695E172009-10-20T17:49:03Z<p>Formode: Package broken.</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|E17}}<br />
{{i18n_entry|Русский|E17 (Русский)}}<br />
{{i18n_entry|Español|E17 (Español)}}<br />
{{i18n_entry|Italiano|E17 (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
E17 is the Development Release 17 (DR17) of the Enlightenment Desktop Environment.<br />
<br />
E17 is currently under heavy development, and is in the pre-alpha stages. Even though it is only young, E17 is still quite stable. Many people use it as a day-to-day Environment. <br />
<br />
New versions are available daily via SVN, but snapshots are also taken for easy installation. Below are instructions on how to install a SVN snapshot from the Arch community repositories.<br />
<br />
== Installing E17 from the community repository ==<br />
<br />
* First, edit your /etc/pacman.conf file and uncomment the community repositories by removing the hash at the start of that line; you should end up with something like the following:<br />
<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
* Next, sync, update, and upgrade using the new community repository:<br />
pacman -Syu<br />
* Install e17 group:<br />
pacman -S e17-svn<br />
* Install additional e17 modules and applications:<br />
pacman -S desktop-file-utils e17-extra-svn<br />
*Install additional fonts in order to avoid any trouble at the first start of e17<br />
pacman -S artwiz-fonts ttf-ms-fonts<br />
* If you need an e17 package which is not (yet) available in the [community] repo, see if it is available in the [http://aur.archlinux.org/ AUR].<br />
<br />
You are now ready. You can allow '''~/.xinitrc''' to start ''enlightenment'' for you:<br />
<br />
...<br />
# exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# ...or the Window Manager of your choice<br />
exec enlightenment_start<br />
<br />
If you want the ''entrance'' login manager (to replace [[KDM]]/[[GDM]]), you can either do this via:<br />
<br />
* '''/etc/rc.conf''' - You only get the login manager on startup; it will not be there if you CTRL+ALT+BACKSPACE<br />
<br />
...<br />
DAEMONS=(... entranced)<br />
...<br />
<br />
OR<br />
<br />
* '''/etc/inittab''' - The recommended way<br />
<br />
...<br />
## Only one of the following two lines can be uncommented!<br />
# Boot to console <br />
#id:3:initdefault: <br />
# Boot to X11 <br />
id:5:initdefault:<br />
<br />
...<br />
<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
#x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >& /dev/null<br />
#x:5:once:/bin/su johndoe -l -c "/bin/bash --login -c startx >/dev/null 2>&1"<br />
x:5:respawn:/usr/sbin/entranced --nodaemon >& /dev/null<br />
<br />
Enjoy!<br />
<br />
<br />
Note : e17 is still alpha software. At some point in the future things may not work as expected anymore. Although all packages are tested before added to the [community] repo, things may stop working for you. You are therefore encouraged to keep packages for the previous version on your computer, allowing you to downgrade if needed.<br />
<br />
If you find some unexpected behavior, there is a few things you can do. First try if the same behavior exists with the default theme. Second remove ~/.e (you may want to make a backup first). If you are sure you found a bug please report it directly upstream. If you are not sure if it is a bug in the software or in the package, report it on the [community] bug tracker.<br />
<br />
==== I want my e17 packages updated more often ====<br />
You can build your own Arch Linux e17 packages with a small python script called ArchE17. For more information and to download the latest version of the script, see [http://dev.archlinux.org/~ronald/e17.html http://dev.archlinux.org/~ronald/e17.html]<br />
<br />
== Installing E17 using easy_e17.sh ==<br />
'''This method is broken, the package no longer exists.'''<br />
The reason to use this method over the one mentioned before is mostly based on what you want to do, but I find it easier because the script (along with an extra tool) can give those who want more control over when E17 is updated than the aforementioned python script. It allows you to install components from E17's repository without having to go through and make a new PKGBUILD for it. With this script, when you uninstall this package, everything that was installed with the script is uninstalled. If you want to learn more about this script, see [http://ubuntuforums.org/showthread.php?t=916690 the thread for it on ubuntuforums.org].<br />
<br />
To install E17 using this script, add this repo to your /etc/pacman.conf:<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
Then, run:<br />
<br />
pacman -Sy easy-e17<br />
<br />
Alternatively, you can [http://aur.archlinux.org/packages.php?ID=22793 download the tarball from AUR], extract it to a new directory, and run makepkg. Then run as root pacman -U *.pkg.tar.gz.<br />
<br />
It will ask you a few questions and then install. You will need to put this in your .xinitrc in order to start E17:<br />
<br />
exec /opt/e17/bin/enlightenment_start<br />
<br />
It may be helpful to put /opt/e17/bin in your PATH, as then you won't have to add /opt/e17/bin in front of each program in order to run it. To do that, modify this line in /etc/profile:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin"<br />
<br />
So that it reads instead:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin:/opt/e17/bin"<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependancy problem. If it is, install the dependancy and continue installing e17 by running this command as root:<br />
<br />
easy_e17.sh -i<br />
<br />
To install one of the many applications from E17's svn repository, simply remove that program's name from /etc/easy_e17.conf, and then run this command as root (replacing name and name2 by the name of the program(s) you removed from easy_e17.conf):<br />
<br />
easy_e17.sh -i --only=''name'',''name2''<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
<br />
easy_e17.sh -u<br />
<br />
=== Update_e17.sh ===<br />
Another package, for OzOs's update_e17.sh script, is helpful when used in conjuntion with this script, as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. To install this, use either of the above meathods. The AUR page is located [http://aur.archlinux.org/packages.php?ID=23227 here].<br />
<br />
== Installing Themes ==<br />
More themes to customise the look of e17 are available from [http://exchange.enlightenment.org/ exchange.enlightenment.org].<br />
Make sure you also check out [http://www.e17-stuff.org e17-stuff.org].<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting /usr/bin/etk_prefs<br />
<br />
[http://aur.archlinux.org/packages.php?ID=7896 e17-themes] (aur package), can automate the download and install of lots of themes from exchange.enlightenment.org<br />
<br />
== Troubleshooting ==<br />
* If X complains about X cursors not being available, get the package 'libxcursor'.<br />
* If screenlock does not accept your password add the following to /etc/pam.d/enlightenment:<br />
auth required pam_unix_auth.so<br />
<br />
== External Links ==<br />
* [http://exchange.enlightenment.org/ Exchange.enlightenment.org, a new, integrated site that replaces the former get-e.org. get-e.org closed August, 2008.]<br />
* [http://e17-stuff.org/ e17-stuff.org, Themes, backgrounds, etc. are available here]</div>Formode