klik://usage

Usage

Q: Where does klik store the newly installed applications? A: All applications are stored on your desktop. In the file system, this is the directory $HOME/Desktop.

Q: Why does it put all downloaded .cmgs onto the Desktop? A: This is to make it more easy and more obvious to users where the new klik application ended up.

Q: Can I move the .cmg files away from my Desktop? A: Yes. The .cmg files will run from any place in your local file system.

Q: What do I need to do to install and run an application via klik? A: Just klik on a "klik://appname"-type of link.

Q: Is there a commandline client for klik? A: Yes. You can run ".klik" from the command line too: try "$HOME/.klik klik://xvier" or simply "$HOME/.klik xvier".

Q: Can't you make the klik application more verbose? A: Yes we can. However, we want to make it as fast and as little confusing to "newbie" and "grandma" users too. It is an art to find the right balance, and maybe it will always be subject to objections by some groups of users, however we do it.

Q: Why does it download xvier again and again each time I click on klik://xvier ? A: This is by design. Just don't click the same klik:// link twice. To run a klik application already present on your system, there are other means.

Q: How can I run a klik application already present on my system? A: Just click (or double-click, depending on your settings) onto the .cmg file.

Q: Can i run the klik application from the command line too? A: Yes. Use "$HOME/.zAppRun /path/to/appname.cmg", or "$HOME/.zAppRun -x /path/to/appname.cmg" for a more verbose output.

Q: I see most klik applications are for GUIs. Are there non-GUI ones too? A: Yes. Try klik://scli for an example.

Q: What are the main use cases for klik? A: We see two main purposes for klik: First, use klik to add missing applications to Linux running from live CD systems. Second, use klik to quickly evaluate (or beta-test) new versions of a certain software without endangering your current system library setup.

Q: Do you advice to leave the "old-school" package management systems like RPM or APT behind, and replace it with klik? A: No, not at all! klik is not a replacement for your established package manager, but merely a good complement. Use klik to evaluate new software. Install it permanently, using your system's package manager once you are convinced of a new application or new version.

Q: Can I use klik to run applications permanently? A: Yes.

Q: Can I use klik to run applications from a USB stick? A: Yes.

Q: Can I use klik to run applications from a CD? A: Yes.

Q: Does klik work for GUI applications only? A: No. There are some commandline utilities that work with klik too.

Q: Are there some "rules of thumb" for the type of applications that work with klik best? A: All simple standalone GUI programs should work "out of the box".

Q: Can you tell which type of applications are not expected to work with klik? A: Complex applications with lots of dependencies are more difficult to get working via klik. Examples are integrated development environments (IDEs) (like KDevelop, eric3 or gambas2), applications requiring databases (like Kexi), programs which need another service running (like amarok, which needs a sound server), or servers which generally need root privileges to start or require access to a TCP/IP-UDP port below 1024 (CUPS, BIND, Samba, Apache,...).

Q: Is it possible to make the more complex applications work via klik? A: Yes, it is possible. However -- we just need time to figure it out. Your help is welcome, though.