Free types of user interfaces software for linux

General Graphics User Interface is an effort to produce a common graphical user interface for any command-line program.

It uses a wizard-like input front end to collect the information needed. It then calls the desired program automatically with all the necessary options.

The user is able to point&click on various options and select them in a convenient way. In order to create a new user-interface, a user doesnt need to know a programming language, since there is a graphical editor for new GGUI "scripts".

Squid Users Manager is a web-enabled and intuitive user interface written upon Ruby on Rails web development framework that manager Squid Proxy NCSA auth users across MD5 digest files.
The project is Open Source and distributed under the terms of the GPL licence.
Enhancements:
- Application Web 2.0 compliant
- New design with css and light layout.
- Ajax enabled app.
- More intuitive and elegant application.

qPyProfiler is a GUI (Graphical User Interface) to the Python profiler. It allow user to profile python application and browse profiling result in a convenient way. This projet starts on june 2007.

I started this project because I do not found any free software that do that for python profiling.

The project is a free software licenced under the GNU GPL V2.

Aegis project is a virus scanner for Linux, Unix and Windows with a simple and intuitive user interface.

Aegis supports scanning of subdirectories, hidden files and .zip and .tar archive files, and drag-and-drop of files from the Nautilus file browser, or your Gnome desktop. When a virus is detected you can choose to delete, quarantine or rename the file.

Console Jabber Client is a Jabber client with text-based user interface resembling those known from popular IRC clients.

CJC is a Jabber/XMPP client for text terminals. Console Jabber Client uses pyxmpp library for XMPP comunication and curses for screen output. It is not finished yet, but still quite usable. Its user interface is resembling those of popular IRC clients like irssi or BitchX.

User::pwent is a Perl interface getpw*() functions.

SYNOPSIS

use User::pwent;
$pw = getpwnam(daemon) || die "No daemon user";
if ( $pw->uid == 1 && $pw->dir =~ m#^/(bin|tmp)?z#s ) {
print "gid 1 on root dir";
}

$real_shell = $pw->shell || /bin/sh;

for (($fullname, $office, $workphone, $homephone) =
split /s*,s*/, $pw->gecos)
{
s/&/ucfirst(lc($pw->name))/ge;
}

use User::pwent qw(:FIELDS);
getpwnam(daemon) || die "No daemon user";
if ( $pw_uid == 1 && $pw_dir =~ m#^/(bin|tmp)?z#s ) {
print "gid 1 on root dir";
}

$pw = getpw($whoever);

use User::pwent qw/:DEFAULT pw_has/;
if (pw_has(qw[gecos expire quota])) { .... }
if (pw_has("name uid gid passwd")) { .... }
print "Your struct pwd has: ", scalar pw_has(), "n";

This modules default exports override the core getpwent(), getpwuid(), and getpwnam() functions, replacing them with versions that return User::pwent objects. This object has methods that return the similarly named structure field name from the Cs passwd structure from pwd.h, stripped of their leading "pw_" parts, namely name, passwd, uid, gid, change, age, quota, comment, class, gecos, dir, shell, and expire. The passwd, gecos, and shell fields are tainted when running in taint mode.

You may also import all the structure fields directly into your namespace as regular variables using the :FIELDS import tag. (Note that this still overrides your core functions.) Access these fields as variables named with a preceding pw_ in front their method names. Thus, $passwd_obj->shell corresponds to $pw_shell if you import the fields.

The getpw() function is a simple front-end that forwards a numeric argument to getpwuid() and the rest to getpwnam().

To access this functionality without the core overrides, pass the use an empty import list, and then access function functions with their full qualified names. The built-ins are always still available via the CORE:: pseudo-package.

OpenPFC project is a class library for implementing intelligent consumer electronics as quickly and efficiently as possible.
We address the proliferation of consumer electronics standards by providing common functionality while not restricting use to any single standard.
We also try to introduce special performance not traditionally found in consumer electronics.
PFC is mainly defined by the PFC core. This is a set of objects not specific to any single application.
With this in mind, PFC is not intended for writing desktop applications in a general purpose computing environment.
The runtime configuration of PFC is not intended to be reconfigured by users at the command line level.
User interfaces to PFC products are expected to be simple and media intensive.
Main features:
- Realtime multimedia
- Low memory
- Low CPU speed
- Devices with persistent storage
- Devices without persistent storage
- Advanced user interface rendering
- Fast user interface responsiveness
- 3D user interfaces