Free exporting 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.

Sub::Exporter is a sophisticated exporter for custom-built routines.

SYNOPSIS

Sub::Exporter must be used in two places. First, in an exporting module:

# in the exporting module:
package Text::Tweaker;
use Sub::Exporter -setup => {
exports => [
qw(squish titlecase) # always works the same way
reformat => &build_reformatter, # generator to build exported function
trim => &build_trimmer,
indent => &build_indenter,
],
collectors => [ defaults ],
};

Then, in an importing module:

# in the importing module:
use Text::Tweaker
squish,
indent => { margin => 5 },
reformat => { width => 79, justify => full, -as => prettify_text },
defaults => { eol => CRLF };

With this setup, the importing module ends up with three routines: squish, indent, and prettify_text. The latter two have been built to the specifications of the importer -- they are not just copies of the code in the exporting package.

UMMF::Export::Java is a code generator for JavaTemplate.

SYNOPSIS

use UMMF::Export::Java;

my $exporter = UMMF::Export::Java->new(output => *STDOUT);
my $exporter->export_Model($model);

This package allow UML models to be represented as Java code.

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.

iTunes Export provides useful features that are not included in the iTunes application. iTunes Export project is open source and freely available for use.

iTunes Export currently provides the ability to export iTunes Playlists to the standard .m3u file format. Unfortunately, this feature is not included in the iTunes application and is extremely useful for users who wish to use iTunes with other applications or devices.

iTunes Export provides a simple command line application that can be used to generate playlists, a Graphical UI that provides a wizard interface to exporting playlists, or a DLL that can be used by other developers to add the ability to read iTunes Music Library XML files to other applications.

iTunes Export is written using C# on the .NET runtime. It should work on all versions of Windows that support .NET. The iTunesExport command line application also works on Linux using Mono 0.29 or later.

JDBCImporter provides a consistent mechanism for importing data from a file to a database, exporting data from a database to a file, and generating data.
JDBCImporter API can run from the command line using an XML config file or from inside an Ant build script. It works with CSV, fixed data, and XML files and supports numbers, strings, and date/times as database column types.
Custom classes can be used to parse different file formats, format column values into different file formats, translate column values before importing or after exporting, or allocate or release JDBC connections.
Installation:
Below are the installation steps for installing JDBC Importer:
unzip the jdbcimporter.zip file
add jdbcimporter.jar and commons-logging.jar to the CLASSPATH.
For example: set CLASSPATH=%CLASSPATH%;INSTALL_DIRlibjdbcimporter.jar;INSTALL_DIRlibcommons-logging.jar
JDBC Importer
Basic Usage:
> java [options] net.sourceforge.jdbcimporter.Importer [plugin file]
where :
config file : the import config file
plugin file : the (optional) property file that describes the plugins available during the import
options : two system properties may be set (both are optional)
jdbcimporter.engine = The import engine to use
jdbcimporter.failonerror = Flag indicating that the import should end if an error occurrs
Enhancements:
- This release fixes a bug with CSV delimiter parser.

IMS Transport provides a Plone product that supports importing and exporting of IMS packages.
The IMS Transport Tool allows Plone users to upload content in the form of an IMS package.
Although preliminary support is included for popular proprietary learning management system packages, support for extending this product to handle the import or export of any IMS package is also included.
Works with:
- Plone 2.5.1
- Plone 2.5
This is the first major release of this product.

Lyrics Manager is an amaroK script that manages the song lyrcis.
Main features:
- Edit lyrics with your favorite editor
- Export lyrics to file
- Import lyrics from file
You can setup your editor (for editing) and directory with texts (for import and export) via script configuration. Script will take care of html break tags while importing and exporting lyrics text, so you can edit and store plain text with correct rendering it in amaroK.