Free events in software for linux

Event is an Event loop processing.

SYNOPSIS

use Event qw(loop unloop);

# initialize application
Event->flavor(attribute => value, ...);

my $ret = loop();

# and some callback will call
unloop(ok);

The Event module provide a central facility to watch for various types of events and invoke a callback when these events occur. The idea is to delay the handling of events so that they may be dispatched in priority order when it is safe for callbacks to execute.

Events (in the ordinary sense of the word) are detected by watchers, which reify them as events (in the special Event module sense). For clarity, the former type of events may be called "source events", and the latter "target events". Source events, such as signals arriving, happen whether or not they are being watched. If a source event occurs which a watcher is actively watching then the watcher generates a corresponding target event. Target events are only created by watchers. If several watchers are interested in the same source event then each will generate their own target event. Hence, any particular source event may result in zero, one, two, or any number of target events: the same as the number of watchers which were actively watching for it.

Target events are queued to be processed in priority order (priority being determined by the creating watcher) and in FIFO order among events of the same priority. Queued ("pending") events can, in some cases, be cancelled before being processed. A queued event is processed by being passed to the callback function (or method on a particular object or class) which was specified to the watcher.

A watcher, once created, operates autonomously without the Event user having to retain any reference to it. However, keeping a reference makes it possible to modify most of the watchers characteristics. A watcher can be switched between active and inactive states. When inactive, it does not generate target events.

Some types of source event are not reified as target events immediately. Signals received, for example, are counted initially. The counted signals are reified at certain execution points. Hence, signal events may be processed out of order, and if handled carelessly, on the wrong side of a state change in event handling. A useful way to view this is that occurrence of the source event is not actually the arrival of the signal but is triggered by the counting of the signal.
Reification can be forced when necessary. The schedule on which some other events are created is non-obvious. This is especially the case with watchers that watch for a condition rather than an event. In some cases, target events are generated on a schedule that depends on the operation of the event loop.

Event::RPC is a event based transparent Client/Server RPC framework.

SYNOPSIS

#-- Server Code
use Event::RPC::Server;
use My::TestModule;
my $server = Event::RPC::Server->new (
port => 5555,
classes => { "My::TestModule" => { ... } },
);
$server->start;

----------------------------------------------------------

#-- Client Code
use Event::RPC::Client;
my $client = Event::RPC::Client->new (
server => "localhost",
port => 5555,
);
$client->connect;

#-- Call methods of My::TestModule on the server
my $obj = My::TestModule->new ( foo => "bar" );
my $foo = $obj->get_foo;

ABSTRACT

Event::RPC supports you in developing Event based networking client/server applications with transparent object/method access from the client to the server. Network communication is optionally encrypted using IO::Socket::SSL. Several event loop managers are supported due to an extensible API. Currently Event and Glib are implemented.

Tk::event contains miscellaneous event facilities: define virtual events and generate events.

SYNOPSIS

$widget->eventAction(?arg, arg, ...?);

The eventAction methods provides several facilities for dealing with window system events, such as defining virtual events and synthesizing events. Virtual events are shared by all widgets of the same MainWindow. Different MainWindows can have different virtual event.

The following methods are currently supported:

$widget->eventAdd(, sequence ?,sequence, ...?)

Associates the virtual event virtual with the physical event sequence(s) given by the sequence arguments, so that the virtual event will trigger whenever any one of the sequences occurs. Virtual may be any string value and sequence may have any of the values allowed for the sequence argument to the bind method. If virtual is already defined, the new physical event sequences add to the existing sequences for the event.

$widget->eventDelete( ?,sequence, sequence, ...?)

Deletes each of the sequences from those associated with the virtual event given by virtual. Virtual may be any string value and sequence may have any of the values allowed for the sequence argument to the bind method. Any sequences not currently associated with virtual are ignored. If no sequence argument is provided, all physical event sequences are removed for virtual, so that the virtual event will not trigger anymore.

$widget->eventGenerate(event ?,option => value, option => value, ...?)

Generates a window event and arranges for it to be processed just as if it had come from the window system. $window is a reference to the window for which the event will be generated. Event provides a basic description of the event, such as < Shift-Button-2 > or >. If Window is empty the whole screen is meant, and coordinates are relative to the screen. Event may have any of the forms allowed for the sequence argument of the bind method except that it must consist of a single event pattern, not a sequence. Option-value pairs may be used to specify additional attributes of the event, such as the x and y mouse position; see "EVENT FIELDS" below. If the -when option is not specified, the event is processed immediately: all of the handlers for the event will complete before the eventGenerate method returns. If the -when option is specified then it determines when the event is processed.

$widget->eventInfo(?>?)

