Free american express software for linux

VBA Express is a frontend for the very popular game emulator VisualBoyAdvance.

Whats VBA Express? Its First, to configure VisualBoyAdvance (emulator)... EASILY! Graphics, sound, controls (keyboard and joystick), paths (to saves and captures)... You can configure all this without edit VisualBoyAdvance.cfg manually!

Open your Roms (games) with the frontend! You can run the roms with "Play!" button (without using the console command VisualBoyAdvance game.rom).

Class::Meta::Express is a Perl module for concise, expressive creation of Class::Meta classes.

Synopsis

package My::Contact;
use Class::Meta::Express;

class {
meta contact => ( default_type => string );
has name;
has contact => ( required => 1 );
}

This module provides an interface to concisely yet expressively create classes with Class::Meta. Although I am of course fond of Class::Meta, Ive never been overly thrilled with its interface for creating classes:

package My::Thingy;
use Class::Meta;

BEGIN {
# Create a Class::Meta object for this class.
my $cm = Class::Meta->new( key => thingy );

# Add a constructor.
$cm->add_constructor( name => new );

# Add a couple of attributes with generated accessors.
$cm->add_attribute(
name => id,
is => integer,
required => 1,
);

$cm->add_attribute(
name => name,
is => string,
required => 1,
);

$cm->add_attribute(
name => age,
is => integer,
);

# Add a custom method.
$cm->add_method(
name => chk_pass,
code => sub { return code },
);
$cm->build;
}

This example is relatively simple; it can get a lot more verbose. But even still, all of the method calls were annoying. I mean, whoever thought of using an object oriented interface for declaring a class? (Oh yeah: I did.) I wasnt alone in wanting a more declarative interface; Curtis Poe, with my blessing, created Class::Meta::Declare, which would use this syntax to create the same class:

package My::Thingy;
use Class::Meta::Declare :all;

Class::Meta::Declare->new(
# Create a Class::Meta object for this class.
meta => [
key => thingy,
],
# Add a constructor.
constructors => [
new => { }
],
# Add a couple of attributes with generated accessors.
attributes => [
id => {
type => $TYPE_INTEGER,
required => 1,
},
name => {
required => 1,
type => $TYPE_STRING,
},
age => { type => $TYPE_INTEGER, },
],
# Add a custom method.
methods => [
chk_pass => {
code => sub { return code },
}
]
);

This approach has the advantage of being a bit more concise, and it is declarative, but I find all of the indentation levels annoying; its hard for me to figure out where I am, especially if I have to define a lot of attributes. And finally, everything is a string with this syntax, except for those ugly read-only scalars such as $TYPE_INTEGER. So I cant easily tell where one attribute ends and the next one starts. Bleh.

This project is to produce drivers for the Logitech Quickam Express that will run popular linux software, such as video for linux.

This site hosts the Linux driver for the QuickCam Express and other QuickCam-related and QuickCam-compatible USB web cameras. The original work was done by Georg Acher and was known as qce-ga; Jean-Frederic Clere took that driver and created the first Video4Linux (V4L) driver, enabling popular V4L applications such as Xawtv to display pictures from the webcam. Since then, a group of developers around the world have evolved the driver into its current state, adding support for new cameras and chipsets as they have become available. In the process, the driver became known as qc-usb to reflect the fact that it supports a wide variety of USB-attached QuickCam cameras, not just the QuickCam Express.

The qc-usb driver supports the following webcams:

Dexxa Webcam
Labtec Webcam (old model)
LegoCam
Logitech QuickCam Express (old model)
Logitech QuickCam Notebook (some models)
Logitech QuickCam Web

Generally, any USB camera with a USB vendor ID of 0x46d and a USB product ID of 0x840, 0x850, or 0x870 (so, 0x46d:0x840, for example), should work. You can see the USB ID using operating system utilities such as lsusb in Linux.

American Political Science: Campaign Simulator project is a statistically based political campaign simulation game.
The Campaign Simulator is an attempt to statistically model and predict the outcome of an American presidential election.
Several users assume the roles of competitive candidates and inflict the repercussions of certain decisions on a GSS-based dataset.
The application is written in Java and supports all operating systems with a Java 1.5 VM.
Main features:
- Time is not the only limiting variable. In fact, time may not be the proper limit as most operations may be performed in tandem; an economic system that allows fund raising elements should be implemented.
- The current choices all utilize the same dataset algorithm to effect the populace in similar ways- this set of scripts should be broadened and deepened as they are too high level.
- The Python Architecture needs polishing- the internal IDE is not complete, and the ability to assign scripts to run at differing points in the lifetime of the application has yet to be created.
- The installer should place links on the desktops of Mac and Unix/Linux Systems.
- Some of the small features planned, such as a GUI for dialog creation, have been cut for the deadline and should be added.

Monitoring API project is a multi-user programming interface designed to simplify the development of network monitoring software and allows users to express their monitoring needs in a device-independent way.
The main abstraction provided by MAPI is the network flow. Although flows have been used before in network monitoring systems, MAPI gives flows a first-class status. Applications that uses MAPI can specify what flows or flow statistics they are interested in by applying functions to flows.
A MAPI function can be a BPF filter, string search, packet counter or more advanced like a NetFlow generator. These function will automatically run in hardware if there is support for it on the hardware being used.
MAPI currently supports the following hardware:
- Normal NICs through libpcap
- DAG cards without co-processor
- SCAMPI adapter
Enhancements:
- This release includes support for distributed monitoring, several new MAPI functions, demo applications, and a lot of bugfixes.

DateTime::TimeZone::SystemV is a Perl module with System V and POSIX timezone strings.

SYNOPSIS

use DateTime::TimeZone::SystemV;

$tz = DateTime::TimeZone::SystemV->new("EST5EDT");

if($tz->is_floating) { ...
if($tz->is_utc) { ...
if($tz->is_olson) { ...
$category = $tz->category;
$tz_string = $tz->name;

if($tz->has_dst_changes) { ...
if($tz->is_dst_for_datetime($dt)) { ...
$offset = $tz->offset_for_datetime($dt);
$abbrev = $tz->short_name_for_datetime($dt);
$offset = $tz->offset_for_local_datetime($dt);

An instance of this class represents a timezone that was specified by means of a System V timezone string or the POSIX extended form of the same syntax. These can express a plain offset from Universal Time, or a system of two offsets (standard and daylight saving time) switching on a yearly cycle according to certain types of rule.

This class implements the DateTime::TimeZone interface, so that its instances can be used with DateTime objects.