Free conduit software for linux

Conduit project is a synchronization application for GNOME.
Conduit allows you to synchronize your data between computers, or online web services (Gmail, backpackit.com, Flickr, etc).
This includes:
- Tomboy and iPod Notes
- Files and Folders
- Fspot and Flickr

Kontact Personal Information Management suite unites mature and proven KDE applications (called components in the context) under one roof. Thanks to the powerful KParts technology, all components are seamlessly integrated into one application.
The components of KDE Kontact are all shaped to work nice with each other. This results in features like intuitive drag n dropping between components and appointment handling, task lists and contacts.
KDE Kontact also extends its components with support for various groupware servers. When using these servers your workgroup will have access to features like shared email folders, group task lists, calendar sharing, central addressbooks and meeting scheduling.
In short: KDE Kontact delivers innovations to help you manage your communications more easily, organize your work faster and work together more closely, resulting in more productivity and efficiency in digital collaboration.
Main features:
The Summary Component
- This component is specially made for KDE Kontact. It provides both an overview of the other components and a selection of information gathered from the internet like weather info and headlines. In fact any RDF news feed can be added.
The Mail Component
- The mail component is provided by KMail, the KDE mail client -- a straight forward mail client that comes with all features you would expect.
The Calendar Component
- It is quite obvious that KOrganizer, again very mature KDE application, gets used as the calendar component. This feature-rich program is so easy to use and intuitive that you will quickly adopt it as your personal organizer. Extended with groupware functionality it can boost the communication within every workgroup.
The Contacts Component
- As the name implies: this component manages your valued contacts. The application providing this component is KAddressbook, a program that is deeply rooted into KDE. It was integrated in KMail and KOrganizer even before the KDE Kontact project was started
The Notes Component
- This component serves as your infinite block of digital sticky notes. Your can stick them on your desktop and they say visible even after closing KDE Kontact.
The News Component
- This straight forward, full-featured news reader is provided by KNode, KDEs default news reader.
The Sync Component
- KitchenSync, KDEs universal syncing application provides a framework for syncing with all kinds of devices. On one side it will have a plugin based interface with your mobile devices, like: PDAs and smart phones. On the other side it has conduits for connecting with other KDE Kontact components and external applications. The Sync component, provided by KitchenSync, is currently being implemented, therefore KitchenSync is not yet considered to be stable. Till the day that KitchenSync takes over we have two very nice applications that seamlessly integrate with KDE Kontact: KPilot for syncing with Palm compatible devices and Kandy for syncing with several mobile phone types. Eventually, KitchenSync will become a universal syncing framework.

phpDiveLog project displays the information of your Aqua DiveLog LogBook based on CSV files you generate with the Java Conduit shipped with Aqua DiveLog.
These dynamic pages are nicely and lucidly formatted. phpDiveLog allows you to combine these data with additional information, such as pictures or other external data sources.
You can create your own skins (template sets) to change the look and feel to match your Web site.
Main features:
- ...the DiveLogBook. Here you browse through the list of your dives (in the config file, you may specify how many entries should be displayed per page). For detailed information, a click on the dive# brings you directly to the log books entry.
- ...the Dive Statistics show you some basic stats about your dives, such as max/avg depth and divetime etc.
- ...the Dive Sites Information provides you with a list of your dive sites. Again, a click on the site# brings you to the details page
Enhancements:
- Sorting functionality was added to logbook and sitelist.
- Some vulnerability checks were added.

Jabber::RPC::HTTPgate is an HTTP gateway for Jabber-RPC / XML-RPC.

SYNOPSIS

use Jabber::RPC::HTTPgate;

my $gw = new Jabber::RPC::HTTPgate(
server => myserver.org:5701,
identauth => jrpchttp.localhost:secret,
httpcomp => http,
);

$gw->start;

Jabber::RPC::HTTPgate is an experimental gateway that provides a conduit service between traditional (HTTP-transported) XML-RPC encoded requests/responses and Jabber-RPC (XML-RPC encoded requests/responses transported over Jabber).

The idea is that you can start a gateway, that connects as a component to the backbone of a Jabber server, and it proxies Jabber-RPC to HTTP-based XML-RPC endpoints, and vice versa. That means that your Jabber-RPC client can not only make XML-RPC encoded calls to a Jabber-RPC endpoint but also to a traditional HTTP-based XML-RPC endpoint. And it also means that your traditional HTTP-based XML-RPC client can make XML-RPC encoded calls to a Jabber-RPC endpoint.

Jabber -> HTTP

When you create and start up a gateway, it listens for Jabber-RPC calls, just like a normal Jabber-RPC responder. On receipt of such a call, the gateway creates an HTTP request and sends this request on to the HTTP-based XML-RPC endpoint. The response received back from this HTTP call is relayed back to the original Jabber-RPC requester.
While a Jabber-RPC endpoint address is a Jabber ID (JID), an traditional XML-RPC endpoint address is a URL. So all the Jabber-RPC client needs to do is specify the URL in the resource part of the gateways endpoint JID.

HTTP -> Jabber

As well as listening for Jabber-RPC calls, a gateway will also service incoming HTTP requests that can be made to the HTTP component that this gateway uses. The HTTP component (called simply http) can be downloaded from the normal Jabber software repository.

On receipt of an HTTP request (passed to it by the HTTP component), the gateway creates a Jabber-RPC request containing the XML-RPC encoded payload, and sends it on to the Jabber-RPC responder endpoint. This endpoint is identified (via a JID) by the path part of the URL used in the call by the traditional client.

Timecardimport allows time sheet data to be imported from GnoTime or Palm Timesheet into SQL-Ledger as time cards.

Installation:

Extract Timecardimport.pm and tcimport.pl into the directory of your choice. Edit the variables in tcimport.pl to reflect your database and SQL-Ledger settings. The database user specified must have SELECT rights to customer, employee, parts and projects tables and INSERT rights to the jcitems table.

Usage:

The supplied tcimport.pl script is a sample front-end that calls on the Timecardimport.pm module to do the actual processing of the file. It should be fairly trivial to write additional front ends (eg. Web, gtk) based on the example of tcimport.pl, and such front ends may be included in later releases of this software. To use tcimport.pl, simply run the script from the command line with the file to import as the only argument.

GnoTime must be configured so that customer and project names are nested. That is, the first level of projects defined in GnoTime are the same as the customer names in SQL-Ledger, and the second level of projects are the projects for that customer as defined in SQL-Ledger. The sqltognotime.pl script supplied can create a template gnotime-data.xml file from your SQL-Ledger customers and projects for use with GnoTime.

When importing GnoTime timelines, the tag for any imported lines will be set to PAID, and the line will be ignored on any subsequent run.

If using Palm Timesheet, enter either the project names, or the customer name (in which case the first project of that customer in SQL-Ledger will be used). Since the import of customer and/or project names cannot be automated for Palm Timesheet like it can for GnoTime, the Timecardimport.pm module does not require an exact match between the name used in Palm Timesheet and that used in SQL-Ledger, but you must use an unambiguous substring in order to avoid mis-matches.

Palm Timesheet records can be exported in a number of formats. This script requires the "clockings" format to be used. There is no conduit to sync these records to your PC, but they can be exported from within Timesheet to an SD Card, or as a Memo which can be synchronised with the ordinary Memo conduit. Either of these methods will work fine with this script.