The gtk3/python3 version of DockbarX is a lightweight taskbar / panel replacement for Linux which works as a stand-alone dock (called DockX), as a Xfce4 panel plugin, as a MATE panel applet or as a LXQt panel plugin. DockbarX is a fork of dockbar made by Aleksey Shaferov. DockbarX branch is developed by Matias Särs.
DockbarX is free software and is licensed under GPL3.
The main DockbarX PPA is not maintained for the moment. You can use Xu Zhen's unofficial DockbarX PPA instead. To add the PPA and install the application in Ubuntu (and derivatives), use the following commands:
sudo add-apt-repository ppa:xuzhen666/dockbarx
sudo apt update
sudo apt install dockbarx
If you want to use dockbarx as a panel plugin you also need these commands
sudo apt install xfce4-dockbarx-plugin # for Xfce4 panel
sudo apt install dockbarx-mate-panel-applet # for MATE panel
sudo apt install dockbarx-lxqt-plugin # for LXQt panel
To get more themes for DockbarX and DockX use this command
sudo apt install dockbarx-themes-extra
There is an AUR for DockbarX
https://aur.archlinux.org/packages/dockbarx/
And there is also one for xfce4-dockbarx-plugin
https://aur.archlinux.org/packages/xfce4-dockbarx-plugin/
- Following dependencies needs to be installed (many of them might be installed already on your system):
- gir1.2-gtk-3.0 (>= 3.22), gir1.2-glib-2.0 (>= 1.40), gir1.2-keybinder-3.0, gir1.2-pango-1.0, gir1.2-wnck-3.0, python3 (>= 3.5), python3-cairo (>= 1.11.0), python3-dbus, python3-gi, python3-gi-cairo, python3-pil, python3-xdg and python3-xlib.
- (Only for build) python3-pip, python3-polib, python3-setuptools
- (Optional) gir1.2-zeitgeist-2.0 and zeitgeist, to access latest and most used documents.
- (Optional) indicator-application or ayatana-indicator-application, to use the appindicator applet with DockX
- (Optional) python3-pyudev (>= 0.15), to use the battery status applet with DockX
- (Optional) python3-lxml, to use the settings migrating tool
- Extract dockbarx. Change directory to where you extracted dockbarx and run the following commands:
sudo pip install .
sudo glib-compile-schemas /usr/local/share/glib-2.0/schemas/
To run DockbarX as a stand alone dock use the command dockx.
The preference dialog is not yet usable with the gtk3 version. You have to change settings with the dconf-editor (DockbarX gsettings path is /org/dockbarx/dockbarx/ and /org/dockbarx/dockx/).
NOTE! To use previews with Compiz you need to activate KDE Compatibility in compiz settings manager and under KDE Compability check "Support Plasma Thumbnails". You can not use previews with other window manager than Compiz and Kwin.
DockbarX is a free and open source project I am developing in my free time. I will gladly accept any help I can get to improve DockbarX. Test out new code, report bugs to the issue tracker and make pull request with code you like to contribute.
##FAQ Q: Why do you want to make Linux into a Microsoft Windows 7 clone?
A: I don't. The goal of DockbarX isn't to be a clone of the Windows 7 task bar. Windows 7 task bar has a good principle, though. When it comes to your most used programs it's more productive to do all window handling - launching, selecting, closing, etc. from the same few pixels. If I need a Firefox window I move my mouse cursor to the same spot on the screen regardless of which Firefox window I want and or if I even have not opened a Firefox window yet. This behavior is good and it would be stupid not to implement it just because "Windows had it first". Don't reduce your productivity out of stubbornness. When it comes to looks it's up to you to choose a theme that looks like windows 7 or a theme that doesn't look that way.
Here are some historical references about docks:
http://en.wikipedia.org/wiki/Dock_(computing) http://en.wikipedia.org/wiki/Icon_bar
And another interesting link that has had quite a bit of infuence on my work with DockbarX: http://arstechnica.com/software/news/2009/01/dock-and-windows-7-taskbar.ars
Q: I want a button for every window instead of all windows of the same application grouped together under one button. When will DockbarX support that?
A: Never. That would demand quite a bit of restructuring of the code and I believe it's less productive to keep the windows ungrouped. You are welcome to change the code yourself if you don't like my decision, or try the applet Talika it might suit your needs better than DockbarX does.
Q: I added a new launcher for program X but when I click on the launcher a new groupbutton is made for the window instead of using the groupbutton of the launcher. What went wrong?
A: Dockbarx connects group buttons and windows by using the resource class name of the application. When a launcher is added dockbarx tries to guess the resource class name of that launcher. This works in most cases but not always. Apparently it didn't work for your program X. To fix this, right click on the launcher for program X and choose "Edit Resource name" and enter the correct resource name. If the program is already running you should be able to find it's resource class name in the drop-down list.
Q: There is no menu option to pin program X, but there is one for program Y and Z. Why? A: Dockbarx wasn't able to identify program X correctly then. You can "pin" the program by dragging it's icon from the gnome menu instead. Oh, and you will probably have to enter the resource name manually as well (see previous question).
Q: How do I get to preference dialog?
A: Right click the handle (the dots or lines to the left of dockbarx) to get a menu where you can choose the preference option. Sometimes though, you have to double right click the handle to get the menu. Don't ask me why - just do it. You can also find the preference dialog from gnome menu (in Accessories).
Q: None of DockbarX's compiz stuff like "compiz scale" work. Why?
A: Make sure you enable the GLib extension in Compiz settings manager and that the compiz plugin dockbarx uses is activated as well. (eg. for group button action "compiz scale" to work you need the scale plugin activated)
Q: Opacify doesn't work?
A: A common misunderstanding is that opacify should have something to do with transparency of dockbarx itself, it doesn't. Opacify is a way to find localize a window with dockbar. When opacify is on and you roll over a name in the window list with the mouse, all other windows will become transparent so that you easy can spot the window.
Q: How do I install a theme?
A: If you find a theme on the web that you like, copy the file (should be SOMETHING.tar.gz) to ~/.dockbarx/themes or /usr/share/dockbarx/themes. You change themes in the appearance tab of preference dialog. You might need to press the reload button before your newly installed theme shows up.
Q: How can I make an theme of my own?
A: Read Theming HOWTO. If you need help ask me (Matias Särs alias M7S) on gnome-look or at launchpad. I'm happy to help theme developers as much as I can.
Q: How can I backup and restore all preferences to move my settings to another linux setup?
A: Backup: dconf dump /org/dockbarx/ > dockbarx.xml
Restore: dconf load /org/dockbarx/ < dockbarx.xml
and don't forget to copy ~/.local/share/dockbarx/
Q: All the preferences were lost after upgrading to 1.0, how to get them back?
A: Dump the preferences from GConf database gconftool --dump /apps/dockbarx > dockbarx.xml, run the migrating tool dbx_migrate_settings dockbarx.xml, and move the application folder from ~/.dockbarx to ~/.local/share/dockbarx