"in the AUR" is redundant with the new AUR template
← Older revision
Revision as of 04:23, 16 August 2015
Line 123:
Line 123:
* {{App|LXInput|LXDE keyboard and mouse configuration|http://lxde.org|{{Pkg|lxinput}}}}
* {{App|LXInput|LXDE keyboard and mouse configuration|http://lxde.org|{{Pkg|lxinput}}}}
* {{App|LXRandR|LXDE monitor configuration.|http://wiki.lxde.org/en/LXRandR|{{Pkg|lxrandr}}}}
* {{App|LXRandR|LXDE monitor configuration.|http://wiki.lxde.org/en/LXRandR|{{Pkg|lxrandr}}}}
−
−
From the [[AUR]]:
* {{App|obkey|Configure Openbox keyboard shortcuts|https://code.google.com/p/obkey/|{{AUR|obkey}}}}
* {{App|obkey|Configure Openbox keyboard shortcuts|https://code.google.com/p/obkey/|{{AUR|obkey}}}}
* {{App|ob-autostart|A simple autostart application for Openbox.|http://pastebin.com/012YgXTk|{{AUR|ob-autostart}}}}
* {{App|ob-autostart|A simple autostart application for Openbox.|http://pastebin.com/012YgXTk|{{AUR|ob-autostart}}}}
Line 146:
Line 144:
== Keybinds ==
== Keybinds ==
−
All keybinds must be added to the {{ic|~/.config/openbox/rc.xml}} file, and below the {{ic|<nowiki><!-- Keybindings for running aplications --></nowiki>}} heading. Although a brief overview has been provided here, a more in-depth explanation of keybindings can be found at [http://openbox.org/wiki/Help:Bindings openbox.org].
There
is a utility
'obkey' in AUR
for adjust key-binding. Before
use
obkey, you should use obconf to create {{ic|~/.config/openbox/rc.xml}}.
+
All keybinds must be added to the {{ic|~/.config/openbox/rc.xml}} file, and below the {{ic|<nowiki><!-- Keybindings for running aplications --></nowiki>}} heading. Although a brief overview has been provided here, a more in-depth explanation of keybindings can be found at [http://openbox.org/wiki/Help:Bindings openbox.org].
{{AUR|obkey}}
is a utility for adjust key-binding. Before
using
obkey, you should use obconf to create {{ic|~/.config/openbox/rc.xml}}.
=== Special keys ===
=== Special keys ===
Line 335:
Line 333:
</keybind>
</keybind>
−
This [http://ubuntuforums.org/showthread.php?t=1796793 Ubuntu forum thread] provides more information. Applications such as {{AUR|opensnap-git}} are also available
from the AUR
to automatically simulate window snapping behaviour without the use of keybinds.
+
This [http://ubuntuforums.org/showthread.php?t=1796793 Ubuntu forum thread] provides more information. Applications such as {{AUR|opensnap-git}} are also available to automatically simulate window snapping behaviour without the use of keybinds.
=== Desktop menu ===
=== Desktop menu ===
Line 448:
Line 446:
{{Tip|icons can still be disabled in {{AUR|obmenu-generator}}, even where enabled in {{ic|~/.config/openbox/rc.xml}}.}}
{{Tip|icons can still be disabled in {{AUR|obmenu-generator}}, even where enabled in {{ic|~/.config/openbox/rc.xml}}.}}
−
{{AUR|obmenu-generator}} is
currently only available from the [[AUR]], although it is still
highly recommended. With the ability to be used as a static or dynamic menu, it is highly configurable, powerful, and versatile. Menu categories and individual entries may also be easily hidden, customised, and/or added with ease. The [http://trizenx.blogspot.co.uk/2012/02/obmenu-generator.html official homepage] provides further information and screenshots.
+
{{AUR|obmenu-generator}} is highly recommended
despite being an unofficial package
. With the ability to be used as a static or dynamic menu, it is highly configurable, powerful, and versatile. Menu categories and individual entries may also be easily hidden, customised, and/or added with ease. The [http://trizenx.blogspot.co.uk/2012/02/obmenu-generator.html official homepage] provides further information and screenshots.
Below is an example of how obmenu-generator would be dynamically executed without icons in {{ic|~/.config/openbox/menu.xml}}:
Below is an example of how obmenu-generator would be dynamically executed without icons in {{ic|~/.config/openbox/menu.xml}}:
Line 470:
Line 468:
==== obmenugen ====
==== obmenugen ====
−
{{AUR|Obmenugen}}
is currently only available from the [[AUR]], and
can be used to a generate static or dynamic application menu based on {{ic|.desktop}} files. The [http://obmenugen.sourceforge.net/ official homepage] provides further information.
+
{{AUR|Obmenugen}} can be used to a generate static or dynamic application menu based on {{ic|.desktop}} files. The [http://obmenugen.sourceforge.net/ official homepage] provides further information.
=== Menu icons ===
=== Menu icons ===
Line 558:
Line 556:
{{Tip|Where deciding to modify an existing theme (e.g. the colour scheme), it would be best to work on a copy of it, rather than the original. This will retain the original should anything go wrong, and ensure that your changes are not over-written through an update.}}
{{Tip|Where deciding to modify an existing theme (e.g. the colour scheme), it would be best to work on a copy of it, rather than the original. This will retain the original should anything go wrong, and ensure that your changes are not over-written through an update.}}
−
The process of creating new or modifying existing themes is covered extensively at the official [http://openbox.org/wiki/Help:Themes openbox.org] website.
A user-friendly GUI to do so -
{{AUR|obtheme}} -
is also available from the [[AUR]]
.
+
The process of creating new or modifying existing themes is covered extensively at the official [http://openbox.org/wiki/Help:Themes openbox.org] website. {{AUR|obtheme}}
is a user
-
friendly GUI for doing so
.
== Compositing effects ==
== Compositing effects ==
Line 616:
Line 614:
== Openbox for multihead users ==
== Openbox for multihead users ==
−
While Openbox provides better than average multihead support on its own,
the
{{AUR|openbox-multihead-git}}
package from the [[AUR]]
provides a development branch called '''Openbox Multihead''' that gives multihead users per-monitor desktops. This model is not commonly found in floating window managers, but exists mainly in tiling window managers. It is explained well on the [http://xmonad.org/tour.html#workspace Xmonad web site]. Also, please see [https://github.com/BurntSushi/openbox-multihead/blob/multihead/README.MULTIHEAD README.MULTIHEAD] for a more comprehensive description of the new features and configuration options found in Openbox Multihead.
+
While Openbox provides better than average multihead support on its own, {{AUR|openbox-multihead-git}} provides a development branch called '''Openbox Multihead''' that gives multihead users per-monitor desktops. This model is not commonly found in floating window managers, but exists mainly in tiling window managers. It is explained well on the [http://xmonad.org/tour.html#workspace Xmonad web site]. Also, please see [https://github.com/BurntSushi/openbox-multihead/blob/multihead/README.MULTIHEAD README.MULTIHEAD] for a more comprehensive description of the new features and configuration options found in Openbox Multihead.
Openbox Multihead will function like normal Openbox when only a single head is available.
Openbox Multihead will function like normal Openbox when only a single head is available.
−
A downside to using Openbox Multihead is that it breaks the EWMH assumption that one and only one desktop is visible at any time. Thus, existing pagers will not work well with it. To remedy this, {{AUR|pager-multihead-git}}
can be found in the [[AUR]] and is compatible with
Openbox Multihead. [http://imgur.com/a/cnZeq#y04nk Screenshots].
+
A downside to using Openbox Multihead is that it breaks the EWMH assumption that one and only one desktop is visible at any time. Thus, existing pagers will not work well with it. To remedy this,
you can install
{{AUR|pager-multihead-git}}
alongside
Openbox Multihead. [http://imgur.com/a/cnZeq#y04nk Screenshots].
−
Finally, a new version of [[PyTyle]] that will work with Openbox Multihead
can also be found in the [[AUR]]: {{AUR|pytyle3-git}}
.
+
Finally,
{{AUR|pytyle3-git}} is
a new version of [[PyTyle]] that will work with Openbox Multihead.
Both ''pytyle3'' and ''pager-multihead-git'' will work without Openbox Multihead if only one monitor is active.
Both ''pytyle3'' and ''pager-multihead-git'' will work without Openbox Multihead if only one monitor is active.