Darrell Anderson
8 years ago
37 changed files with 1 additions and 3568 deletions
@ -1,12 +0,0 @@
|
||||
################################################# |
||||
# |
||||
# (C) 2010-2011 Serghei Amelian |
||||
# serghei (DOT) amelian (AT) gmail.com |
||||
# |
||||
# Improvements and feedback are welcome |
||||
# |
||||
# This file is released under GPL >= 2 |
||||
# |
||||
################################################# |
||||
|
||||
tde_create_handbook( DESTINATION kpilot ) |
||||
|
Before Width: | Height: | Size: 45 KiB |
|
Before Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 18 KiB |
File diff suppressed because it is too large
Load Diff
|
Before Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 66 KiB |
@ -1,386 +0,0 @@
|
||||
<chapter id="faq"> |
||||
<title>&FAQ;</title> |
||||
|
||||
<sect1 id="faq-crash"> |
||||
<title>&kpilot; Startup Problems</title> |
||||
|
||||
<qandaset> |
||||
|
||||
<qandaentry> |
||||
<question> |
||||
<para> |
||||
What do I put after <option>--debug</option>? |
||||
</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
Nothing. Most versions of &kpilot; don't even have |
||||
a <option>--debug</option> option, and will complain if you use it. |
||||
For those versions that <emphasis>do</emphasis> have it, |
||||
use a value between 1 and 4, which will control the |
||||
amount of debugging printed (a little). |
||||
Using a value of 1 will print a fairly complete call trace |
||||
without the really-boring functions, while 4 will include every trivial |
||||
function in all of &kpilot;. |
||||
</para> |
||||
|
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
<qandaentry id="faq-connection"> |
||||
<question> |
||||
<para> |
||||
&kpilot; says <errorname>Can't connect to pilot</errorname> |
||||
</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
This can have various causes. Check that: |
||||
<itemizedlist> |
||||
<listitem> |
||||
<para> |
||||
The pilot device (usually <filename |
||||
class="devicefile">/dev/pilot</filename>) exists and points to the |
||||
serial port the &PalmPilot; is actually connected to. |
||||
</para> |
||||
<para> |
||||
To link the &PalmPilot; device to the correct serial port, you can |
||||
either fill in |
||||
<filename |
||||
class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename> |
||||
in the <guilabel>Pilot Device</guilabel> field in the <link |
||||
linkend="page-general">setup dialog</link> or (preferably) link |
||||
<filename class="devicefile">/dev/pilot</filename> to |
||||
<filename |
||||
class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename> |
||||
with the following command (as <systemitem |
||||
class="username">root</systemitem>): |
||||
<userinput> |
||||
<command>ln</command> |
||||
<option>-s</option> |
||||
<parameter>/dev/ttyS<replaceable>n</replaceable></parameter> |
||||
<parameter>/dev/pilot</parameter></userinput> |
||||
Here <filename |
||||
class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename> |
||||
is the name |
||||
of the serial port; replace <replaceable>n</replaceable> |
||||
with the correct number (usually 0 or 1). |
||||
</para> |
||||
</listitem> |
||||
<listitem> |
||||
<para> |
||||
Check that you have permission to read and write to the serial port. |
||||
The permissions for the serial port should be such that you can write to |
||||
it. This is most easily done by running the following (as root): |
||||
<userinput> |
||||
<command>chmod</command> |
||||
<option>666</option> |
||||
<parameter>/dev/ttyS<replaceable>n</replaceable></parameter> |
||||
</userinput> |
||||
</para> |
||||
</listitem> |
||||
<listitem> |
||||
<para> |
||||
Try starting the daemon by hand before starting &kpilot;. |
||||
</para> |
||||
</listitem> |
||||
<listitem> |
||||
<para> |
||||
(For &Linux-Mandrake; 7 systems) Check the system security level: |
||||
settings higher than 3 prevent some forms of inter-process |
||||
communication which are necessary for &kpilot; to |
||||
operate correctly. |
||||
</para> |
||||
|
||||
<para> |
||||
(<emphasis>&Linux-Mandrake; security information |
||||
courtesy of Jay Summett</emphasis>) |
||||
To set your |
||||
<!-- TM? --><acronym>MSEC</acronym> |
||||
<!-- TM? -->(Mandrake SECurity) |
||||
settings to not block the |
||||
&kpilot; socket (for connections to localhost) you can |
||||
login as root and |
||||
type |
||||
<userinput> |
||||
<command>/etc/security/msec/init.sh</command> |
||||
<option>3</option> |
||||
</userinput> |
||||
Which will set your |
||||
<!-- TM? --><acronym>MSEC</acronym> |
||||
level to 3 (regular security). |
||||
For more information about the various security levels, &etc;, see: |
||||
<ulink url="http://www.linux-mandrake.com/userguide/en/reference/017.html#157"> |
||||
the |
||||
<!-- TM? -->Mandrake |
||||
reference guide</ulink>. |
||||
</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
</para> |
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
</qandaset> |
||||
|
||||
</sect1> |
||||
|
||||
<sect1 id="faq-database"> |
||||
<title>Database Questions</title> |
||||
|
||||
<para> |
||||
This section answers questions commonly asked about |
||||
particular databases and how they |
||||
interact with &kpilot;. |
||||
</para> |
||||
|
||||
<qandaset> |
||||
|
||||
<qandaentry> |
||||
<question> |
||||
<para> |
||||
Databases become corrupted after a sync, |
||||
what should I do? |
||||
</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
Certain databases (from third-party software manufacturers) |
||||
appear not to follow the standard database layout. |
||||
If you can find out what the creator id of the database is, |
||||
you can add it to either the |
||||
<guilabel>Backup Only:</guilabel> list or the |
||||
<guilabel>Skip</guilabel> list in the |
||||
<link linkend="page-backup">settings dialog</link>. |
||||
</para> |
||||
|
||||
<para> |
||||
The following table shows which databases should be skipped |
||||
or backed-up only: |
||||
<table id="dbskip"> |
||||
<title>Databases needing Special Treatment</title> |
||||
<tgroup cols="3"> |
||||
<thead> |
||||
<row><entry>Database</entry><entry>Creator ID</entry><entry>Action</entry></row> |
||||
</thead> |
||||
<tbody> |
||||
<row> |
||||
<entry>Launcher (the &PalmPilot;'s main menu)</entry> |
||||
<entry>lnch</entry> |
||||
<entry>Backup Only:</entry> |
||||
</row> |
||||
<row> |
||||
<entry>Arranger</entry> |
||||
<entry>Arng</entry> |
||||
<entry>Backup Only:</entry> |
||||
</row> |
||||
<row> |
||||
<entry>(unknown)</entry> |
||||
<entry>PmDB</entry> |
||||
<entry>Backup Only:</entry> |
||||
</row> |
||||
<row> |
||||
<entry>AvantGo</entry> |
||||
<entry>avgo</entry> |
||||
<entry>Skip (Mostly because there's no point in backing up the |
||||
news articles that AvantGo gives you)</entry> |
||||
</row> |
||||
|
||||
</tbody> |
||||
</tgroup> |
||||
</table> |
||||
</para> |
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
<qandaentry> |
||||
<question> |
||||
<para> |
||||
Is there a conduit for &Netscape; <application>Calendar</application>? |
||||
</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
No, there isn't. |
||||
Neither are there plans to include support or write a |
||||
conduit for &Netscape; <application>Calendar</application>. |
||||
</para> |
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
|
||||
</qandaset> |
||||
|
||||
</sect1> |
||||
|
||||
<sect1 id="faq-hotsync"> |
||||
<title> |
||||
Special HotSync Questions |
||||
</title> |
||||
|
||||
<para> |
||||
This section lists questions about HotSync methods that differ |
||||
from the <quote>usual</quote> direct serial link method. |
||||
</para> |
||||
|
||||
<qandaset> |
||||
|
||||
<qandaentry> |
||||
<question> |
||||
<para> |
||||
How do I do an infrared (<acronym>IR</acronym>) HotSync? |
||||
</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
First of all your &PalmPilot; has to actually support |
||||
<acronym>IR</acronym> HotSyncs. This can be achieved through various |
||||
means: &PalmOS; 3.3 and higher include support for it; there is an |
||||
<acronym>IR</acronym> enhancements package for older &PalmOS; versions; |
||||
<application>IrLink</application> from IsComplete apparently has the |
||||
same capabilities. Check out the <ulink |
||||
url="http://www.palmone.com/us/">PalmOne</ulink> web pages for more information. |
||||
</para> |
||||
|
||||
<para> |
||||
Assuming your &PalmPilot; now has <acronym>PC</acronym> HotSync support |
||||
and it is setup to do <acronym>IR</acronym> HotSyncs (in the HotSync |
||||
preferences on the &PalmPilot;), we can turn our attention to the |
||||
<acronym>PC</acronym> you will be synchronization with. It needs an |
||||
<acronym>IR</acronym> port. For laptops, this is trivial, desktop |
||||
<acronym>PCs</acronym> may require some extra hardware. |
||||
</para> |
||||
|
||||
<para> |
||||
Your &Linux; kernel will need to support <acronym>IR</acronym> and the <acronym>IRCOMM</acronym> protocol. |
||||
For stock |
||||
&RedHat; |
||||
systems, the following command should |
||||
setup <acronym>IR</acronym> support (as <systemitem class="username">root</systemitem>): |
||||
<screen width="40"> |
||||
<prompt># </prompt><userinput><command>modprobe</command> <option>ircomm</option></userinput> |
||||
</screen> |
||||
|
||||
Other distributions should follow the <filename>IR-HOWTO</filename>. |
||||
Once <acronym>IR</acronym> support in the kernel has been activated, |
||||
you need to make devices for the <acronym>IR</acronym> ports. |
||||
The <filename>IR-HOWTO</filename> suggests (as <systemitem class="username">root</systemitem>): |
||||
<screen width="40"> |
||||
<prompt># </prompt><userinput><command>mknod</command> |
||||
<option>/dev/ircomm0</option> <parameter>60</parameter> <parameter>64</parameter> </userinput> |
||||
<prompt># </prompt><userinput><command>chmod</command> |
||||
<option>666</option> <parameter>/dev/ircomm0</parameter></userinput> |
||||
</screen> |
||||
Next we need to start some daemons for <acronym>IR</acronym> services: |
||||
<screen width="40"> |
||||
<prompt># </prompt><userinput><command>irattach</command> |
||||
<option>/dev/ttyS<replaceable>n</replaceable></option></userinput> |
||||
<prompt># </prompt><userinput><command>irmanager</command> |
||||
<option>-d</option> <parameter>0</parameter></userinput> |
||||
</screen> |
||||
Here <filename class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename> |
||||
is the serial port |
||||
the <acronym>IR</acronym> port is using. <replaceable>n</replaceable> could be 0, 1, or some other |
||||
number depending on your hardware setup. |
||||
Follow the instructions in the <filename>IR-HOWTO</filename> for assistance |
||||
(for desktop machines, it's usually a setting in the <acronym>BIOS</acronym>). |
||||
</para> |
||||
|
||||
<para> |
||||
Once you've gotten this far, just make <filename class="devicefile">/dev/pilot</filename> |
||||
point to <filename class="devicefile">/dev/ircomm0</filename> |
||||
and you're ready! |
||||
</para> |
||||
|
||||
<para> |
||||
The IR-HOWTO and other useful information on using IR may |
||||
be found at |
||||
<ulink url="http://mobilix.org/howtos.html">http://mobilix.org/howtos.html</ulink> |
||||
and |
||||
<ulink url="http://mobilix.org/software/irda/">http://mobilix.org/software/irda/</ulink>. |
||||
</para> |
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
<qandaentry> |
||||
<question> |
||||
<para>Can I do a &HotSync; with my (<acronym>USB</acronym>) |
||||
<!-- TM? -->&Handspring; &Visor;? |
||||
</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
Yes, you can. |
||||
I don't have definitive information, but postings on the |
||||
&kpilot; mailing-list have stated that you can point <filename class="devicefile">/dev/pilot</filename> |
||||
to the <acronym>USB</acronym> device and everything will work fine. |
||||
</para> |
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
<qandaentry> |
||||
<question><para>Is there any support for remote HotSyncs?</para> |
||||
</question> |
||||
<answer> |
||||
<para> |
||||
No, not yet. |
||||
Maybe later. |
||||
</para> |
||||
</answer> |
||||
</qandaentry> |
||||
|
||||
</qandaset> |
||||
|
||||
</sect1> |
||||
|
||||
|
||||
<sect1> |
||||
<title>&kpilot;'s &DCOP; interface</title> |
||||
|
||||
<qandaset> |
||||
|
||||
<qandaentry> |
||||
<question> |
||||
<para>What does &kpilot; use &DCOP; for?</para> |
||||
</question> |
||||
<answer><para> |
||||
The daemon and &kpilot; communicate using &DCOP; |
||||
for several purposes: logging messages, changing the &HotSync; |
||||
type, and exchanging configuration information. |
||||
</para></answer> |
||||
</qandaentry> |
||||
|
||||
<qandaentry><question> |
||||
<para>Which &DCOP; interfaces are there?</para></question> |
||||
|
||||
<answer><para> |
||||
The daemon has two important interfaces: |
||||
<interface>LogIface</interface> |
||||
and |
||||
<interface>KPilotDaemonIface |
||||
</interface>. |
||||
The <interface>LogIface</interface> |
||||
interface is used to record messages in the sync log |
||||
on the &handheld;, and is rarely used. |
||||
The <interface>KPilotDaemonIface</interface> |
||||
is the more important &DCOP; interface, |
||||
and is used to control the kind of &HotSync; that |
||||
&kpilot; will do. |
||||
</para></answer> |
||||
</qandaentry> |
||||
|
||||
<qandaentry><question><para> |
||||
How can I tell the daemon to perform a specific kind of &HotSync;?</para></question> |
||||
<answer><para> |
||||
There are three &DCOP; functions that control what kind |
||||
of &HotSync; |
||||
the daemon will do next: |
||||
<function></function> |
||||
<function></function> |
||||
</para></answer> |
||||
</qandaentry> |
||||
</qandaset> |
||||
|
||||
</sect1> |
||||
|
||||
</chapter> |
||||
|
Before Width: | Height: | Size: 52 KiB |
@ -1,280 +0,0 @@
|
||||
<?xml version="1.0" ?> |
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" |
||||
"dtd/kdex.dtd" [ |
||||
<!ENTITY kappname "&kpilot;"> |
||||
<!ENTITY kpilotver "4.4.6"> |
||||
<!ENTITY package "tdepim"> |
||||
<!ENTITY USB "<acronym>USB</acronym>"> |
||||
<!ENTITY PalmOS '<trademark class="registered">Palm OS</trademark>'> |
||||
<!ENTITY PalmOne '<trademark class="registered">PalmOne</trademark>'> |
||||
<!ENTITY Sony '<trademark class="registered">Sony</trademark>'> |
||||
<!ENTITY Clie "<productname><trademark>Clie</trademark></productname>"> |
||||
<!ENTITY FreeBSD '<trademark class="registered">FreeBSD</trademark>'> |
||||
<!ENTITY AvantGo '<trademark class="registered">AvantGo</trademark>'> |
||||
<!ENTITY handheld "handheld"> |
||||
<!ENTITY configuring-kpilot SYSTEM "configuration.docbook"> |
||||
<!ENTITY using-kpilot SYSTEM "usage.docbook"> |
||||
<!ENTITY synchronization SYSTEM "sync.docbook"> |
||||
<!ENTITY kpilot-faq SYSTEM "faq.docbook"> |
||||
<!ENTITY % English "INCLUDE" ><!-- Change language ONLY here --> |
||||
<!ENTITY % addindex "IGNORE"> |
||||
]> |
||||
|
||||
<!-- |
||||
From LW: http://www.palm.com/about/trademark.html According to this, |
||||
we have have overspecified some of the tradmarks... feel free to |
||||
adjust if you think this is the case. |
||||
--> |
||||
|
||||
<book lang="&language;"> |
||||
|
||||
<bookinfo> |
||||
<title>&kpilot; User's Guide</title> |
||||
|
||||
<authorgroup> |
||||
<author> |
||||
<firstname>Carlos</firstname> |
||||
<othername>Leonhard</othername> |
||||
<surname>Woelz</surname> |
||||
<affiliation> |
||||
<address><email>carloswoelz@imap-mail.com</email></address> |
||||
</affiliation> |
||||
</author> |
||||
<author> |
||||
<firstname>Adriaan</firstname> |
||||
<othername>de</othername> |
||||
<surname>Groot</surname> |
||||
<affiliation> |
||||
<address><email>groot@kde.org</email></address> |
||||
</affiliation> |
||||
</author> |
||||
<author> |
||||
<firstname>Dan</firstname> |
||||
<surname>Pilone</surname> |
||||
</author> |
||||
<!-- TRANS:ROLES_OF_TRANSLATORS --> |
||||
</authorgroup> |
||||
|
||||
<copyright> |
||||
<year>1999</year> |
||||
<year>2000</year> |
||||
<year>2001</year> |
||||
<year>2002</year> |
||||
<year>2003</year> |
||||
<year>2004</year> |
||||
<holder>Adriaan de Groot</holder> |
||||
</copyright> |
||||
|
||||
<copyright> |
||||
<year>2004</year> |
||||
<year>2005</year> |
||||
<holder>Carlos Woelz</holder> |
||||
</copyright> |
||||
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice> |
||||
|
||||
<date>2004-06-27</date> |
||||
<releaseinfo>&kpilotver;</releaseinfo> |
||||
|
||||
<abstract> |
||||
<para> |
||||
&kpilot; &kpilotver; is the &kde; version of the Desktop &HotSync; software for |
||||
&PalmOne; handhelds, the &ThreeCom; &PalmPilot; and other &PalmOS; devices. |
||||
</para> |
||||
</abstract> |
||||
|
||||
<keywordset> |
||||
<keyword>KDE</keyword> |
||||
<keyword>KPilot</keyword> |
||||
<keyword>tdepim</keyword> |
||||
<keyword>palm pilot</keyword> |
||||
<keyword>synchronization</keyword> |
||||
</keywordset> |
||||
|
||||
</bookinfo> |
||||
|
||||
<chapter id="introduction"> |
||||
<title>Introduction</title> |
||||
|
||||
<para> |
||||
&kpilot; &kpilotver; is an application that synchronizes your &PalmPilot; or |
||||
similar device (like the &Handspring; &Visor;, the &Sony; &Clie; or other |
||||
&PalmOS; devices) with your &kde; desktop, much like the Palm Desktop &HotSync; |
||||
software does for &Windows;. &kpilot; can back-up, restore, and &HotSync; your |
||||
&PalmPilot;. It can synchronize the built-in applications with their &kde; |
||||
counterparts. It also features additional conduits for third-party software. |
||||
</para> |
||||
|
||||
<para> |
||||
There is a web page for &kpilot;: the <ulink |
||||
url="http://www.kpilot.org/">Official &kpilot; Home Page</ulink>. The <ulink |
||||
url="http://pim.kde.org/">KDE-PIM website</ulink> also offers useful information |
||||
on the subject of <acronym>PIM</acronym> in general. &kpilot; shares the |
||||
tdepim-users mailing list, <email>tdepim-users@kde.org</email>. See <ulink |
||||
url="http://www.kde.org/mailinglists"> the mailing lists page</ulink> for more |
||||
information on subscribing and unsubscribing from the list. |
||||
</para> |
||||
|
||||
<!-- |
||||
<para> |
||||
A word about version numbers: &kpilot; 4.5.x is current and still unstable as of |
||||
August 2005. It does not work with KDE versions lower than 3.2. |
||||
</para> |
||||
--> |
||||
|
||||
<sect1 id="trademarks"> |
||||
<title>Trademarks</title> |
||||
<para> |
||||
&kpilot; describes synchronization operations |
||||
with &PalmOS; devices, and it uses the word &HotSync; |
||||
to name those synchronization operations, |
||||
while recognizing that &HotSync; is a trademark of |
||||
Palm, Inc. Holders of other trademarks, such as |
||||
&Handspring; &Visor;, &Sony; &Clie;, and |
||||
the Palm, Inc. trademarks &PalmPilot; and |
||||
<productname><trademark>Zire</trademark></productname> |
||||
are recognized as well. |
||||
</para> |
||||
</sect1> |
||||
|
||||
</chapter> |
||||
|
||||
<chapter id="overview"> |
||||
<title>Overview of &kpilot;</title> |
||||
|
||||
<para> |
||||
&kpilot; consists of two parts: the &kpilot; daemon, which sits |
||||
in the system tray and handles the actual communication with |
||||
the &handheld;, and the normal &kpilot; program, which lets |
||||
you configure the daemon and view the databases on your |
||||
&handheld;. In normal operation, you will not need to use &kpilot; |
||||
itself very much, since the daemon handles communication unobtrusively |
||||
and synchronizes your data to &kde; applications like &korganizer; |
||||
and &knotes;. &kpilot; is integrated into &kontact; as well. |
||||
</para> |
||||
|
||||
<para> |
||||
It is vital to configure &kpilot; before use. At the very least, |
||||
you need to tell it which hardware device to use to communicate with |
||||
your &handheld;. |
||||
Configuration settings are described at length in |
||||
the <link linkend="configure">section on configuring &kpilot;</link>. |
||||
For the impatient, the <link linkend="configwizard">configuration wizard</link> |
||||
can set up most things for you. |
||||
</para> |
||||
|
||||
<para> |
||||
Once &kpilot; is configured, you should make a <link |
||||
linkend="backup">backup</link> of your &handheld; first. That is to be on the |
||||
safe side. Once that is done, you can just leave the &kpilot; daemon running in |
||||
the system tray, and all you need to do is press the &HotSync; button, and |
||||
changes in the &handheld; data and the &kde; applications will be <link |
||||
linkend="synchronization">synchronized</link>, so that the information matches |
||||
again on both the &handheld; and the desktop. |
||||
</para> |
||||
|
||||
<para> |
||||
If you want to <link linkend="page-viewers">examine</link> the |
||||
data stored on your &handheld;, the built in <link |
||||
linkend="page-viewers">viewers</link> can be used. This allows you to view |
||||
memos, addresses, &etc;. There is a generic hexadecimal database viewer for |
||||
advanced use. |
||||
</para> |
||||
|
||||
<para> |
||||
Finally, &kpilot; can be used to <link linkend="installer-app">install</link> |
||||
new programs and databases on your &handheld;. |
||||
</para> |
||||
|
||||
<!-- |
||||
FIXME: Old Warnings |
||||
<caution> |
||||
<title>Changes in &kpilotver;</title> |
||||
<para> |
||||
The expressiveness of the <guilabel>No Backup</guilabel> configuration |
||||
item, which prevents specific databases from being backed up (for space, speed, |
||||
or stability reasons), has been extended. |
||||
In particular, the old format listed only |
||||
creator values, while the new format can list wildcard database names |
||||
as well as creator values. |
||||
The value set in the configuration dialog will be automatically adjusted to |
||||
the new format. |
||||
</para> |
||||
<para> |
||||
In &kpilot; &kpilotver;, the way conduits are programmed changed, |
||||
and you will need to use newly compiled conduits. If there are |
||||
old conduits on your system, &kpilot; will prompt you to remove them. |
||||
</para> |
||||
<para> |
||||
Please take the time to review all of the configuration settings. |
||||
</para> |
||||
</caution> |
||||
--> |
||||
</chapter> |
||||
|
||||
|
||||
&configuring-kpilot; |
||||
&using-kpilot; |
||||
&synchronization; |
||||
&kpilot-faq; |
||||
|
||||
|
||||
<chapter id="credits"> |
||||
|
||||
<title>Credits and License</title> |
||||
|
||||
<para> |
||||
&kpilot; |
||||
Program copyright 1998-2000 by &Dan.Pilone; |
||||
&Dan.Pilone.mail; |
||||
</para> |
||||
<para> |
||||
Contributors: |
||||
<itemizedlist> |
||||
<listitem><para>Adriaan de Groot <email>groot@kde.org</email></para> |
||||
</listitem> |
||||
<listitem><para>&Preston.Brown; <email>pbrown@redhat.com</email></para> |
||||
</listitem> |
||||
<listitem><para>VCal and Todo Conduits by: Herwin Jan Steehouwer, |
||||
Kenneth Albanowski, &Michael.Kropfberger; |
||||
</para></listitem> |
||||
<listitem><para>Popmail Conduit overhaul: Marko Grönroos |
||||
</para></listitem> |
||||
<listitem><para>&kaddressbook; Conduit: Greg Stern |
||||
</para></listitem> |
||||
<listitem><para>Patches by: |
||||
Jörn Ahrens, |
||||
Robert Ambrose, |
||||
Jörg Habenicht, |
||||
Philipp Hullmann, |
||||
Dag Nygren, |
||||
Scott Presnell, |
||||
Heiko Purnhagen, |
||||
Chuck Robey |
||||
and |
||||
Jay Summet |
||||
</para></listitem> |
||||
</itemizedlist> |
||||
</para> |
||||
|
||||
<para> |
||||
Documentation copyright 2000,2001 Adriaan de Groot <email>groot@kde.org</email>. |
||||
Documentation copyright 2004,2005 Carlos Leonhard Woelz |
||||
<email>carloswoelz@imap-mail.com</email> |
||||
</para> |
||||
|
||||
<!-- TRANS:CREDITS_FOR_TRANSLATORS --> |
||||
&underFDL; |
||||
&underGPL; |
||||
</chapter> |
||||
|
||||
&documentation.index; |
||||
</book> |
||||
<!-- |
||||
Local Variables: |
||||
sgml-minimize-attributes: nil |
||||
sgml-general-insert-case: lower |
||||
End: |
||||
--> |
||||
|
||||
|
Before Width: | Height: | Size: 96 KiB |
|
Before Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 5.3 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 68 KiB |
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 42 KiB |
@ -1,450 +0,0 @@
|
||||
<chapter id="synchronization"> |
||||
<title>Syncing your &handheld; with a PC</title> |
||||
|
||||
<para> |
||||
This chapter describes the synchronization process |
||||
that &kpilot; uses, focusing on the &kpilot; daemon functionality. |
||||
You may sync your &handheld; using the <link linkend="builtin">internal |
||||
viewers</link> and / or <link linkend="conduits">conduits</link>, depending |
||||
on your personal preferences. Conduits allow external applications to interface |
||||
with the data on your &handheld;. |
||||
</para> |
||||
|
||||
<para> |
||||
It is a good idea to make a <link linkend="backup">backup</link> |
||||
of your &handheld; regularly. Other than making backups, it should rarely be |
||||
necessary to do anything other than drop your &handheld; on the cradle and press |
||||
the &HotSync; button. The &kpilot; daemon icon in the system tray will flash |
||||
indicating that a sync is under way. |
||||
</para> |
||||
|
||||
|
||||
<screenshot> |
||||
<screeninfo>&kpilot; Daemon Pop-Up Menu</screeninfo> |
||||
<mediaobject> |
||||
<imageobject><imagedata fileref="daemon-menu.png" format="PNG"/></imageobject> |
||||
<textobject><phrase>&kpilot; daemon popup menu</phrase></textobject> |
||||
<caption><para>&kpilot; daemon popup menu</para></caption> |
||||
</mediaobject> |
||||
</screenshot> |
||||
|
||||
|
||||
<para> |
||||
To which type of sync &kpilot; will perform next, you can use the main |
||||
application |
||||
<link linkend="menu-file"> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
</menuchoice> |
||||
menu</link>, |
||||
or right click the &kpilot; daemon icon located in the system tray, |
||||
and select one of the menu items under the |
||||
<menuchoice> |
||||
<guisubmenu>Next Sync</guisubmenu> |
||||
</menuchoice> |
||||
sub menu. |
||||
<tip><para> |
||||
If you hover over the &kpilot; daemon icon, a tooltip will appear showing you |
||||
what the type of sync &kpilot; will perform next. |
||||
</para></tip> |
||||
|
||||
</para> |
||||
|
||||
|
||||
|
||||
<para> |
||||
In short, the sync types are: |
||||
</para> |
||||
|
||||
<itemizedlist> |
||||
|
||||
<listitem><para> |
||||
<guilabel>HotSync (once)</guilabel>: this option offers |
||||
a nice balance between speed and data safety. |
||||
</para></listitem> |
||||
|
||||
<listitem><para> |
||||
<guilabel>FastSync (once)</guilabel>: only sync those |
||||
databases that have conduits. |
||||
</para></listitem> |
||||
|
||||
<listitem><para> |
||||
<guilabel>FullSync (once)</guilabel>: the safest option, but |
||||
takes the longest time to complete. |
||||
</para></listitem> |
||||
|
||||
<listitem><para> |
||||
<guilabel>Backup (once)</guilabel>: copy all the data from the &handheld; to the |
||||
<acronym>PC</acronym>. |
||||
</para></listitem> |
||||
|
||||
<listitem><para> |
||||
<guilabel>Restore from Backup (once)</guilabel>: copy the data from a previous backup from the PC to the |
||||
&handheld;, erasing the data previously held there. |
||||
|
||||
<warning><para> |
||||
Use the restore functionality with care, as you can lose all the new |
||||
data entered on the &handheld; since the last backup. |
||||
</para></warning> |
||||
</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> |
||||
<guilabel>Copy Handheld to PC (once)</guilabel>: run all conduits and |
||||
sync all databases, but instead of merging the information from both sources, |
||||
just copy the handheld data to the PC. |
||||
<warning><para>Use with care, as this option erases the changes |
||||
you made in your PC since the last sync.</para></warning> |
||||
</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> |
||||
<guilabel>Copy PC to Handheld (once)</guilabel>: run all conduits and |
||||
sync all databases, but instead of merging the information from both sources, |
||||
just copy the PC data to the handheld. |
||||
<warning><para>Use with care, as this option erases the changes |
||||
you made in your handheld since the last sync.</para></warning> |
||||
</para> |
||||
</listitem> |
||||
|
||||
</itemizedlist> |
||||
|
||||
|
||||
<para> |
||||
Alternatively, you can change the default syncing behavior of &kpilot; by |
||||
choosing the most suitable option in the <link linkend="page-hotsync">&HotSync; |
||||
configure dialog</link>. |
||||
|
||||
<note><para> |
||||
To configure the conduits or the sync process, you do not need to open the main |
||||
&kpilot; application, as the |
||||
<menuchoice> |
||||
<guimenuitem>Configure KPilot...</guimenuitem> |
||||
</menuchoice> |
||||
menu item is available on the &kpilot; daemon popup menu as well. |
||||
</para></note> |
||||
|
||||
</para> |
||||
|
||||
<sect1 id="backup"> |
||||
<title>Backing up your &handheld; data</title> |
||||
|
||||
<para> |
||||
On every backup, &kpilot; stores a copy of all your &handheld; data under the |
||||
<filename class="directory">$TDEHOME/share/apps/kpilot/DBBackup/User Name/</filename> |
||||
folder, allowing you to restore that copy later, if needed. The |
||||
<filename class="directory">$TDEHOME</filename> environment variable |
||||
(typically <filename class="directory">/home/Login Name/.trinity/</filename>) |
||||
points to the folder that contains your configuration and data for the &kde; |
||||
applications.</para> |
||||
|
||||
<para> |
||||
It is a good idea to backup your data often. To perform a backup, you can click |
||||
the |
||||
<menuchoice> |
||||
<guisubmenu>Next Sync</guisubmenu> |
||||
<guimenuitem>Backup</guimenuitem> |
||||
</menuchoice> |
||||
on the &kpilot; daemon icon popup menu or the |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Backup</guimenuitem> |
||||
</menuchoice> |
||||
menu item on the main &kpilot; application menu in order |
||||
to make the next sync a backup. Then, just press the &HotSync; button. |
||||
</para> |
||||
|
||||
</sect1> |
||||
|
||||
<sect1 id="restore"> |
||||
<title>Restoring Your &handheld; Data</title> |
||||
|
||||
<para> |
||||
The restore operation consist of transferring all the data previously saved on |
||||
the <acronym>PC</acronym> to the &handheld;, effectively erasing all the new |
||||
data held by the device by returning it to a previous state. |
||||
<warning><para> |
||||
Use the restore functionality with care, as you can lose all the new |
||||
data entered on the &handheld; since the last backup. |
||||
</para></warning> |
||||
</para> |
||||
|
||||
<para> |
||||
The data saved on the last backup is located on the <filename class="directory">$TDEHOME/share/apps/kpilot/DBBackup/User Name/</filename> |
||||
folder. The <filename class="directory">$TDEHOME</filename> environment variable |
||||
(typically <filename class="directory">/home/Login Name/.trinity/</filename>) |
||||
points to the folder that contains your configuration and data for the &kde; |
||||
applications.</para> |
||||
|
||||
<para> |
||||
The most common use for the restore functionality is to recover from a hardware |
||||
or software failure on the device. |
||||
The restore function can be accessed from the |
||||
main &kpilot; application, and from the &kpilot; daemon. be careful, as |
||||
restoring the data is not a common operation. In order |
||||
to restore the data at the next sync, click the |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Restore</guimenuitem> |
||||
</menuchoice> |
||||
menu item, then press the &HotSync; button. |
||||
</para> |
||||
|
||||
</sect1> |
||||
|
||||
|
||||
<sect1 id="sync-s"> |
||||
<title>Selecting the Synchronization Type</title> |
||||
|
||||
<para> |
||||
There are three ways to sync your &handheld;, <guilabel>HotSync</guilabel>, |
||||
<guilabel>FastSync</guilabel> or <guilabel>FullSync</guilabel>. |
||||
</para> |
||||
|
||||
<para> |
||||
When you press the &HotSync; button on your &handheld;, &kpilot;'s will run the |
||||
default sync operation (usually a <guilabel>HotSync</guilabel>). You can select |
||||
the default sync operation in the <link linkend="page-hotsync">&HotSync; |
||||
configure dialog</link>. Alternatively, you can click one of the sync options on |
||||
the main &kpilot; application |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
</menuchoice> |
||||
menu or on the &kpilot; daemon popup |
||||
<menuchoice> |
||||
<guisubmenu>Next Sync</guisubmenu> |
||||
</menuchoice> |
||||
submenu. |
||||
|
||||
<important><para> |
||||
Using the <link linkend="page-hotsync">&HotSync; configure dialog</link> |
||||
is the only way to change the default sync operation. |
||||
The main &kpilot; application |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
</menuchoice> |
||||
menu items or the &kpilot; daemon popup |
||||
<menuchoice> |
||||
<guisubmenu>Next Sync</guisubmenu> |
||||
</menuchoice> |
||||
submenu items change only the type of sync that will be performed <emphasis>next</emphasis>. |
||||
</para></important> |
||||
</para> |
||||
|
||||
<screenshot> |
||||
<screeninfo>&kpilot; Daemon Pop-Up Menu</screeninfo> |
||||
<mediaobject> |
||||
<imageobject><imagedata fileref="daemon-menu.png" format="PNG"/></imageobject> |
||||
<textobject><phrase>&kpilot; daemon popup menu</phrase></textobject> |
||||
<caption><para>&kpilot; daemon popup menu</para></caption> |
||||
</mediaobject> |
||||
</screenshot> |
||||
|
||||
|
||||
<para> |
||||
For more information on the sync types, please refer to the descriptions |
||||
available in <xref linkend="page-hotsync" />. |
||||
</para> |
||||
|
||||
|
||||
</sect1> |
||||
|
||||
<sect1 id="conduits"> |
||||
<title>Syncing your &handheld; Data Using Conduits</title> |
||||
|
||||
<para> |
||||
Conduits are programs that interface your &handheld; data with |
||||
<acronym>PC</acronym> applications or sync your &handheld; data with files |
||||
that can be used by <acronym>PC</acronym> applications. |
||||
</para> |
||||
|
||||
<para> |
||||
Conduits can be set up by selecting |
||||
<menuchoice> |
||||
<guimenu>Settings</guimenu> |
||||
<guimenuitem>Configure KPilot...</guimenuitem> |
||||
</menuchoice>, or using the daemon pop up menu and clicking the |
||||
<guimenuitem>Configure KPilot...</guimenuitem> |
||||
menu item. |
||||
</para> |
||||
|
||||
<screenshot> |
||||
<screeninfo>&kpilot; Daemon Pop-Up Menu</screeninfo> |
||||
<mediaobject> |
||||
<imageobject><imagedata fileref="daemon-menu.png" format="PNG"/></imageobject> |
||||
<textobject><phrase>&kpilot; daemon popup menu</phrase></textobject> |
||||
<caption><para>&kpilot; daemon popup menu</para></caption> |
||||
</mediaobject> |
||||
</screenshot> |
||||
|
||||
<para> |
||||
The <guilabel>Conduits</guilabel> tree in the configuration dialog |
||||
collects all the installed conduits available. |
||||
The conduits can be enabled and disabled |
||||
by clicking on the check box to the left of the conduit's name. |
||||
Conduits can have an extensive configuration of |
||||
their own, and may be supplied by third parties. |
||||
Most of the conduits require some initial configuration, so it is strongly |
||||
recommended to check the |
||||
<link linkend="config-conduits">section detailing the default conduits |
||||
configuration</link> before using them. |
||||
</para> |
||||
|
||||
|
||||
<para> |
||||
The default conduits are the following: |
||||
</para> |
||||
|
||||
|
||||
<variablelist> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>KNotes / Memos</guilabel></term> |
||||
<listitem><para> |
||||
Synchronizes the Memo Pad application with &knotes;. |
||||
|
||||
<important><para> |
||||
The conduit only synchronizes the Memo Pad data if &knotes; is running. If you |
||||
want to enable this functionality, please remember to start &knotes; first, or |
||||
check if it is already running (tip: look for the &knotes; icon in the system tray). |
||||
</para></important> |
||||
|
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Notepad</guilabel></term> |
||||
<listitem> |
||||
<para> |
||||
Exports the free hand notes of the &handheld;'s Notepad application as pictures |
||||
to the PC. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Time Synchronization</guilabel></term> |
||||
<listitem><para> |
||||
Sets the &handheld;'s time to that of the desktop machine. |
||||
Useful for keeping the clock of the &handheld; accurate. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Calendar (KOrganizer)</guilabel></term> |
||||
<listitem><para> |
||||
Synchronizes the Datebook application with &korganizer; or with a iCalendar file of |
||||
your choice. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Palm DOC</guilabel></term> |
||||
<listitem><para> |
||||
Automatically converts, installs and sync text files in the &PalmPilot; |
||||
DOC format, so you can read the text files with most DOC-capable |
||||
applications on the &handheld;. There are many free or open source Palm |
||||
DOC readers, and some Palm DOC editors for your handheld.</para> |
||||
<para> |
||||
Any plain text file can be easily converted. For instance, you can download and |
||||
convert the public domain books provided by the <ulink url="http://www.gutenberg.net"> |
||||
Gutenberg Project</ulink> and read them in your &handheld;. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Addressbook</guilabel></term> |
||||
<listitem><para> |
||||
Synchronizes the Address application with &kaddressbook; or with a vCard file of |
||||
your choice. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>System Information</guilabel></term> |
||||
<listitem><para> |
||||
Writes information about your &handheld;, (such as OS version, |
||||
RAM available, and the list of databases) to a file. Useful mostly for |
||||
debugging purposes. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>ToDo's (KOrganizer)</guilabel></term> |
||||
<listitem><para> |
||||
Synchronizes the Todo list application with &korganizer; or with a iCalendar file of |
||||
your choice. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>MAL (AvantGo) Conduit</guilabel></term> |
||||
<listitem><para> |
||||
Synchronizes your &handheld; with the &AvantGo; server. The &AvantGo; server |
||||
offers general content (news, guides, stock quotes, &etc;) in a format that is |
||||
suitable for reading in a &handheld;. To use this conduit, you need to register, subscribe |
||||
the channels you select and install the &AvantGo; software on your &handheld;. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Mail</guilabel></term> |
||||
<listitem><para> |
||||
Sends mail written on the &handheld; through &kmail;. |
||||
There is no provision for receiving mail, however. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term><guilabel>Perl</guilabel></term> |
||||
<term><guilabel>Python</guilabel></term> |
||||
<term><guilabel>NULL</guilabel></term> |
||||
<listitem><para> |
||||
These conduits are intended as a programming demonstration, |
||||
and serve no practical purpose during a &HotSync;. |
||||
They are not normally listed, but you may see them on some systems. |
||||
</para></listitem> |
||||
</varlistentry> |
||||
|
||||
</variablelist> |
||||
|
||||
<screenshot> |
||||
<screeninfo>The Conduit Setup Dialog</screeninfo> |
||||
<mediaobject> |
||||
<imageobject><imagedata fileref="setup-conduit.png" format="PNG"/></imageobject> |
||||
<textobject><phrase>The Conduit Setup Dialog</phrase></textobject> |
||||
<caption><para>The Conduit Setup Dialog</para></caption> |
||||
</mediaobject> |
||||
</screenshot> |
||||
|
||||
|
||||
</sect1> |
||||
|
||||
<sect1 id="conflicts"> |
||||
<title>Resolving Conflicts</title> |
||||
|
||||
<para> |
||||
Data records can be changed both on the &handheld; and |
||||
on the <acronym>PC</acronym>. If one record has incompatible changes |
||||
in both the &handheld; and the <acronym>PC</acronym>, (such as |
||||
changing a phone number in different ways on both sides), |
||||
the conflicting change needs to be resolved so |
||||
that both the &handheld; and the <acronym>PC</acronym> are in sync again. |
||||
</para> |
||||
|
||||
<para> |
||||
A popup dialog may appear, asking you how to resolve the |
||||
conflict, or you may have a general rule to automatically handle these |
||||
conflicts (depending on your <link linkend="page-hotsync">conflict resolution |
||||
choice</link>). Note that you can define different resolution choices |
||||
for different conduits in the <link linkend="config-conduits">conduits |
||||
configuration dialog</link>. |
||||
</para> |
||||
|
||||
</sect1> |
||||
</chapter> |
||||
|
Before Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 1.0 KiB |
|
Before Width: | Height: | Size: 984 B |
@ -1,648 +0,0 @@
|
||||
<chapter id="using-kpilot"> |
||||
<title>Using &kpilot; Data Viewers and Main Window Interface</title> |
||||
|
||||
<para> |
||||
This chapter describes the usage of &kpilot;'s main window; as a viewer |
||||
application for data on the &handheld;, and its menu structure. |
||||
The main window of &kpilot; also contains |
||||
the &HotSync;-log, which can be useful when |
||||
debugging problems. |
||||
</para> |
||||
|
||||
<para> |
||||
&kpilot; starts up with a splash screen, and then switches to showing the |
||||
&HotSync;-log, as shown <link linkend="main-app">here</link>. |
||||
</para> |
||||
|
||||
<sect1 id="main"> |
||||
<title>The Main Window</title> |
||||
|
||||
<screenshot id="main-app"> |
||||
<screeninfo>&kpilot; Main Window</screeninfo> |
||||
<mediaobject> |
||||
<imageobject><imagedata fileref="main-app.png" format="PNG"/></imageobject> |
||||
<textobject><phrase>The Main Window</phrase></textobject> |
||||
<caption><para>The Main Window</para></caption> |
||||
</mediaobject> |
||||
</screenshot> |
||||
|
||||
<para> |
||||
The main window contains the application menu, which we will deal with here. |
||||
</para> |
||||
|
||||
<para> |
||||
The <guimenu>file</guimenu> menu contains the synchronization menu items. Note |
||||
that these items do not start the sync process, they only select what the new |
||||
sync will be. To really start it, you must press the HotSync button on your |
||||
&PalmPilot;'s cradle (or on the &handheld; itself, when there is no cradle). |
||||
</para> |
||||
<note> |
||||
<para> |
||||
It is not possible to cancel a sync operation once the request has been made. |
||||
</para> |
||||
</note> |
||||
<para> |
||||
For more information regarding the synchronization functionality, please check the |
||||
<link linkend="synchronization">Synchronization Chapter</link> of this handbook, |
||||
where you can find detailed descriptions of the synchronization methods |
||||
and options offered by &kpilot;. |
||||
</para> |
||||
|
||||
<variablelist id="menu-file"> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>HotSync</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
Make the next sync a &HotSync;. For more information, please check the |
||||
<link linkend="sync-s"> Syncing your &handheld; data</link> section of this |
||||
handbook. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>FastSync</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
(not available with all installations) |
||||
Make the next sync a FastSync. For more information, please check the |
||||
<link linkend="sync-s">Syncing your &handheld; data</link> section of this |
||||
handbook. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>FullSync</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
(not available with all installations) |
||||
Make the next sync a FullSync. For more information, please check the |
||||
<link linkend="sync-s"> Syncing your &handheld; data</link> section of this |
||||
handbook. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Backup</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
Make the next sync a full backup of your &PalmPilot; data. This action can take |
||||
several minutes. For more information, please check the |
||||
<link linkend="backup"> Backing up your &handheld; data</link> section of this |
||||
handbook. |
||||
</para> |
||||
<tip> |
||||
<para> |
||||
The first thing you should do after starting &kpilot; for |
||||
the first time is make a full backup. |
||||
</para> |
||||
</tip> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Restore</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
This copies all the data from a previous backup on your |
||||
<acronym>PC</acronym> to your &PalmPilot;, |
||||
replacing whatever data was there. |
||||
Use this if your &PalmPilot; suffers some from software or hardware failure |
||||
(or is replaced by a new one). For more information, please check the |
||||
<link linkend="restore"> Restoring your &handheld; data</link> section of this |
||||
handbook. |
||||
</para> |
||||
<warning> |
||||
<para> |
||||
Doing a restore will erase all data on the &PalmPilot; |
||||
before restoring the information from your |
||||
<acronym>PC</acronym>!</para> |
||||
</warning> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Copy Handheld to PC</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
This runs all conduits and syncs all databases, but instead of merging the |
||||
information from both sources, it will copy the handheld data to the PC. |
||||
<emphasis>Use with care, as this option erases the changes |
||||
you made in your PC since the last sync</emphasis>.</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Copy PC to Handheld</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
This runs all conduits and syncs all databases, but instead of merging the |
||||
information from both sources, it will copy the PC data to the handheld. |
||||
<emphasis>Use with care, as this option erases the changes |
||||
you made in your handheld since the last sync</emphasis>.</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<!-- |
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>List Only</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
The next sync will only list the databases on your &handheld;, no exchange of |
||||
data will be performed. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
--> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>File</guimenu> |
||||
<guimenuitem>Quit</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
Quits &kpilot;, closing the main window and stopping the |
||||
daemon if that |
||||
<link linkend="stopdaemononexit">configuration option</link> |
||||
is enabled. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
</variablelist> |
||||
|
||||
|
||||
<para> |
||||
The <guimenu>Settings</guimenu> menu allows you to configure &kpilot; main |
||||
interface and fine-tune the synchronization process with the &handheld;. |
||||
</para> |
||||
|
||||
<variablelist> |
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>Settings</guimenu> |
||||
<guimenuitem>Show Statusbar</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
Click this menu item to toggle &kpilot;'s status bar on and off, or in other |
||||
words, to show it if hidden, or to hide it if shown. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>Settings</guimenu> |
||||
<guimenuitem>Show Toolbar</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
Click this menu item to toggle &kpilot;'s toolbar on and off, or in other |
||||
words, to show it if hidden, or to hide it if shown. |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>Settings</guimenu> |
||||
<guimenuitem>Configure Shortcuts...</guimenuitem> |
||||
</menuchoice> |
||||
</term> |
||||
<listitem> |
||||
<para> |
||||
Displays &kpilot;'s shortcut configuration dialog, allowing you change or create |
||||
key bindings, which are associations between actions (for example, opening |
||||
&kpilot;'s configuration dialog) and keys or key combinations (for instance, |
||||
Ctrl + Shift + a). |
||||
</para> |
||||
</listitem> |
||||
</varlistentry> |
||||
|
||||
|
||||
<varlistentry> |
||||
<term> |
||||
<menuchoice> |
||||
<guimenu>Settings</guimenu> |
||||
<guimenuitem>Configure Toolbars...</guimenuitem> |
||||
</menuchoice> |
||||