Free to export software for linux

BBDB::Export is a Perl module to export data from The Insidious Big Brother Database.

SYNOPSIS

use BBDB::Export;

# export to LDIF
my $exporter = BBDB::Export::LDIF->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => "export.ldif",
dc => "dc=geekfarm, dc=org",
}
);
$exporter->export();

# sync with ldap via ldapadd and ldapdelete
my $exporter = BBDB::Export::LDAP->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => "/tmp/tempfile",
dc => "dc=geekfarm, dc=org",
ldappass => "supersecret",
}
);

$exporter->export();

# export to vcards
my $exporter = BBDB::Export::vCard->new(
{
bbdb_file => "/path/to/.bbdb",
output_dir => "/some/path/",
}
);

$exporter->export();

# create .mail_aliases
my $exporter = BBDB::Export::MailAliases->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => ".mail_aliases",
}
);

$exporter->export();

This module was designed to export to your bbdb data to a wide array of formats, and also to make it easy to write new modules to export to new formats. Current export options include building an LDIF, vCard, or .mail_aliases, and automatically updating an ldap server.
For a fully functional command line converter, see the bbdb-export script that comes with this module.

BBDB::Export should not be used directly. Use any of the available subclasses using the examples above. For more examples of using BBDB::Export, see the test cases.

Exporter::Easy is a Perl module that takes the drudgery out of Exporting symbols.

SYNOPSIS

In module YourModule.pm:
package YourModule;
use Exporter::Easy (
OK => [ $munge, frobnicate ] # symbols to export on request
);
In other files which wish to use YourModule:
use ModuleName qw(frobnicate); # import listed symbols
frobnicate ($left, $right) # calls YourModule::frobnicate

Exporter::Easy makes using Exporter easy. In its simplest case it allows you to drop the boilerplate code that comes with using Exporter, so

require Exporter;
use base qw( Exporter );
use vars qw( @EXPORT );
@EXPORT = ( init );
becomes
use Exporter::Easy ( EXPORT => [ init ] );
and more complicated situations where you use tags to build lists and more tags become easy, like this
use Exporter::Easy (
EXPORT => [qw( init :base )],
TAGS => [
base => [qw( open close )],
read => [qw( read sysread readline )],
write => [qw( print write writeline )],
misc => [qw( select flush )],
all => [qw( :base :read :write :misc)],
no_misc => [qw( :all !:misc )],
],
OK => [qw( some other stuff )],
);

This will set @EXPORT, @EXPORT_OK, @EXPORT_FAIL and %EXPORT_TAGS in the current package, add Exporter to that packages @ISA and do a use vars on all the variables mentioned. The rest is handled as normal by Exporter.

GENE Graph Export Engine is an advanced XML exporter.
GENE Graph Export Engine is a complex convertor/framework for multi-namespace XML transforming and exporting.
It is able to convert various XML types including SVG, DocBook, MathML, XSL-FO, and their combinations into a wide area of output formats: PDF, PNG, SVG, PS, MIF, RTF, and XHTML.
Custom XSLT scripts can be registered easily and are used automatically. It requires Sun JRE 5.0.
Enhancements:
- GENE Core bugfixes. FOP plugin bugfixes.
- Gene Runner I18N support has been added. l12n in Slovak.
- Configuration ability has been added.
- New command line switches have been added.
- Preliminary buggy CML (Chemical Markup Language) and XHTML->DocBook exporters have been added.

Tagore project is a personal desktop wiki for GNOME.

Tagore lets you take notes using the textile syntax and display them with the embeded browser. You can add tags to your notes for easy organizing them and you can later export them to html.

Sub::Exporter::Tutorial is a friendly guide to exporting with Sub::Exporter.

Whats an Exporter?

When you use a module, first it is required, then its import method is called. The Perl documentation tells us that the following two lines are equivalent:

use Module LIST;

BEGIN { require Module; Module->import(LIST); }

The import method is the modules exporter.

The Basics of Sub::Exporter

