The conduits used by KPilot can be enabled and configured after selecting -> . The following is a list of some important conduits:
This conduit handles the data exchange with the handheld's address book. The KDE counterpart for managing these contacts is KAddressBook. Start it from the main menu or with the command kaddressbook. For details about this program, refer to 7. Address Management with KAddressBook.
This conduit allows you to transfer notes created with KNotes to the handheld's memo application. Start the KDE application from the main menu or with the command knotes.
This conduit is responsible for syncing the appointments (events) of the hendheld. The desktop equivalent is KOrganizer. For more information about this program, refer to 6. Scheduling with KOrganizer.
This conduit is responsible for syncing task (to-do) items. The desktop counterpart is again KOrganizer.
Enabling this conduit adjusts the handheld's clock to that of the desktop computer during each sync operation. This is only a good idea if the clock of the desktop computer itself is corrected by a time server at fairly frequent intervals.
To be able to use KPilot, first set up the connection with the handheld computer. The configuration depends on the type of cradle (docking unit) used with the handheld. There are two types of these: USB cradles and serial cradles.
The easiest way to set up the connection is by using the configuration assistant. Select 188.8.131.52. “Creating a /dev/pilot Link”.+ to start the assistant. In the first step, enter your user name and the name of the device to which the handheld is connected. The assistant attempts to detect them itself if you select . If the autodetection fails, refer to
After confirming with, the assistant prompts you to specify the applications that should be used for synchronization. You can choose among the KDE application suite (default), Evolution, and none. After selecting, close the window with .
The setup of the connection with a serial handheld cradle is different from that of a USB cradle. Depending on which cradle is used, you may or may not need to create a symbolic link named /dev/pilot.
Normally, a USB cradle is autodetected and there should be no need to create the symbolic link mentioned.
With a serial cradle, you need to know to which serial port it is actually connected. Serial devices are named /dev/ttyS?, starting from /dev/ttyS0 for the first port. To set up a cradle connected to the first serial port, enter the command:
ln -s /dev/ttyS0 /dev/pilot
Initially, it should be sufficient to enable the KAddressBook conduit without changing any of the defaults. After the data has been synchronized for the first time, configure the details: what to do in case of conflicts, the way in which backup databases are saved, and how certain fields as stored on the handheld should be assigned to the fields expected by KAddressBook.
On the KDE desktop, to-dos (tasks) and events (appointments) are managed with KOrganizer. Start the application from the main menu or with the command korganizer. After enabling the calendar and the to-do conduit of KPilot, set some configuration options before using them.
KOrganizer stores its files in the directory ~/.kde/share/apps/korganizer. However, given that the directory .kde/ begins with a dot, it may not be shown by the file selection dialog. In this case, enter the complete path manually or explicitly toggle the display of hidden files (dot files) in the file selection dialog. The default shortcut for this is F8.
After opening the directory ~/.kde/share/apps/korganizer, select a file that can be used as a calendar file by KOrganizer. In our example, this is the file palm.ics. In the case of a user called tux, the complete path and file name would be /home/tux/.kde/share/apps/korganizer/palm.ics, as shown in Figure 5.3. “Dialog Showing the Path to a KOrganizer Calendar File”.
KOrganizer should not be running when data is being exchanged with the handheld. Otherwise KPilot fails to carry out the sync operation.