![]() Adesklets will remember the position of the desklet, so it will start in that location next time it is run. You can move them by right clicking on them and selecting Move, then left clicking when you are happy with the placement. To remove desklets which you have registered, but which have been deleted, you can "clean up" the configuration file with:ĭesklets will usually appear in the top left corner of the screen. To kill running desklets (which are registered) you can use: You can register many desklets which will all be run when you run adesklets, and it is a good idea to put that command in the session startup (in GNOME this is System->Preferences->Sessions and go on the Startup Programs tab and add it). Once the desklet has been registered it will be started when you run the adesklets command. This is usually done by running the desklet script, but instead of choosing test you should choose register. When you are happy with a desklet running in test mode you can tell adesklets to run it for you by registering it. If there is no config.txt or similar file (if there is a README then check in there for what the configuration file is called) then try running the desklet in test mode then killing it (ctrl-C) to see if the file has been created. ('gtk-gnutella.png', 'Gnutella', 'gtk-gnutella')],Īfter changing the configuration you can restart the desklet in test mode to try it out. ('inkscape.png', 'Inkscape', 'inkscape'), ('evolution.png', 'EMail', 'evolution -component=mail'), ('home.png', 'Files', 'nautilus /home/chris/Files'), 'Terminal', 'gnome-terminal -working-directory /home/chris'), The layout is the same as the original and you can see how easy it is to tweak the settings (this desklet looks for icons in a folder called "icons" inside it's directory, and this is where I stored my icon images): ![]() For example, here is a configuration file I use for the "modubar" desklet, which is similar to MacOSX's dock (the thing across the bottom of the screen with the icons in it), but without the extensive comments at the top. Since every desklet is different it would be impossible to explain how to configure them all, but the text files are usually straightforward. The desklets are controlled with text files, usually called config.txt, which you can open with any text editor (don't open it if the desklet is running, since your changes may be overwritten). ![]() To kill a desklet in test mode press ctrl-C (this is the standard way of killing programs being run in a terminal) To begin with you should run the desklet in test mode, so you can see what it is like and whether you would want to have it on your desktop. There are two ways of running each desklet, either in "test" mode or "registering" it, you will be asked which action you want to perform when you run the desklet (press the corresponding key, then Enter). Since they are usually python scripts (usually ending in ".py") they can be run from a terminal in the extracted directory with "python filename.py" (where filename.py is the desklet script, usually named similar to the archive). There is a collection of desklets here.Īfter getting a desklet you should move it to a location where you would like it to live permanently (at least until you uninstall adesklets), then extract it by right clicking on the archive and choosing Extract Here.ĭesklets initially need to be run manually. Since adesklets seperates itself from the desklets themselves, you will need to find some desklets which you like. It is in the Universe repository, so all you need to do is install the adesklets package. Even by adding icons, many common tasks such as reading news, checking for new emails and monitoring the system's resources take a few clicks and key presses, the programs can take a while to start, etc.ĭesklets attempt to solve these problems by placing graphical mini-applications (commonly called "applets") onto the desktop, and these desklets can constantly give information from news feeds, system monitors, email accounts and more, and since they are constantly on (yet relatively unobtrusive) it is much quicker to access this information.Īdesklets takes the approach of providing a few pieces of information to it's desklets (like which X session is being used, what the root window is, etc.) then allowing each desklet to do what it wants.Īdesklets itself is easy to install. The desktop can be a very boring place, especially since Ubuntu likes to use few icons.
0 Comments
Leave a Reply. |