Free uml 2.0 component diagram software for linux

SWT component for OpenSceneGraph is a SWT component that allows you to display an OpenSceneGraph.

SWT component for OpenSceneGraph is know as libosgswt. libosgswt is the initial component included inside the josgviewer set of libraries.

The OpenSceneGraph is an open source high peformance 3D graphics toolkit, used by application developers in fields such as visual simulation, games, virtual reality, scientific visualization and modelling. Written entirely in Standard C++ and OpenGL it runs on all Windows platforms, OSX, GNU/Linux, IRIX, Solaris and FreeBSD operating systems.

POE::Component::OSCAR is a POE component for the Net::OSCAR module.

SYNOPSIS

use POE qw(Component::OSCAR);

[ ... POE set up ... ]

sub _start { # start an OSCAR session $oscar = POE::Component::OSCAR->new();
# start an OSCAR session with automatic throttling of new connections
# to prevent being banned by the server
$oscar = POE::Component::OSCAR->new( throttle => 4 );

# set up the "im_in" callback to call your state, "im_in_state"
$oscar->set_callback( im_in => im_in_state);

# its good to detect errors if you dont want to get banned
$oscar->set_callback( error => error_state );
$oscar->set_callback( admin_error => admin_erro_stater );
$oscar->set_callback( rate_alert => rate_alert_state );

# sign on
$oscar->signon( screenname => $MY_SCREENNAME, password => $MY_PASSWORD );
}
sub im_in_state { my ($nothing, $args) = @_[ARG0..$#_]; my ($object, $who, $what, $away) = @$args;
print "Got $what from $whon";
}

POE::Component::Basement provides Class::Std and base POE component functionality.

SYNOPSIS

package POE::MyComponent;

# use as base
use base qw/ POE::Component::Basement /;

# where the initializations happen (see Class::Std)
sub BUILD { ... }

# see also Class::Std and Class::Data::Inheritable also
# for accessor creation etc.

# define states
sub state_one : State( :inline< _start > ) { ... }
sub state_two : State( :object< foo > ) { ... }
sub state_three : State( :package< bar > ) { ... }

# combined
sub state_multi : State( :inline< foobar > :package< snafoo > ) { ... }
...

# chained events
sub first : State( :object< foo > :chained< bar > ) { ... }
sub second : State( :object< bar > ) { ... }
...

# calling in a row
sub first : State( :object< foo > :next< bar > ) { ... }
sub second : State( :object< bar > ) { ... }
...

# usage
my $comp = POE::MyComponent->new ({

# single alias or array reference for multiple
aliases => [qw/ mycomp shub_niggurath /],

... # your specific init_args.
});

Provides Class::Std and base POE component functionality. This module is still kinda experimental.

POE::Component::Proxy::MSN is a POE Component that is an MSN Messenger proxy.

SYNOPSIS

use POE qw(Component::Proxy::MSN);

# spawn MSN session
POE::Component::Proxy::MSN->spawn(
alias => msnproxy, # Optional, default
ip => any, # Optional, ip to bind to or any (default)
port => 1863, # Optional, default
msn_server => 207.46.106.79, # Server to connect to, not optional
msn_port => 1863, # Just leave this at 1863, not optional
);

# register your session as MSN proxy observer in _start of a new session
POE::Session->create(
inline_states => {
_start => sub {
$_[KERNEL]->post(msnproxy => register);
}
msn_logged_in => sub {
my ($kernel, $cmd) = @_[KERNEL, ARG0];
# tell them they are on the proxy, this is called when they log in
if ($cmd->{data} =~ m/(S+@S+)/) {
$kernel->post(msnproxy => toast => {
text => "MSN Proxy Active",
site_url => http://teknikill.net/?MSNProxy,
action_url => /,
options_url => /,
# not speciying email will toast all users
email => $1, # email targets a specific user that is logged in
});
}
},
}
);

$poe_kernel->run;

POE::Component::Proxy::MSN is a POE component that proxys the MSN Messenger service and allows you to send your own notifications (toasts).

POE::Component::Client::Halo is an implementation of the Halo query protocol.

SYNOPSIS

use Data::Dumper; # for the sample below
use POE qw(Component::Client::Halo);

my $halo = new POE::Component::Client::Halo(
Alias => halo,
Timeout => 15,
Retry => 2,
);

$kernel->post(halo, info, 127.0.0.1, 2302, pbhandler, ident);

$kernel->post(halo, detail, 127.0.0.1, 2302, pbhandler, ident);

sub postback_handler {
my ($ip, $port, $command, $identifier, $response) = @_;
print "Halo query $command_executed on ";
print " at $ip:$port";
print " had a identifier of $identifier" if defined $identifier;
print " returned from the server with:";
print Dumper($response), "nn";
}

POE::Component::Client::Halo is an implementation of the Halo query protocol. It was reverse engineered with a sniffer and two cups of coffee. This is a preliminary release, based version 1.00.01.0580 of the dedicated server (the first public release). It is capable of handling multiple requests of different types in parallel.

POE::Component::Client::Ping is a non-blocking ICMP ping client.

SYNOPSIS

use POE qw(Component::Client::Ping);

POE::Component::Client::Ping->spawn(
Alias => "pingthing", # defaults to "pinger"
Timeout => 10, # defaults to 1 second
Retry => 3, # defaults to 1 attempt
OneReply => 1, # defaults to disabled
Parallelism => 20, # defaults to undef
BufferSize => 65536, # defaults to undef
AlwaysDecodeAddress => 1, # defaults to 0
);

sub some_event_handler {
$kernel->post(
"pingthing", # Post the request to the "pingthing" component.
"ping", # Ask it to "ping" an address.
"pong", # Have it post an answer as a "pong" event.
$address, # This is the address we want to ping.
$timeout, # Optional timeout. It overrides the default.
$retry, # Optional retries. It overrides the default.
);
}

# This is the sub which is called when the session receives a "pong"
# event. It handles responses from the Ping component.
sub got_pong {
my ($request, $response) = @_[ARG0, ARG1];

my ($req_address, $req_timeout, $req_time) = @$request;
my ($resp_address, $roundtrip_time, $resp_time, $resp_ttl) = @$response;

# The response address is defined if this is a response.
if (defined $resp_address) {
printf(
"ping to %-15.15s at %10d. pong from %-15.15s in %6.3f sn",
$req_address, $req_time,
$resp_address, $roundtrip_time,
);
return;
}

# Otherwise the timeout period has ended.
printf(
"ping to %-15.15s is done.n", $req_address,
);
}

or

use POE::Component::Client::Ping ":const";

# Post an array ref as the callback to get data back to you
$kernel->post("pinger", "ping", [ "pong", $user_data ]);

# use the REQ_USER_ARGS constant to get to your data
sub got_pong {
my ($request, $response) = @_[ARG0, ARG1];
my $user_data = $request->[REQ_USER_ARGS];
...;
}

POE::Component::DebugShell is a component to allow interactive peeking into a running POE application.

SYNOPSIS

use POE::Component::DebugShell;

POE::Component::DebugShell->spawn();

This component allows for interactive peeking into a running POE application.

spawn() creates a ReadLine enabled shell equipped with various debug commands. The following commands are available.

COMMANDS

show_sessions

debug> show_sessions
* 3 [ session 3 (POE::Component::DebugShell controller) ]
* 2 [ session 2 (PIE, PIE2) ]

Show a list of all sessions in the system. The output format is in the form of loggable session ids.

session_stats

debug> session_stats 2
Statistics for Session 2
Events coming from: 1
Events going to: 1

Display various statistics for a given session. Provide one session id as a parameter.

list_aliases

debug> list_aliases 2
Alias list for session 2
* PIE
* PIE2

List aliases for a given session id. Provide one session id as a parameter.

queue_dump

debug> queue_dump
Event Queue:
* ID: 738 - Index: 0
Priority: 1078459009.06715
Event: _sigchld_poll
* ID: 704 - Index: 1
Priority: 1078459012.42691
Event: ping

Dump the contents of the event queue. Add a -v parameter to get verbose output.

help

debug> help
The following commands are available:
...

Display help about available commands.

status

debug> status
This is POE::Component::DebugShell v1.14
running inside examples/foo.perl.
This console spawned at Thu Mar 4 22:51:51 2004.
There are 3 known sessions (including the kernel).

General shell status.

reload

debug> reload
Reloading...

Reload the shell

exit

debug> exit
Exiting...

Exit the shell