Free power event software for linux

TigerEvents is a novel, Web-based event announcement system for promoting upcoming and ongoing events to large communities such as university campuses, companies, or the general public.
Enhancements:
- This release has several bugfixes and enhancements.
- New to this release is the exporting of several calendar formats, including iCal, hCal, and being able to import events into Google Calendar.

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.

KMail Power Tools is meant to be a suite of enhancements to KMail and may be other mail user agents.
It is currently composed of only one (perl) script that acts as a filter (take input from stdin, outputs the modified mail to stdout), adds dialog boxes to kmail, and allows the user to:
- remove all attachments from an email (no user interaction),
- remove selectively attachments, after asking the user,
detach (i.e. save then remove) any attachment to a directory chosen by the user,
- hence reducing the size of your mailbox, while allowing you to backup important attached files.
All these actions are logged within a sentence in the mail body (see below).
Note: removing and detaching is already supported by Thunderbird, but my favourite mailer program is KMail, then...
How it works
KMail allows the definition of filters (like any other email program), but you can define filters:
- which are launched manually,
- which can be programs reading your email on stdin and outputing the result on stdout (or "pipe through").
So I had the idea to use this in order to enhance KMail, and allow it to remove and detach attachments: kmailpt will read and interpret the email (thank you Perl MIME::Parser), then depending on the command line switches, popup a dialog box to ask the user for a directory where to save attachments, and ask him which attachment to remove/detach (thank you Kdialog!).
Also, the sentence "[Attachment removed by jice (26/02/2007 20:33:01): bill.zip]" will be added to the mail body. When you detach an email, it will add a similar sentence, and if the mail body is html, you will even get a link to the new location of the file: "[Attachment saved by jice (26/02/2007 20:36:17) to heavenly.gif]", on which you can even click in order to view the detached file. For text/plain messages, the sentence will be something like: "[Attachment saved by jice (26/02/2007 20:36:17) to file:///home/jice/Images/heavenly.gif]" (unfortunately, although kmail renders http:// or ftp:// urls as links, file:// are not (yet?) - I should enter a bug on bugs.kde.org for this...).
Should you want to know the currently available command line switches, here is the help:
Usage: kmailpt [options]
kmailpt takes an email on stdin, performs actions based
on this mail, then output an email on stdout.
Without any option, it will remove any file attached.
Options:
-d detach the attachments (save and remove)
-q ask which attachment to remove
-h prints this help

libevent library provides a mechanism to execute a callback function when a specific event occurs on a file descriptor or after a timeout has been reached.
It is meant to replace the asynchronous event loop found in event-driven network servers.
libevent is meant to replace the event loop found in event driven network servers. An application just needs to call event_dispatch() and then add or remove events dynamically without having to change the event loop.
Currently, libevent supports /dev/poll, kqueue(2), select(2), poll(2) and epoll(4). It also has experimental support for real-time signals. The internal event mechanism is completely independent of the exposed event API, and a simple update of libevent can provide new functionality without having to redesign the applications. As a result, Libevent allows for portable application development and provides the most scalable event notification mechanism available on an operating system.
More information about event notification mechanisms for network servers can be found on Dan Kegels "The C10K problem" web page. Another library that abstracts asynchronous event notification is liboop.
Enhancements:
- Bugs in libevents HTTP layer were fixed.

Data Architects, DBAs, Analysts and Designers rely on Data Modeling tools to facilitate and simplify their data Modeling efforts, while maximizing the use of their resources. The Power*Architect allows these busy highly technical resources to perform this most intricate part of their job in a fraction of the time.
Power*Architect project is an innovative Java-based data modeling tool geared specifically for Data Warehouse and Data Mart design. It allows the designer to open multiple concurrent source Database connections, create and explore profiles of the source data, drag and drop source schemas, tables and columns into the data modeling playpen, and forward engineer the resultant target database and its associated ETL template.
Main features:
- Access any JDBC or ODBC accessible source database
- Quickly create profiles of source data, including information about the size of the data in each column, maximum and minimum values, frequency distribution of values in a column, and more.
- Profile information is saved with the project, so profile data can still be used to aid off-site design sessions when it is not possible to access the source databases.
- Design the target database Data Model (Data Warehouse)
- Compare the database structure of any two databases highlighting the structural differences and generating the required DDL to synchronize
- Compare the Data Model data structures to an existing target database
- Save a snapshot of all source systems data structures in the project file, allowing data warehouse designers to evolve their target data model remotely
- Forward engineer to Oracle, SQL Server, DB2, and PostgreSQL and more.
- Forward engineer ETL Templates containing source-to-target data mappings
- Invoke ETL Engine to load initial set of data into the target database
- Enable easy centralized installation and updates to many end users (Supports Java WebStart technology).
- The Power*Architect can open multiple source databases concurrently, even if they are from competing database vendors. Another key feature of the Power*Architect, that sets it apart from other data modeling tools, is that it remembers the origin of each column, and is capable of automatically generating the source-to-target data mappings.
- Whether youre building or maintaining your Data Warehouse data model, the Power*Architect will provide you a complete view of all required database structures and will expedite every aspect of your data warehouse design.
- Design your Data Warehouse in a fraction of the time with the Power*Architect.
- We look forward to showing you how!
- The Power*Architect is available now for download! The product is available for free to individuals for personal use. Commercial licensing and support are available at competitive prices. Please call us at 1-866-SQL-POWR to purchase.
Enhancements:
- This release fixes a bug that caused corrupt project files to be saved.
- The handling of automatic cascading primary keys in multi-level identifying relationships now works better.
- The profile manager is now even more stable.
- It is now possible to add new database connection types from within the GUI.

XML::Essex::Event is a base event class, also used for unknown event types. Stringifies as $event->type . "()" to indicate an event that has no natural way to represented in XML, or for ones that havent been handled yet in Essex.

Methods

new

XML::Event->new( a => 1, b => 2 );
XML::Event->new( { a => 1, b => 2 } );

## in a subclass:
sub new {
my $self = shift->SUPER::new( @_ );
...
return $self;
}

A generic constructor.

If a single value is passed in, a reference to it is kept. This must be a HASH for all builtin objects.

If an even number of parameters is passed in, treats them as key => value pairs and creates a HASH around them.

isa

Accepts shorthand; if the objects class starts with "XML::Essex::Event::", the parameter is checked against the string after "XML::Essex::Event::". So a XML::Essex::Event::foo->isa( "foo" ) is true (assuming it really is true; in other words, assuming that its @ISA is set properly).

clone

my $clone = $e->clone;

Does a deep copy of an event. Any events that require a deep copy must overload this to provide it, the default action is to just copy the main HASH.

type

Strips all characters up to the "::" and returns the remainder, so, for the XML::Essex::start_document class, this returns "start_document".

This must return a valid SAX event name, it is used to figure out how to serialize most event objects.

This is overloaded in most classes for speed and to allow subclasses to tweak the behavior of a class and still be reported as the proper type.

generate_SAX

$e->generate_SAX( $handler );

Emits the SAX event(s) necessary to serialize this event object and send them to $handler. $handler will always be defined.

Uses the type method to figure out what to send. Some classes (notably XML::Essex::characters) overload this for various reasons.

Assumes scalar context (which should not cause problems).

App::Modular::Module::Events is a Perl module with event handling for App::Modular compatible applications.

SYNOPSIS
####################################################################
package App::Modular::Module::Me;

use base qw(App::Modular::Module);

sub depends { return Events; }

sub start_listen {
my $self = shift;

$self->{modularizer}->module(Events)->
register(Listener, TelephoneRings);
};

sub event_handler {
my $self = shift;
my $event = shift;
print Yeah! Somebody thought about me!
if ($event eq TelephoneRings);
};

####################################################################
package App::Modular::Module::You;

use base qw(App::Modular::Module);

sub depends { return Events; }

sub call_me {
$self->{modularizer}->module(Events)->
trigger(TelephoneRings);
};

####################################################################
package main;

use App::Modular;

my $modul = instance App::Modular;

$modul->module(Me)->start_listen();
$modul->module(You)->callme();

exit;

App::Modular aims to provide a framework which should it make very easy to programmes to create any kind of modular program.

This module provides basic event handling as a contribution to that toolkit. Modules may register themselves as listeners for events, if an event is triggered, all the modules are notified by calling $module-event_handler(event, @params) >.

The events are speciefied as simple strings.