Sub::Exporter builds a custom exporter which can then be installed into your module. It builds this method based on configuration passed to its setup_exporter method.

A very basic use case might look like this:

package Addition;
use Sub::Exporter;
Sub::Exporter::setup_exporter({ exports => [ qw(plus) ]});

sub plus { my ($x, $y) = @_; return $x + $y; }

This would mean that when someone used your Addition module, they could have its plus routine imported into their package:

use Addition qw(plus);

my $z = plus(2, 2); # this works, because now plus is in the main package

That syntax to set up the exporter, above, is a little verbose, so for the simple case of just naming some exports, you can write this:

use Sub::Exporter -setup => { exports => [ qw(plus) ] };
...which is the same as the original example -- except that now the exporter is built and installed at compile time. Well, that and you typed less.

Using Export Groups

You can specify whole groups of things that should be exportable together. These are called groups. Exporter calls these tags. To specify groups, you just pass a groups key in your exporter configuration:

package Food;
use Sub::Exporter -setup => {
exports => [ qw(apple banana beef fluff lox rabbit) ],
groups => {
fauna => [ qw(beef lox rabbit) ],
flora => [ qw(apple banana) ],
}
};

Now, to import all that delicious foreign meat, your consumer needs only to write:

use Food qw(:fauna);
use Food qw(-fauna);

Either one of the above is acceptable. A colon is more traditional, but barewords with a leading colon cant be enquoted by a fat arrow. Well see why that matters later on.

Groups can contain other groups. If you include a group name (with the leading dash or colon) in a group definition, it will be expanded recursively when the exporter is called. The exporter will not recurse into the same group twice while expanding groups.

There are two special groups: all and default. The all group is defined by default, and contains all exportable subs. You can redefine it, if you want to export only a subset when all exports are requested. The default group is the set of routines to export when nothing specific is requested. By default, there is no default group.

Tail server allows you to export the output of a "tail -f" command of a log file to a TCP port, allowing it to be viewed remotely with telnet. Tail Server provides a regular expression filter to include or exclude output view.
In several circumstances the need to access on remote time-varying log file leads to write some simple scripts.
These files generated by applications like syslog, http, news, etc. are often located on different machines.
System Administrator usually logon on remote system then type:
# tail -f filename
Tail Server offers the possibliy to map on Tcp/Ip port the output of "# tail -f filename" without (each time) logging on remote systems.
Also offers output regular expressions filter in order to include or exclude strings.
Enhancements:
- Server Log File has been implemented.

Audio Daemon is a perl module to daemonize various players and support a single UDP interace for different players. Currently you can set up a server for MPG123, Xmms and an icecast stream (using libshout).

Audio::Daemon is made of two parts, the client and server.

The Client (Audio::Daemon::Client) remains the same across the board no matter what server you are communicating with, with a few exceptions noted in the pods.

The Server currently can be configured to be MPG123, Xmms or an Icecast (libshout) stream. Neither the Client nor the Servers need to be run as root and I strongly advise against it.

Audio::Daemon::MPG132:
Requires Audio::Play::MPG123 an optionally Audio::Mixer for volume control. It automatically spawns mpg123 in the background so there is no need to prestart it.

Audio::Daemon::Xmms:
Requires the Xmms and MP3::Info perl module and xmms installed. Id suggest getting the latest version of the Xmms perl module. It uses the volume and random feature built into xmms and if it doesnt find an xmms running it will try to spawn its own copy. Bear in mind that
xmms MUST HAVE an X display to export to, and that xmms must be running as the same user Audio::Daemon::Xmms is.

Audio::Daemon::Shout:
This wasnt easy to do. It requires MP3::Info and libshout to be installed (http://developer.icecast.org/libshout/) as well as a functioning icecast server. The timing here is pretty critical so I recomend being careful not to be polling the server too much. Be sure to read the icecast docs as Im still confused on how I got this part to work.

F-Spot project is an application designed to provide personal photo management to the GNOME desktop.
Main features:
- import
- export
- printing
- advanced sorting of digital images.