Free archivers scrapbook store software for linux

Really Simple CalDAV Store project is a server implementation of the CalDAV protocol for storing calendaring resources (iCalendar format) on a remote shared server.
An increasing number of calendar clients support the maintenance of shared remote calendars through CalDAV including Mozilla Calendar (Sunbird/Lightning), Evolution, Mulberry, and soon Apples iCal.
The Really Simple CalDAV Store supports basic delegation of read/write access among calendar users and multiple users or clients reading and writing the same calendar entries over time.
Enhancements:
- Lots of improvements were made to CalDAV specification compliance, especially around privacy of tasks and events.
- Two new translations of the administration interface were added (Polish and Hungarian).
- Support for authentication against an LDAP backend was added along with a number of performance, security, and bugfixes.

wallpaperChooser is a small application for managing your wallpapers. It has the ability to store wallpapers, preview them, and set them on the desktop.
This is a small application made with Python and PyGTK to admin your wallpapers. It has the ability to store wallpapers, preview them and set them in the desktop.
Installation:
To install this application just run as root:
#make install
In order to uninstall it (as root too):
#make uninstall
Enhancements:
- Added to the code the ability to check if the needed directories and files exist and in case they dont, create them.

Email::Store is a framework for database-backed email storage.

SYNOPSIS

use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once

Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );

...

Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.

Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.

User::Identity::Archive is a base class for archiving user information.

INHERITANCE

User::Identity::Archive
is a User::Identity::Item

User::Identity::Archive is extended by
User::Identity::Archive::Plain

SYNOPSIS

use User::Identity::Archive::Plain;
my $friends = User::Identity::Archive::Plain->new(friends);
$friends->from(*FH);
$friends->from(.friends);

An archive stores collections. It depends on the type of archive how and where that is done. Some archivers may limit the kinds of selections which can be stored.

Wiki::Toolkit::Store::Mediawiki is a Mediawiki (MySQL) storage backend for Wiki::Toolkit.

SYNOPSIS

Implementation of Wiki::Toolkit::Store::Database which reads and writes to a Mediawiki 1.6 database running in MySQL. This is module is intended to be capable of running concurrently with a Mediawiki 1.6 installation without data corruption. That said, use it at your own risk.

If you are looking for a general Wiki implementation, you might be better off looking at Wiki::Toolkit::Kwiki. It is simpler, more general, and does not require the database to be initialized by outside software. Currently, initializing the database for this module requires a working (PHP) Mediawiki installation.

I initially wrote this module because I was sick of running both PHP and Perl on my web server so that I could have the only wiki I could find with the full featureset I wanted running in parallel with the Perl scripts which generate the rest of my content dynamically. Generating my Perl content was much faster than my Mediawiki installation and I like Perl better, so PHP lost. Converting the old Mediawiki database into a format that a less fully featured wiki could read looked generally unrewarding, so here we are.

All date and time values are returned as Time::Piece::Adaptive objects. This should be transparent for most uses.

See Wiki::Toolkit::Store::Database for more on the general API.

Email::Store::DBI is a Perl module for database backend to Email::Store.

SYNOPSIS

use Email::Store dbi:...;

This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.

"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.

Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.