Free events software for linux

WWW::Facebook::API::REST::Client::Events is a Perl module with events for Client.

SYNOPSIS

use WWW::Facebook::API::REST::Client;

Methods for accessing events with WWW::Facebook::API::REST::Client

SUBROUTINES/METHODS

base

The WWW::Facebook::API::REST::Client::Base object to use to make calls to the REST server

get_in_window

The events.getInWindow method of the Facebook API

DIAGNOSTICS

This module is used by WWW::Facebook::API::REST::Client and right now does not have any unique error messages.

Event::Stats is a Perl module for event loop statistics. Instrument the Event module in order to gather statistics.

API

collect($yes)

Determines whether statistics are collected. Arithmetically adds $yes to the usage count. Stats are enabled while the usage count is positive.

$round_sec = round_seconds($sec)

Statistics are not collected in one second intervals. This function converts a *desired* time interval into an *available* time interval. Units are in seconds.

$elapse = total_time($sec)

Due to long-running callbacks, measurement intervals may take longer than expected. This function returns the actual clock-time for a given measurement interval.

($rans, $dies, $elapse) = idle_time($sec)

($runs, $dies, $elapse) = $watcher->stats($sec)

Return statistics for the last $sec seconds of operation. Three numbers are returned: the number of times the callback has been invoked, the number of uncaught exceptions and the number of seconds spent within the callback. Also see NetServer::ProcessTop.

enforce_max_callback_time($yes)

Useful for debugging. XXX

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.

XevdevServer is a program that uses the Linux evdev interface to capture events from specific mouse and keyboard devices.

It then translates these events and sends them to an X display using the XTEST extension. It can be helpful in a multi-seat X configuration.

Special keys

I dont know if this will work in the same way on other keyboard types, but on mine, the following special combinations work:

- Windows key + pause key: execute telinit 3. This may be useful if youre having some X-windows related problems.
- Windows key + keypad plus key: if multiple displays were specified to send events to, this selects the next display as the active one, allowing you to cycle through them.