Free app software for linux

Mountapp is a dockapp for mounting and unmounting filesystems. Mount.app is especially useful for removable volumes like CD-ROMs, ZIP(tm) disks, and floppies.
One click to mount, unmount, eject. GUI configuration, automatically configures "user" and "owner" mounts from /etc/fstab.
Enhancements:
- The source has been moved from CVS to Mercurial.
- Some user-supplied patches have been applied.

wmsm.app is a WindowMaker System Monitor.
Main features:
- Processor load
- Memory load
- Swap load
- Disk I/O (read/write)
- Uptime
- Two different scale types
Installation:
cd wmsm
make
make install (root)
Enhancements:
- added -d < dev > option to select the device that should observe, e.g. hda or sda (thanks to Carles Garrigues and krakov)
- added small point befor IOR and IOW only if the change of IOR or IOW was to small to display with the scale. Result: .IOR or .IOW

App::faq is a Perl module witj App-Context Frequently Asked Questions.

The App-Context is like a software backplane for many services required by an enterprise application. Into that backplane plug the App-Context Services. There may be many implementations of each of the App-Context Services, making for an almost limitless array of possible combinations. (Hopefully, favorites will emerge.)

The Context is a Core Service, like Session and Config. (A Core Service is one that is not derived from App::Service but maintains the concept of "a pluggable implementation of an abstract service".) An examination of the App::Context documentation will show that there are many Contexts from which the implementer may choose to deploy the software, and the software could reasonably run on all of them. The fact that (the envisioned) App::Context::Modperl2 depends on 5.6.0 does not invalidate the fact that the App-Context depends only on 5.5.3. Implementers who choose to deploy with Services that have higher Perl version dependencies must of course satisfy those dependencies.

The important thing to realize is that there is some combination of implementations of Services which will run on 5.5.3. Thus, the implementer who is stuck with 5.5.3 on a platform does indeed have a set of possible combinations of Services which will work.

The dependency on Perl version is not the only issue like this. Some modules are dependent upon certain operating systems. It is acceptable for a Service implementation to use these OS-specific functions as long as there is some other Service implementation (perhaps lower performing) which meets the cross-platform requirement.

i.e. App::Context::Modperl2 may require 5.6.0, but App::Context::Modperl and App::Context::CGI will both run on 5.5.3.

Sometimes when we think about Enterprise Systems, we think about big budget projects with the latest new hardware. My experience with customers who are large enterprises is that they have an incredible mish-mash of systems and legacy environments. I envision that App-Context software could be installed on every platform they own (isnt Perl almost the most-ported language on the planet?). That is why I believe that App-Context must support 5.5.3 (or perhaps earlier, but I wont go there yet until I see a real need to and understand exactly what I would be giving up).

wmAppKill is a window maker dock app that lists all your running processes. You can kill any of them by double-clicking on their names.

You can specify wich process will be the oldest one of the list. The one by default is "wmaker". Type "wmAppKill -h" to get command line options.

Installation:

To install wmAppKill :

1. tar xvfz wmAppKill-x.x.tar.gz
2. make
3. make install (you must be root)

Volume.app is a small graphical software utility enabling quick and convenient control of a computers audio volume level. Volume.app is intended for use on Linux/Unix systems in conjunction with an X window manager that supports dockable applications ("dockapps") such as AfterStep, BlackBox, or Window Maker.

It is a refinement of an idea that first appeared in Timecops WMix: a user interface comprising a "knob" that can be interactively "turned" by clicking and dragging the mouse. I found this approach quite appealing, both from an aesthetic viewpoint, and (more importantly) from a user-interface perspective.

A handful of other dockapp volume control programs are out there, and I have tried many of them. An interface element present in most of these is some form of "slider" as the primary means of adjusting the volume. (A fictitious example may be seen at right). To my dismay, with this kind of interface, volume adjustments tended to be large and abrupt. Because the slider was so small, raising or lowering the volume "just a bit" required extremely careful control of the mouse-- a slip of the hand had the potential to spike the volume to full blast. (I have a set of Altec-Lansing ACS48 speakers which make this a rather unpleasant experience). This approach left much to be desired.

I longed for an alternative, and upon playing with WMix (pictured at left) I had found it. The knob was genius in that it provided a means of graphically adjusting the volume, as a slider would, without tying itself directly to the motion of the mouse. The basic mode of usage is identical: you click on the thing and drag the mouse up or down. However, with the knob, the range of motion need not be confined to the postage-stamp-sized area of the dockapp. The mouse travel needed to cover the entire range of volume settings can be made longer, on the order of the full height of the screen-- almost like a much larger, easier-to-use slider. No longer were precise movements needed to make volume adjustments!

Still, I found WMixs interface to be a bit busy (never was a fan of tiny little buttons) and the all-important knob was yet a rather small target to find with the mouse. So, I grabbed a copy of the WMix source code, and rebuilt it into a dockapp that had a much larger knob as its sole interface element. I dubbed it Volume.app, and have placed it here for the benefit of everyone.

ImgGeoRef.app is a program that allow georeferencing an image. Georeferencing an image is the act of adding some properties to the image in order to manipulate it later in a cartography enabled application.
Initially, ImgGeoRef.app is build around some FlightTrack sources.
Todo:
Preferences
- taille du reticule
- couleur selectionne / deselectionne
Panels
- info
- info GDAL
- loupe
Enhancements:
- Really stupid simple manipulations are currently allowed.

App::Options is Perl module to combine command line options, environment vars, and option file values (for program configuration).

SYNOPSIS

#!/usr/local/bin/perl

use App::Options; # reads option values into %App::options by default

# do something with the options (in %App::options)
use DBI;
$dsn = "dbi:mysql:database=$App::options{dbname}";
$dbh = DBI->connect($dsn, $App::options{dbuser}, $App::options{dbpass});
...

Get help from the command line (assuming program is named "prog") ...

prog -?

Option values may be provided on the command line, in environment variables, and option files. (i.e. $ENV{APP_DBNAME} would set the value of %App::options{dbname} by default.)

The "dbname" and other options could also be set in one of the following configuration files

$HOME/.app/prog.conf
$HOME/.app/app.conf
$PROGDIR/prog.conf
$PROGDIR/app.conf
$PREFIX/etc/app/prog.conf
$PREFIX/etc/app/app.conf
/etc/app/app.conf

with a file format like

[prog]
dbname = prod
dbuser = scott
dbpass = tiger

See below for a more detailed explanation of these and other advanced features.

App::Options combines command-line arguments, environment variables, option files, and program defaults to produce a hash of option values.

XScreenSaver dockapp that will lock (left-click) your XSession and upon right-click bring up the XScreenSaver prefs.