Free zooming user interface software for linux

RULI stands for Resolver User Layer Interface. Its a library built on top of an asynchronous DNS stub resolver. RULI provides an easy-to-use interface for querying DNS SRV resource records. The goal is to promote wide deployment of SRV-cognizant software. RULI aims to fully support SRV-related standards. There are bindings for PHP, Perl, Guile/Scheme, Java, and Lua. IPv6 is supported.

Now you can understand the benefits of SRV records and please see how RULI can help you.

SRV records are more complex than A records

Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you

The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic

Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.

RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech

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.

Amazon API Search is the beginnings of a perl script to search Amazon.

It interfaces with Amazons API interface and performs whatever search the user desires, it then parses the data returned and inserts it in to an MySQL table.

Currently the script only deals with basic returned data, and does not have a user interface. In future releases I hope to correct this.

The script is certainly worth a look for anyone interested in using Amazons API interface.

Quill is a visual Web interface designer based on QuiX, Porcupines integrated XML User interface Language.

It took us quite longer than we expected but here it is. Quill is a visual web interface designer based on QuiX, Porcupines integrated XML User-Interface Language. We believe this is a major leap for the web interface design process, as it has become almost identical to this of a common desktop application.

This is an alpha release and as such there are a lot of missing features, but generally you can get things done a lot faster and easier than before. This release supports almost every QuiX widget, giving you full control over it, exhibiting all of its editable properties.

User::grent is an interface to Perls built-in getgr*() functions.

SYNOPSIS

use User::grent;
$gr = getgrgid(0) or die "No group zero";
if ( $gr->name eq wheel && @{$gr->members} > 1 ) {
print "gid zero name wheel, with other members";
}

use User::grent qw(:FIELDS);
getgrgid(0) or die "No group zero";
if ( $gr_name eq wheel && @gr_members > 1 ) {
print "gid zero name wheel, with other members";
}

$gr = getgr($whoever);

This modules default exports override the core getgrent(), getgruid(), and getgrnam() functions, replacing them with versions that return "User::grent" objects. This object has methods that return the similarly named structure field name from the Cs passwd structure from grp.h; namely name, passwd, gid, and members (not mem). The first three return scalars, the last an array reference.

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 gr_. Thus, $group_obj->gid() corresponds to $gr_gid if you import the fields. Array references are available as regular array variables, so @{ $group_obj->members() } would be simply @gr_members.

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. On the other hand, the built-ins are still available via the CORE:: pseudo-package.

ippfp is an easy-to-use library which provides oo-methods for creating and rendering user interfaces in PHP independently from output format. It features HTML, GTK, PDF and ncurses.
You can create input masks such as forms for databases or other user interfaces. ippfp features abstraction, elements can be accessed like data structures, they have values and various attributes.
For me ippfp is a construction kit to build software quickly.
Another purpose could be the automatically generation by software.
You can select one of these packages to display:
- HTML
- PDF
- GTK
- ncurses
Available elements:
- button
- checkbox
- choice
- fopen (file open)
- grid
- image
- label (readonly text)
- link
- multiplechoice
- password
- radio
- text
- textarea
- table
The library puts the elements together in a frame. For HTML a HTML page will be created which contains the elements, GTK and ncurses have appropriate windows. The data of elements will be stored in session variables.
One does not need to care for details of formats like HTML-tags or GTK-classes. For navigating within a program the button element should be used. To arrange elements the elements "grid" or rather "table" are the right choices.
Elements are created with the "create"-functions which are members of the ippfp main instance and returns objects respective to the goal. To make them visible they will be grouped in a "view" which will be given to the ippfp main instance for processing.
This is a flexible way because an existing element can be used in several views. Thus, elements will be included by reference, not by copy. The advantages are: if an element is in a state, it is independent from the current view and related informations are available globally.
For example: create a text element:
$myText = $ippfp->createText("default", 20, "my_text");
...
echo $myText->getValue();
Your code should be organised into php functions. For example if a button is used, it calls the function given as attribute. It is expedient to integrate your views into this functions.
Enhancements:
- switched from html to xhtml, format identifier is XHTML
- a simple debug function added, for internal debugging, writes messages into a file (usefull for ncurses)
- pdf passes the "tabellentest", tables and grids can extend over a big number of pages, and can contain big text
- some bugfixes in xhtml and pdf

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