Returns information about virtual events. If the argument is omitted, the return value is a list of all the virtual events that are currently defined. If is specified then the return value is a list whose elements are the physical event sequences currently defined for the given virtual event; if the virtual event is not defined then undef is returned.

Event::ExecFlow is a high level API for event-based execution flow control.

ABSTRACT

Event::ExecFlow provides a ligh level API for defining complex flow controls with asynchronous execution of external programs.

SYNOPSIS

use Event::ExecFlow;

my $job = Event::ExecFlow::Job::Group->new (
jobs => [
Event::ExecFlow::Job::Command->new (
name => "transcode",
title => "Transcoding DVD title to OGG",
command => "transcode -i /dev/dvd ...",
fetch_output => 1,
progress_max => 4711, # number of frames
progress_parser => sub {
my ($job, $buffer) = @_;
$job->set_progress_cnt($1) if $buffer =~ /[d+-(d+)]/;
#-- or simply write this:
#-- progress_parser => qr/[d+-(d+)]/,
},
),
Event::ExecFlow::Job::Code->new (
name => "checks",
title => "Do some checks",
depends_on => [ "transcode" ],
code => sub {
my ($job) = @_;
my $transcode = $job->get_group->get_job_by_name("transcode");
if ( $transcode->get_output !~ /.../ ) {
$job->set_error_message("XY check failed");
}
#-- this could be done easier as a post_callback added to
#-- the "transcode" job above, but its nevertheless a good
#-- example for the Code job type and shows how jobs can
#-- interfere with each other.
},
),
Event::ExecFlow::Job::Command->new (
title => "Muxing OGG file",
depends_on => [ "checks" ],
command => "ogmmerge ...",
no_progress => 1,
),
],
);

#-- this inherits from Event::ExecFlow::Frontend
my $frontend = Video::DVDRip::GUI::ExecFlow->new(...);
$frontend->start_job($job);

Event::ExecFlow offers a high level API to declare jobs, which mainly execute external commands, parse their output to get progress or other status information, triggers actions when the command has been finished etc. Such jobs can be chained together in a recursive fashion to fulfill rather complex tasks which consist of many jobs.

Additionally it defines an extensible API for communication with the frontend application, which may be a written using Gtk2, Tk or Qt or is a simple text console program.

In case of Gtk2 a custom widget for displaying an Event::ExecFlow job plan, including progress updates, is shipped with the Gtk2::Ex::FormFactory package.

POE::Loop::Event is a bridge that supports Gtks event loop from POE.

SYNOPSIS

See POE::Loop.

This class is an implementation of the abstract POE::Loop interface. It follows POE::Loops public interface exactly. Therefore, please see POE::Loop for its documentation.

CTBClient is a mobile client for the CTB. The main objective of CTBClient is to allow registering expenses and other financial events in the road, and later uploading them to the mother system.
It puts in use a set of exciting technologies: Bluetooth, Python SQL DBI, serialization (marshaling) of objects, GTK+, Python for Series 60 Nokia cell phones (known as S60), perhaps PyObjc in future Mac OS X versions etc. CTBClient is also meant to be a guinea pig for portable Python development.
CTBClient is a project sponsored by INdT - Instituto Nokia de Tecnologia (Nokia Institute of Technology), where I work and have the environment and time to make such experiments.
Functional clients are:
- GTK+ Linux/local (no Bluetooth, for quick tests);
- GTK+ Linux Bluetooth
- Symbian/S60 cell phone
- GTK+/Hildon Linux (Maemo platform, like Nokia 770 tablets)
Functional servers:
- Linux/local (for testing)
- Linux/Bluetooth

Discrete Event Calculus Reasoner is an open source program for performing automated commonsense reasoning using the event calculus, a comprehensive and highly usable logic-based formalism.
Discrete Event Calculus Reasoner solves problems efficiently by converting them into satisfiability (SAT) problems.
Main features:
- Comes with 99 examples
- Comes with 12-page users manual
- Supports deduction/temporal projection, abduction/planning, postdiction, and model finding
- Allows default reasoning about action, change, space, and mental states
- Useful for intelligent user interfaces, business systems, natural language understanding, and computer vision
- Helps applications understand the world, make inferences, adapt to unexpected situations, and be more flexible
- Released under the Common Public License v1.0

EvRouter reads events from the Linux input layer, and acts on them according to a user-specified set of rules. Currently, EvRouter can map events to X11 key and button presses, XMMS commands, and it can also run shell commands.

EvRouter is intended to help legacy applications understand modern events such as mouse wheel movement and special keys on keyboards.

EvRouter also offers hotkey-like functions, and can help existing modern applications deal with events that, for one reason or another, X11 is unaware of (as long as they are accessible through a Linux event device).