Free international components for unicode 3.6 software for linux

Simple components for Ada library is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
As a special exception, if other files instantiate generics from this unit, or you link this unit with other files to produce an executable, this unit does not by itself cause the resulting executable to be covered by the GNU General Public License.
This exception does not however invalidate any other reasons why the executable file might be covered by the GNU Public License.
Enhancements:
- Functions Is_In were added for doubly-linked webs and lists. GPS project files were added for GNAT users.

Application Standard Components Library (ASCL) comprises a set of reusable Ada packages. The focus is not on light-weight components but larger components such as a configuration manager and a CLI application environment which does all the argument parsing.

It also includes a build environment for Linux which can be updated and maintained independently of the actual source code. It supports the personal software process for Ada programming.

Midgard Components Framework (also called MidCOM) is an advanced component architecture which extends the Midgard Web content management framework. It provides mechanisms for building a Web site using components without much need for writing code to glue all this together.
The administration site gets built automatically by using those components. Goodies like a caching engine and subrequests make site building even easier.
Enhancements:
- Full multilingual content support, performance enhancements, and support for Midgard builds that have the legacy API disabled were added.

eZ components project is an enterprise-ready, general-purpose PHP platform.
As a collection of high-quality independent building blocks for PHP application development, eZ components will both speed up development and reduce risks.
An application can use one or more components easily, as they all adhere to the same naming conventions and follow the same structure.
All components are based on PHP 5.1, except for the ones that require the new Unicode support that will be available from PHP 6 on.
Main features:
- Designed for enterprise PHP application development
- Open source and licensed under the New BSD license
- Clear IP rights
- Thoroughly documented
- Developed, supported and maintained by eZ systems
As the developers of eZ publish, one of the largest enterprise PHP applications in the world, eZ systems has over several years been developing enterprise PHP applications.
During the development of eZ publish eZ systems has been writing all the needed general libraries itself instead of reusing existing libraries. Quite a few other PHP projects are also doing the same. There are several reasons for this, like lack of documentation, quality of code, lacking functionality, unclear IP rights or inconsistencies between the libraries. eZ systems has the experience and resources to make such a product as well as the need for it.
The eZ components are developed with interoperatibility and a clean design in mind, allowing its users more flexibility and freedom, while keeping a consistent and well documented API. It is thouroughly documented, New BSD licensed with clear IP rights and available free of charge.
eZ systems has a dedicated team of professional developers for developing, maintaining and supporting eZ components. This will ensure that eZ components will be an active project for the future, making them a safe choice for PHP application developers to rely on.
Enhancements:
- The Graph component renders statistical data into 2-D and 3-D charts and graphs like bar, pie, and line charts.
- The SignalSlot component implements a kind of Subject-Observer pattern for object-oriented application design.
- Designed after Qts Signals and Slots mechanism, it gives you a handy tool for inter- and intra-object communication.
- The Url component conveniently extracts data from URLs and similarly creates URLs.
- This mechanism is commonly used in controller parts of a Model-View-Controller (MVC) implementation.

POE::Component::IRC is a fully event-driven IRC client module.

SYNOPSIS

# A simple Rot13 encryption bot

use strict;
use warnings;
use POE qw(Component::IRC);

my $nickname = Flibble . $$;
my $ircname = Flibble the Sailor Bot;
my $ircserver = irc.blahblahblah.irc;
my $port = 6667;

my @channels = ( #Blah, #Foo, #Bar );

# We create a new PoCo-IRC object and component.
my $irc = POE::Component::IRC->spawn(
nick => $nickname,
server => $ircserver,
port => $port,
ircname => $ircname,
) or die "Oh noooo! $!";

POE::Session->create(
package_states => [
main => [ qw(_default _start irc_001 irc_public) ],
],
heap => { irc => $irc },
);

$poe_kernel->run();
exit 0;

sub _start {
my ($kernel,$heap) = @_[KERNEL,HEAP];

# We get the session ID of the component from the object
# and register and connect to the specified server.
my $irc_session = $heap->{irc}->session_id();
$kernel->post( $irc_session => register => all );
$kernel->post( $irc_session => connect => { } );
undef;
}

sub irc_001 {
my ($kernel,$sender) = @_[KERNEL,SENDER];

# Get the components object at any time by accessing the heap of
# the SENDER
my $poco_object = $sender->get_heap();
print "Connected to ", $poco_object->server_name(), "n";

# In any irc_* events SENDER will be the PoCo-IRC session
$kernel->post( $sender => join => $_ ) for @channels;
undef;
}

sub irc_public {
my ($kernel,$sender,$who,$where,$what) = @_[KERNEL,SENDER,ARG0,ARG1,ARG2];
my $nick = ( split /!/, $who )[0];
my $channel = $where->[0];

if ( my ($rot13) = $what =~ /^rot13 (.+)/ ) {
$rot13 =~ tr[a-zA-Z][n-za-mN-ZA-M];
$kernel->post( $sender => privmsg => $channel => "$nick: $rot13" );
}
undef;
}

# We registered for all events, this will produce some debug info.
sub _default {
my ($event, $args) = @_[ARG0 .. $#_];
my @output = ( "$event: " );

foreach my $arg ( @$args ) {
if ( ref($arg) eq ARRAY ) {
push( @output, "[" . join(" ,", @$arg ) . "]" );
} else {
push ( @output, "$arg" );
}
}
print STDOUT join , @output, "n";
return 0;
}

POE::Component::IRC is a POE component (whod have guessed?) which acts as an easily controllable IRC client for your other POE components and sessions. You create an IRC component and tell it what events your session cares about and where to connect to, and it sends back interesting IRC events when they happen. You make the client do things by sending it events. Thats all there is to it. Cool, no?

[Note that using this module requires some familiarity with the details of the IRC protocol. Id advise you to read up on the gory details of RFC 1459 before you get started. Keep the list of server numeric codes handy while you program. Needless to say, youll also need a good working knowledge of POE, or this document will be of very little use to you.]
The POE::Component::IRC distribution has a docs/ folder with a collection of salient documentation including the pertinent RFCs.

POE::Component::IRC consists of a POE::Session that manages the IRC connection and dispatches irc_ prefixed events to interested sessions and an object that can be used to access additional information using methods.

Sessions register their interest in receiving irc_ events by sending register to the component. One would usually do this in your _start handler. Your session will continue to receive events until you unregister. The component will continue to stay around until you tell it not to with shutdown.

The SYNOPSIS demonstrates a fairly basic bot.

POE::Component::Player::Musicus is a POE wrapper for the musicus audio player.

SYNOPSIS

use POE qw(Component::Player::Musicus);

$musicus = POE::Component::Player::Musicus->new();
$musicus->play("test.mp3");

POE::Kernel->run();

This POE component is used to manipulate the musicus player from within a POE application