|
Lines 1-1783
Link Here
|
| 1 |
<chapter id="configure"> |
|
|
| 2 |
<title>Configuring &kpilot;</title> |
| 3 |
|
| 4 |
<para> |
| 5 |
Once &kpilot; is installed it needs to be |
| 6 |
configured |
| 7 |
to match your hardware. |
| 8 |
The <link linkend="config-conduits">conduits</link> |
| 9 |
need to be configured as well. |
| 10 |
After that you can use &kpilot; |
| 11 |
to synchronize your &PalmPilot; with |
| 12 |
your &kde; desktop or view |
| 13 |
data from your &PalmPilot; with the |
| 14 |
<link linkend="builtin">built-in viewers</link>. |
| 15 |
</para> |
| 16 |
|
| 17 |
<para> |
| 18 |
When you run &kpilot; from either |
| 19 |
the panel menu or from the command prompt for the first time |
| 20 |
it will prompt you with |
| 21 |
a dialog box to configure it. |
| 22 |
This configuration dialog can be requested later |
| 23 |
from the main application |
| 24 |
<menuchoice> |
| 25 |
<guimenu>Settings</guimenu> |
| 26 |
<guimenuitem>Configure &kpilot;</guimenuitem> |
| 27 |
</menuchoice> |
| 28 |
menu, from the &kpilot; daemon popup menu |
| 29 |
<menuchoice> |
| 30 |
<guimenuitem>Configure KPilot...</guimenuitem> |
| 31 |
</menuchoice> |
| 32 |
menu item or by starting &kpilot; |
| 33 |
from the shell |
| 34 |
as follows: |
| 35 |
<screen width="40"><prompt>$ </prompt> <userinput><command>kpilot</command><option>--setup</option></userinput> |
| 36 |
</screen> |
| 37 |
In addition, if you upgrade &kpilot; and some new configuration |
| 38 |
options require your attention, this setup dialog will reappear. |
| 39 |
</para> |
| 40 |
|
| 41 |
<screenshot> |
| 42 |
<screeninfo>Configuration Dialog</screeninfo> |
| 43 |
<mediaobject> |
| 44 |
<imageobject><imagedata fileref="setup-tabs.png" format="PNG"/></imageobject> |
| 45 |
<textobject><phrase>The configuration dialog</phrase></textobject> |
| 46 |
<caption><para>The configuration dialog</para></caption> |
| 47 |
</mediaobject> |
| 48 |
</screenshot> |
| 49 |
|
| 50 |
|
| 51 |
<para> |
| 52 |
&kpilot;'s configuration dialog is a large one. |
| 53 |
This is because it contains not only the configuration of the |
| 54 |
device for communicating with the &PalmPilot;, but also |
| 55 |
the configuration of all the installed conduits. |
| 56 |
Each group of configuration options |
| 57 |
(<link linkend="general-setup">general</link> |
| 58 |
and <link linkend="config-conduits">conduits</link>) |
| 59 |
will be discussed separately. |
| 60 |
We will begin, however, by taking a look at the |
| 61 |
<link linkend="configwizard">configuration wizard</link>, which should make most |
| 62 |
of the |
| 63 |
general group of configuration options superfluous. |
| 64 |
</para> |
| 65 |
|
| 66 |
<sect1 id="configwizard"> |
| 67 |
<title>Using the Wizard</title> |
| 68 |
|
| 69 |
<para> |
| 70 |
The configuration wizard helps you to set up &kpilot; to communicate |
| 71 |
with the &PalmPilot; and to configure the conduits as a group. It's a great |
| 72 |
start for new users, and you can always fine-tune your preferences later. |
| 73 |
</para> |
| 74 |
|
| 75 |
<para> |
| 76 |
In the <guilabel>Pilot Info</guilabel> dialog, type your <guilabel>User |
| 77 |
Name</guilabel>. It |
| 78 |
should match the one from the &PalmPilot;. Next, type the file name of |
| 79 |
the <guilabel>Device</guilabel> you will use to connect the &PalmPilot; (The |
| 80 |
connection can be through a serial port, USB port, infrared, Bluetooth, network |
| 81 |
or the generic <filename class="devicefile">/dev/pilot</filename> device.) |
| 82 |
Alternatively, click the |
| 83 |
<guibutton>Automatically detect handheld and user name...</guibutton> |
| 84 |
button and press the &HotSync; button on your &handheld;. The Wizard will try |
| 85 |
to find the correct <guilabel>Device</guilabel> and |
| 86 |
<guilabel>User Name</guilabel>. |
| 87 |
</para> |
| 88 |
|
| 89 |
<important><para> |
| 90 |
If the |
| 91 |
<guilabel>Device</guilabel> does not have the right permissions, the wizard will |
| 92 |
not be able to find it. Normal users must be able to read/write the correct |
| 93 |
device. To resolve this issue, please refer to <link |
| 94 |
linkend="faq-connection"><quote>&kpilot; says <errorname>Can't connect to |
| 95 |
pilot</errorname></quote> |
| 96 |
&FAQ; entry</link>, or contact your system administrator. |
| 97 |
</para></important> |
| 98 |
|
| 99 |
|
| 100 |
<screenshot> |
| 101 |
<screeninfo>The First Configuring Wizard Dialog</screeninfo> |
| 102 |
<mediaobject> |
| 103 |
<imageobject><imagedata fileref="wizard-general.png" |
| 104 |
format="PNG"/></imageobject> |
| 105 |
<textobject><phrase>Configuring Wizard: The Pilot Info |
| 106 |
Dialog</phrase></textobject> |
| 107 |
<caption><para>Configuring Wizard: The Pilot Info Dialog</para></caption> |
| 108 |
</mediaobject> |
| 109 |
</screenshot> |
| 110 |
|
| 111 |
<para> |
| 112 |
Press the &HotSync; button of your &handheld; to probe for the |
| 113 |
correct <guilabel>Device</guilabel> and <guilabel>User Name</guilabel>. |
| 114 |
</para> |
| 115 |
|
| 116 |
|
| 117 |
<screenshot> |
| 118 |
<screeninfo>The Second Configuring Wizard Dialog</screeninfo> |
| 119 |
<mediaobject> |
| 120 |
<imageobject><imagedata fileref="wizard-connection.png" |
| 121 |
format="PNG"/></imageobject> |
| 122 |
<textobject><phrase>Configuring Wizard: The Autodetection |
| 123 |
Dialog</phrase></textobject> |
| 124 |
<caption><para>Configuring Wizard: The Autodetection Dialog</para></caption> |
| 125 |
</mediaobject> |
| 126 |
</screenshot> |
| 127 |
|
| 128 |
<para> |
| 129 |
&kpilot; has the ability to sync the data on your &handheld; with |
| 130 |
applications or files on your <acronym>PC</acronym>. The programs that |
| 131 |
perform these actions are called conduits. The sync dialog configures |
| 132 |
all applicable &kpilot; conduits to sync with widely used |
| 133 |
<acronym>PIM</acronym> suites. You can fine-tune these settings later, from the |
| 134 |
<menuchoice> |
| 135 |
<guimenu>Settings</guimenu> |
| 136 |
<guimenuitem>Configure &kpilot;</guimenuitem> |
| 137 |
</menuchoice> |
| 138 |
menu. Please check the <link linkend="config-conduits">conduits |
| 139 |
configuration</link> |
| 140 |
section of this document for more information. |
| 141 |
</para> |
| 142 |
|
| 143 |
<screenshot> |
| 144 |
<screeninfo>The Third Configuring Wizard Dialog</screeninfo> |
| 145 |
<mediaobject> |
| 146 |
<imageobject><imagedata fileref="wizard-conduits.png" |
| 147 |
format="PNG"/></imageobject> |
| 148 |
<textobject><phrase>Configuring Wizard: The Sync Dialog</phrase></textobject> |
| 149 |
<caption><para>Configuring Wizard: The Sync Dialog</para></caption> |
| 150 |
</mediaobject> |
| 151 |
</screenshot> |
| 152 |
|
| 153 |
|
| 154 |
</sect1> |
| 155 |
|
| 156 |
|
| 157 |
<sect1 id="general-setup"> |
| 158 |
<title>General Setup</title> |
| 159 |
|
| 160 |
<para> |
| 161 |
The settings available in the &kpilot; configuration dialog |
| 162 |
under the heading <guilabel>General Setup</guilabel> |
| 163 |
give you detailed control over the operation of &kpilot;: |
| 164 |
you can select a non-standard hardware device, |
| 165 |
set special encodings for foreign-language &handheld;s, |
| 166 |
and control how &kpilot; displays your data. There |
| 167 |
are five items under the <guilabel>General Setup</guilabel> |
| 168 |
heading. You may need to expand the <guilabel>General Setup</guilabel> |
| 169 |
heading to see them. |
| 170 |
</para> |
| 171 |
|
| 172 |
<screenshot> |
| 173 |
<screeninfo>Items under General Setup</screeninfo> |
| 174 |
<mediaobject> |
| 175 |
<imageobject><imagedata fileref="setup-items.png" format="PNG"/></imageobject> |
| 176 |
<textobject><phrase>The items under General Setup</phrase></textobject> |
| 177 |
<caption><para>The items under General Setup</para></caption> |
| 178 |
</mediaobject> |
| 179 |
</screenshot> |
| 180 |
|
| 181 |
|
| 182 |
<sect2 id="page-general"> |
| 183 |
<title>Device Setup</title> |
| 184 |
|
| 185 |
<para> |
| 186 |
This is a setup page that contains options describing |
| 187 |
the &PalmPilot; hardware, you, the user |
| 188 |
and how you want the various parts of &kpilot; |
| 189 |
to be started. |
| 190 |
</para> |
| 191 |
|
| 192 |
<screenshot> |
| 193 |
<screeninfo>Device Page</screeninfo> |
| 194 |
<mediaobject> |
| 195 |
<imageobject><imagedata fileref="setup-general.png" format="PNG"/></imageobject> |
| 196 |
<textobject><phrase>The Device Page</phrase></textobject> |
| 197 |
<caption><para>The Device Page</para></caption> |
| 198 |
</mediaobject> |
| 199 |
</screenshot> |
| 200 |
|
| 201 |
|
| 202 |
<variablelist> |
| 203 |
<varlistentry> |
| 204 |
<term><guilabel>Pilot device</guilabel></term> |
| 205 |
<listitem> |
| 206 |
<para> |
| 207 |
The port that the cradle is connected to. |
| 208 |
By default it is |
| 209 |
set to <filename class="devicefile">/dev/pilot</filename> |
| 210 |
which should be a symbolic link to the real port. |
| 211 |
The port might be a serial port, in which case |
| 212 |
<filename class="devicefile">/dev/pilot</filename> |
| 213 |
should point to |
| 214 |
something like |
| 215 |
<filename class="devicefile">/dev/cuaa0</filename> |
| 216 |
(in &FreeBSD;) or |
| 217 |
<filename class="devicefile">/dev/ttyS0</filename> |
| 218 |
(in &Linux;). |
| 219 |
For &USB; devices, it can be more difficult to |
| 220 |
determine where |
| 221 |
<filename class="devicefile">/dev/pilot</filename> |
| 222 |
should point. |
| 223 |
It may be possible to configure your &USB; daemon |
| 224 |
to set up the link automatically, so that |
| 225 |
<filename class="devicefile">/dev/pilot</filename> |
| 226 |
points to the right port no matter where you plug in your &PalmOS; device. |
| 227 |
</para> |
| 228 |
|
| 229 |
<para> |
| 230 |
<emphasis>Make sure the port has |
| 231 |
the correct permissions.</emphasis> |
| 232 |
It |
| 233 |
must be read/write by all if &kpilot; is intended to be used by a |
| 234 |
normal user! &kpilot; will complain if the permissions are wrong, but you |
| 235 |
will need to fix the permissions by hand. This could be done by doing a |
| 236 |
<userinput><command>chmod</command> <parameter>666</parameter> |
| 237 |
<replaceable>device</replaceable></userinput> |
| 238 |
as root where <replaceable>device</replaceable> is the correct port. |
| 239 |
|
| 240 |
To resolve this issue, please refer to <link |
| 241 |
linkend="faq-connection"><quote>&kpilot; says <errorname>Can't connect to pilot |
| 242 |
</errorname></quote> |
| 243 |
&FAQ; entry</link>, or contact your system administrator. |
| 244 |
</para> |
| 245 |
|
| 246 |
|
| 247 |
<para> |
| 248 |
You can also use network sync (with pilot-link 0.11.5 and later) |
| 249 |
by entering <userinput>net:any</userinput> as the |
| 250 |
device name. |
| 251 |
</para> |
| 252 |
|
| 253 |
</listitem> |
| 254 |
</varlistentry> |
| 255 |
|
| 256 |
<varlistentry> |
| 257 |
<term><guilabel>Speed</guilabel></term> |
| 258 |
<listitem> |
| 259 |
<para> |
| 260 |
Indicate the speed of the <emphasis>serial</emphasis> |
| 261 |
connection to the &PalmPilot;. |
| 262 |
It has no meaning for &USB; devices. |
| 263 |
For an older model &PalmPilot;, choose 9600. |
| 264 |
Newer models may be able to handle speeds up to |
| 265 |
the maximum listed, 115200. |
| 266 |
You can experiment with the connection speed: the &PalmPilot; |
| 267 |
manual suggests starting at a speed of 19200 and trying faster |
| 268 |
speeds to see if they work. |
| 269 |
</para> |
| 270 |
</listitem> |
| 271 |
</varlistentry> |
| 272 |
|
| 273 |
<varlistentry><term><guilabel>Encoding</guilabel></term> |
| 274 |
<listitem> |
| 275 |
<para> |
| 276 |
&PalmOS; devices are available in |
| 277 |
many different languages. |
| 278 |
If your device uses a different encoding than |
| 279 |
ISO-latin1, you will need to select the |
| 280 |
correct encoding from the list in order to |
| 281 |
display special characters correctly. |
| 282 |
If you can enter Russian in your &PalmPilot;, |
| 283 |
select CP1251, for instance. |
| 284 |
</para> |
| 285 |
</listitem> |
| 286 |
</varlistentry> |
| 287 |
|
| 288 |
<varlistentry> |
| 289 |
<term><guilabel>Pilot user</guilabel></term> |
| 290 |
<listitem> |
| 291 |
<para> |
| 292 |
The user name of the &PalmPilot;. By default this name is the same as |
| 293 |
your log on name. When you sync with the &PalmPilot; &kpilot; will |
| 294 |
check to see if this name matches the one on the &PalmPilot;. If they do |
| 295 |
not, you are asked to pick which you will use. If you pick the local |
| 296 |
name, the &PalmPilot; will be changed to match. |
| 297 |
The <guilabel>Pilot User</guilabel> entry is also used to name the folder that |
| 298 |
stores the information from the &PalmPilot;. This folder is created in the |
| 299 |
<filename class="directory">$TDEHOME/share/apps/kpilot/DBBackup/</filename> |
| 300 |
folder, where the <filename class="directory">$TDEHOME</filename> environment |
| 301 |
variable |
| 302 |
(typically <filename class="directory">/home/Login Name/.trinity/</filename>) |
| 303 |
points to the folder that contains your configuration and data for the &kde; |
| 304 |
applications. |
| 305 |
</para> |
| 306 |
</listitem> |
| 307 |
</varlistentry> |
| 308 |
|
| 309 |
</variablelist> |
| 310 |
|
| 311 |
</sect2> |
| 312 |
|
| 313 |
<sect2 id="page-hotsync"> |
| 314 |
<title>HotSync Setup</title> |
| 315 |
|
| 316 |
<para> |
| 317 |
This page contains settings with which you can instruct &kpilot; to perform |
| 318 |
special kinds of &HotSync;, as well as direct how conflicts during a &HotSync; |
| 319 |
should be resolved. A conflict happens when both the desktop application and the |
| 320 |
&handheld; application change the same data. |
| 321 |
</para> |
| 322 |
|
| 323 |
<para> |
| 324 |
&kpilot; interfaces with your &handheld; in two ways: using the |
| 325 |
the conduits and the internal viewers. Conduits are plug-in programs which |
| 326 |
extend the synchronization capabilities of &kpilot;. &kpilot; stores separate copies of |
| 327 |
the databases and records for conduits, while the internal viewers and backup |
| 328 |
operation share the same copy. This distinction is important to choose your |
| 329 |
update method depending on your usage. If you use mainly the conduits to sync |
| 330 |
your &handheld; with external programs, you may choose as default |
| 331 |
synchronization method any option that runs the conduits. However, if you use mainly the |
| 332 |
internal viewers, you need to update copy of the databases as well in order to |
| 333 |
view and edit the information from your &handheld;, so running the conduits only |
| 334 |
is not sufficient. |
| 335 |
</para> |
| 336 |
|
| 337 |
<screenshot> |
| 338 |
<screeninfo>The &HotSync; setup page</screeninfo> |
| 339 |
<mediaobject> |
| 340 |
<imageobject> |
| 341 |
<imagedata fileref="setup-hotsync.png" format="PNG"/> |
| 342 |
</imageobject> |
| 343 |
<textobject> |
| 344 |
<phrase>The &HotSync; Page</phrase> |
| 345 |
</textobject> |
| 346 |
<caption> |
| 347 |
<para>The &HotSync; setup page</para></caption> |
| 348 |
</mediaobject> |
| 349 |
</screenshot> |
| 350 |
|
| 351 |
|
| 352 |
<variablelist> |
| 353 |
<varlistentry> |
| 354 |
|
| 355 |
<term><guilabel>Default Sync</guilabel></term> |
| 356 |
|
| 357 |
<listitem> |
| 358 |
<para> |
| 359 |
Select the type of synchronization that will be performed by default. |
| 360 |
</para> |
| 361 |
|
| 362 |
<itemizedlist> |
| 363 |
|
| 364 |
<listitem> |
| 365 |
<para> |
| 366 |
<guilabel>HotSync</guilabel>: run all selected conduits, sync the databases |
| 367 |
with a modified flag set, updating the modified records only. Performs a fast |
| 368 |
backup, backing up only the databases that were modified. This option offers |
| 369 |
a nice balance between speed and data safety. |
| 370 |
</para> |
| 371 |
</listitem> |
| 372 |
|
| 373 |
<listitem> |
| 374 |
<para> |
| 375 |
<guilabel>FastSync</guilabel>: Only synchronize those |
| 376 |
databases that have conduits, and perform no backup of the data |
| 377 |
on the &PalmPilot;, reducing greatly the time required for the sync |
| 378 |
operation. This also means that if something goes wrong with your &PalmPilot;, |
| 379 |
you may not be able to recover the databases. This is a classic |
| 380 |
trade-off between speed and safety. |
| 381 |
</para> |
| 382 |
</listitem> |
| 383 |
|
| 384 |
<listitem> |
| 385 |
<para> |
| 386 |
<guilabel>FullSync</guilabel>: run all selected conduits, and sync all |
| 387 |
databases, reading all records, and performing a full backup. It is the safest |
| 388 |
option, but takes the longest time to complete, as it will merge all the records |
| 389 |
from the &handheld; and your desktop. It is the &kpilot; equivalent of the Palm |
| 390 |
SlowSync. |
| 391 |
</para> |
| 392 |
</listitem> |
| 393 |
|
| 394 |
<listitem> |
| 395 |
<para> |
| 396 |
<guilabel>Copy PC to handheld</guilabel>: run all conduits and sync all |
| 397 |
databases, but instead of merging the information from both sources, copy the PC |
| 398 |
data to the handheld. <emphasis>Use with care, as this option erases the changes |
| 399 |
you made in your handheld since the last sync</emphasis>. |
| 400 |
</para> |
| 401 |
</listitem> |
| 402 |
|
| 403 |
<listitem> |
| 404 |
<para> |
| 405 |
<guilabel>Copy handheld to PC</guilabel>: run all conduits and sync all |
| 406 |
databases, but instead of merging the information from both sources, copy the |
| 407 |
handheld data to the PC. <emphasis>Use with care, as this option erases the |
| 408 |
changes you made in your PC since the last sync</emphasis>. |
| 409 |
</para> |
| 410 |
<warning> |
| 411 |
<para> |
| 412 |
Remember, when &kpilot; does a &HotSync; and runs the conduits, |
| 413 |
the databases in the internal viewers are <emphasis>not</emphasis> |
| 414 |
updated. To update the internal viewers, use the FullSync or backup actions. |
| 415 |
</para> |
| 416 |
</warning> |
| 417 |
|
| 418 |
</listitem> |
| 419 |
|
| 420 |
</itemizedlist> |
| 421 |
|
| 422 |
</listitem> |
| 423 |
</varlistentry> |
| 424 |
|
| 425 |
|
| 426 |
<varlistentry> |
| 427 |
<term><guilabel>Do full backup when changing PCs</guilabel></term> |
| 428 |
<listitem> |
| 429 |
<para> |
| 430 |
If you &HotSync; your &handheld; with multiple <acronym>PC</acronym>s, the flag |
| 431 |
on the &handheld; that stores which |
| 432 |
records have changed since the last &HotSync; may be inaccurate. It is |
| 433 |
recommended to do a full sync when changing <acronym>PC</acronym>s. You can |
| 434 |
disable the full sync by unchecking this box. |
| 435 |
</para> |
| 436 |
</listitem> |
| 437 |
</varlistentry> |
| 438 |
<!-- |
| 439 |
<varlistentry> |
| 440 |
<term><guilabel>Do not sync when screen saver is active</guilabel></term> |
| 441 |
<listitem> |
| 442 |
<para> |
| 443 |
This is a security feature that prevents the &handheld; from synchronization |
| 444 |
while the PC screen saver is active. This prevents other people from |
| 445 |
stealing your data through the &handheld; cradle while your PC is |
| 446 |
unattended. The feature only works with the &kde; screen savers, though, |
| 447 |
and you will need to disable it to use &kpilot; in non-&kde; environments. |
| 448 |
</para> |
| 449 |
</listitem> |
| 450 |
</varlistentry> |
| 451 |
--> |
| 452 |
<varlistentry> |
| 453 |
<term><guilabel>Conflict Resolution</guilabel></term> |
| 454 |
<listitem> |
| 455 |
<para> |
| 456 |
Data records can be changed both on the &handheld; and |
| 457 |
on the <acronym>PC</acronym>. If one record has incompatible changes |
| 458 |
in both the &handheld; and the <acronym>PC</acronym>, (such as |
| 459 |
changing a phone number in different ways on both sides), |
| 460 |
the conflicting change needs to be resolved so |
| 461 |
that the &handheld; and the <acronym>PC</acronym> data are consistent again. |
| 462 |
Choices for conflict resolution are: |
| 463 |
</para> |
| 464 |
<itemizedlist> |
| 465 |
<listitem><para><guilabel>Ask User</guilabel>: |
| 466 |
pop up a dialog for the user to |
| 467 |
choose how the conflict is to be resolved for |
| 468 |
every conflict. |
| 469 |
</para></listitem> |
| 470 |
<listitem><para><guilabel>Do Nothing</guilabel>: |
| 471 |
leave the entries in an inconsistent state. |
| 472 |
Future syncs may not notice the discrepancy. |
| 473 |
</para></listitem> |
| 474 |
<listitem><para><guilabel>Handheld Overrides</guilabel>: |
| 475 |
copy the values from the &handheld; to the <acronym>PC</acronym>, |
| 476 |
discarding the changes on the <acronym>PC</acronym>. |
| 477 |
</para></listitem> |
| 478 |
<listitem><para><guilabel>PC Overrides</guilabel>: |
| 479 |
copy the values from the <acronym>PC</acronym> to the &handheld;, |
| 480 |
discarding changes on the &handheld;. |
| 481 |
</para></listitem> |
| 482 |
<listitem><para><guilabel>Values From Last Sync (if possible)</guilabel>: |
| 483 |
&kpilot; stores a backup copy of the information on your &handheld; depending on |
| 484 |
the synchronization method you selected. If this information is available, use |
| 485 |
neither |
| 486 |
the values from the &handheld; nor the PC, but the values from |
| 487 |
the last sync. |
| 488 |
</para></listitem> |
| 489 |
<listitem><para><guilabel>Use Both Entries</guilabel>: |
| 490 |
Create duplicate entries of the conflicting records on both the |
| 491 |
<acronym>PC</acronym> and |
| 492 |
&handheld;, one with the value from the <acronym>PC</acronym>, the other with |
| 493 |
the value |
| 494 |
from the &handheld;. |
| 495 |
</para></listitem> |
| 496 |
</itemizedlist> |
| 497 |
</listitem> |
| 498 |
</varlistentry> |
| 499 |
|
| 500 |
</variablelist> |
| 501 |
|
| 502 |
</sect2> |
| 503 |
|
| 504 |
|
| 505 |
<sect2 id="page-backup"> |
| 506 |
<title>Backup Setup</title> |
| 507 |
|
| 508 |
<para> |
| 509 |
This page contains settings specific to the backup operation, which saves |
| 510 |
a copy of the the &handheld; databases, allowing the user to |
| 511 |
restore this information later. |
| 512 |
</para> |
| 513 |
|
| 514 |
<para>In short, databases are all files stored in your &handheld;. A database |
| 515 |
can be either a record database, which stores dynamic information created by the |
| 516 |
user (for instance, the addresses or the todo information), or a resource |
| 517 |
database, which tend to be static (for instance the applications).</para> |
| 518 |
|
| 519 |
<screenshot> |
| 520 |
<screeninfo>Backup Page</screeninfo> |
| 521 |
<mediaobject> |
| 522 |
<imageobject> |
| 523 |
<imagedata fileref="setup-dbspecial.png" format="PNG"/> |
| 524 |
</imageobject> |
| 525 |
<textobject><phrase>The Backup Page</phrase></textobject> |
| 526 |
<caption><para>The Backup Page</para></caption> |
| 527 |
</mediaobject> |
| 528 |
</screenshot> |
| 529 |
|
| 530 |
<variablelist> |
| 531 |
<varlistentry> |
| 532 |
<term><guilabel>Databases</guilabel></term> |
| 533 |
<listitem> |
| 534 |
<para> |
| 535 |
List databases that should not be synced or backed up. |
| 536 |
</para> |
| 537 |
|
| 538 |
<para> |
| 539 |
The values can be either database creator values, which are 4-letter strings |
| 540 |
surrounded by square brackets (so for Handbase databases you fill in |
| 541 |
<userinput>[PmDB]</userinput>), or database names, |
| 542 |
which are strings without square brackets that may contain shell-style |
| 543 |
wildcards. |
| 544 |
See the <link linkend="dbskip">FAQ</link> |
| 545 |
for a list of databases that should be listed |
| 546 |
here (the default should be OK though). |
| 547 |
Newer &PalmPilot; devices contain emulation code for |
| 548 |
the older 68k processor; this means that they have a large |
| 549 |
number of databases with names ending in |
| 550 |
<literal role="extension">_a68k</literal>. |
| 551 |
These do not need to be backed up nor synced, so you could |
| 552 |
add <userinput>*_a68k</userinput> |
| 553 |
to the list of databases to skip. |
| 554 |
|
| 555 |
<itemizedlist> |
| 556 |
<listitem><para> |
| 557 |
<guilabel>No backup</guilabel> List here databases that should be excluded from |
| 558 |
the backup operation. Some databases do not follow the standard database layout, |
| 559 |
and trying to backup and restore them will result in information loss. You may |
| 560 |
include here databases with volatile information, such as news or web pages, |
| 561 |
that |
| 562 |
often do not require to be backed up. |
| 563 |
</para> |
| 564 |
</listitem> |
| 565 |
|
| 566 |
<listitem><para> |
| 567 |
<guilabel>Not restored</guilabel> List here databases that should be excluded |
| 568 |
from the restore operation, even if they were previously backed up. Databases |
| 569 |
included here can be installed manually later, using the |
| 570 |
<guilabel>File Installer</guilabel>. You may |
| 571 |
include here databases with volatile information, such as news or web pages, |
| 572 |
that |
| 573 |
often do not require to be restored. |
| 574 |
</para></listitem> |
| 575 |
</itemizedlist> |
| 576 |
|
| 577 |
<warning> |
| 578 |
<para> |
| 579 |
Changing the contents of the <guilabel>No backup</guilabel> |
| 580 |
or <guilabel>Not restored</guilabel> fields, in particular removing |
| 581 |
the databases already listed there, can damage those databases |
| 582 |
when you perform a &HotSync;. |
| 583 |
</para> |
| 584 |
</warning> |
| 585 |
|
| 586 |
</para></listitem> |
| 587 |
</varlistentry> |
| 588 |
|
| 589 |
<varlistentry> |
| 590 |
<term><guilabel>Run conduits during a backup</guilabel></term> |
| 591 |
<listitem> |
| 592 |
<para> |
| 593 |
The backup typically updates the copy of the &handheld; databases. |
| 594 |
Conduits are programs that extend the &kpilot; functionality. Running them |
| 595 |
usually means synchronization the &handheld; to other <acronym>PC</acronym> |
| 596 |
databases, |
| 597 |
like the address book or the calender. Check this box to perform both operations |
| 598 |
on |
| 599 |
every backup. |
| 600 |
</para> |
| 601 |
</listitem> |
| 602 |
</varlistentry> |
| 603 |
|
| 604 |
|
| 605 |
</variablelist> |
| 606 |
|
| 607 |
</sect2> |
| 608 |
|
| 609 |
|
| 610 |
<sect2 id="page-viewers"> |
| 611 |
<title>Internal Viewers Setup</title> |
| 612 |
<para> |
| 613 |
&kpilot; contains <quote>viewers</quote> for |
| 614 |
presenting information from the &PalmPilot;. |
| 615 |
These viewers present the databases available on |
| 616 |
the &PalmPilot; in much the same way that the device |
| 617 |
itself does. Not all databases have an application-specific |
| 618 |
viewer, though you can use the generic database viewer for those. |
| 619 |
The viewers page contains settings for the internal viewers in |
| 620 |
&kpilot;. |
| 621 |
These settings change the way in which the data is shown. |
| 622 |
</para> |
| 623 |
|
| 624 |
<screenshot> |
| 625 |
<screeninfo>Viewers Page</screeninfo> |
| 626 |
<mediaobject> |
| 627 |
<imageobject><imagedata fileref="setup-viewer.png" format="PNG"/></imageobject> |
| 628 |
<textobject><phrase>The Viewers Setup Page</phrase></textobject> |
| 629 |
<caption><para>The Viewers Setup Page</para></caption> |
| 630 |
</mediaobject> |
| 631 |
</screenshot> |
| 632 |
|
| 633 |
<variablelist> |
| 634 |
<varlistentry> |
| 635 |
<term><guilabel>Make internal viewers editable</guilabel></term> |
| 636 |
<listitem><para> |
| 637 |
The internal viewers can be read only or editable. The editable mode allows you |
| 638 |
to add new records, delete or edit the existing records and sync your |
| 639 |
modifications back to the &handheld;. Check |
| 640 |
this box to set the internal viewers to editable mode, uncheck to set them to |
| 641 |
read |
| 642 |
only mode.</para> |
| 643 |
<warning><para> |
| 644 |
On some &kpilot; versions, it is not possible check this box, and therefore to |
| 645 |
use the internal viewers as editors. |
| 646 |
</para></warning> |
| 647 |
</listitem> |
| 648 |
</varlistentry> |
| 649 |
|
| 650 |
<varlistentry> |
| 651 |
<term><guilabel>Show private records</guilabel></term> |
| 652 |
<listitem><para> |
| 653 |
In your &PalmPilot; you can mark some records as <quote>private</quote>. By |
| 654 |
default, &kpilot; does not display these records on the screen. Check this box |
| 655 |
if you want to see them. |
| 656 |
</para></listitem> |
| 657 |
</varlistentry> |
| 658 |
|
| 659 |
<varlistentry> |
| 660 |
<term><guilabel>Address Viewer</guilabel></term> |
| 661 |
<listitem><para> |
| 662 |
Set there the options for the address internal viewer. |
| 663 |
|
| 664 |
<itemizedlist> |
| 665 |
<listitem><para> |
| 666 |
<guilabel>Show as "Last, first"</guilabel> or |
| 667 |
<guilabel>Show as "Company, last"</guilabel>: the order and display of the |
| 668 |
address records in the address internal viewer can be set to match the |
| 669 |
&handheld;. Select the option that suits better your personal preferences. |
| 670 |
</para></listitem> |
| 671 |
|
| 672 |
<listitem><para> |
| 673 |
<guilabel>Use key field</guilabel> Check this box to combine entries with the |
| 674 |
same last name. |
| 675 |
</para></listitem> |
| 676 |
|
| 677 |
</itemizedlist> |
| 678 |
|
| 679 |
</para></listitem> |
| 680 |
</varlistentry> |
| 681 |
|
| 682 |
|
| 683 |
</variablelist> |
| 684 |
|
| 685 |
</sect2> |
| 686 |
|
| 687 |
|
| 688 |
|
| 689 |
<sect2 id="page-startup-exit"> |
| 690 |
<title>Startup and Exit Behavior Setup</title> |
| 691 |
|
| 692 |
<para> |
| 693 |
This pages present options related to the startup and exit of &kpilot; and |
| 694 |
&kpilot; daemon. |
| 695 |
</para> |
| 696 |
|
| 697 |
<para> |
| 698 |
While &kpilot; is the front-end for the internal viewers, configuration options |
| 699 |
and logs, the sync operation is handled by the &kpilot; daemon. Even if &kpilot; |
| 700 |
is not running you can &HotSync; if the daemon is. Therefore, if you want to |
| 701 |
be able to sync your &handheld; at anytime, it is important to start the daemon |
| 702 |
at login, or the opposite, if you want to be able to sync only when &kpilot; is |
| 703 |
running, you have to stop the daemon on exit. The last option is especially |
| 704 |
usefull if you have other applications that use the same port as &kpilot;. |
| 705 |
</para> |
| 706 |
|
| 707 |
|
| 708 |
<screenshot> |
| 709 |
<screeninfo>Startup and Exit Page</screeninfo> |
| 710 |
<mediaobject> |
| 711 |
<imageobject><imagedata fileref="setup-startup-exit.png" |
| 712 |
format="PNG"/></imageobject> |
| 713 |
<textobject><phrase>The Startup and Exit Page</phrase></textobject> |
| 714 |
<caption><para>The Startup and Exit Page</para></caption> |
| 715 |
</mediaobject> |
| 716 |
</screenshot> |
| 717 |
|
| 718 |
|
| 719 |
<variablelist> |
| 720 |
|
| 721 |
<varlistentry> |
| 722 |
<term><guilabel>Startup Options</guilabel></term> |
| 723 |
|
| 724 |
<listitem> |
| 725 |
<para> |
| 726 |
|
| 727 |
<itemizedlist> |
| 728 |
<listitem> |
| 729 |
<para> |
| 730 |
<guilabel>Start daemon at login</guilabel>: |
| 731 |
By checking this, a link to |
| 732 |
the daemon is placed in your autostart folder |
| 733 |
and will be started automatically. Note that this is not normally |
| 734 |
needed if the daemon is docked in the panel. |
| 735 |
<!-- TODO: broken functionality --> |
| 736 |
</para> |
| 737 |
</listitem> |
| 738 |
|
| 739 |
<listitem> |
| 740 |
<para> |
| 741 |
<guilabel>Show daemon in panel</guilabel>: |
| 742 |
Check this box to instruct the daemon to place a &kpilot; icon |
| 743 |
<guiicon> |
| 744 |
<inlinemediaobject> |
| 745 |
<imageobject><imagedata fileref="kpilot.png" format="PNG"/> |
| 746 |
</imageobject> |
| 747 |
</inlinemediaobject> |
| 748 |
</guiicon> |
| 749 |
in the system tray. This icon has a menu that can be brought up with |
| 750 |
the right mouse button. Without this option, the daemon is not visible to the |
| 751 |
user at all. |
| 752 |
</para> |
| 753 |
</listitem> |
| 754 |
</itemizedlist> |
| 755 |
|
| 756 |
</para> |
| 757 |
</listitem> |
| 758 |
|
| 759 |
</varlistentry> |
| 760 |
|
| 761 |
<varlistentry> |
| 762 |
|
| 763 |
<term> |
| 764 |
<guilabel>Exit Options</guilabel> |
| 765 |
</term> |
| 766 |
|
| 767 |
<listitem> |
| 768 |
<para> |
| 769 |
|
| 770 |
<itemizedlist> |
| 771 |
<listitem> |
| 772 |
<para> |
| 773 |
<guilabel>Quit after HotSync</guilabel>: When this option is enabled, both |
| 774 |
&kpilot; and the &kpilot; daemon will exit after the &HotSync; operation has |
| 775 |
completed, leaving the device port free for other tools. This may be needed on |
| 776 |
systems where the &USB; daemon starts &kpilot; automatically. |
| 777 |
</para> |
| 778 |
</listitem> |
| 779 |
|
| 780 |
<listitem> |
| 781 |
<para> |
| 782 |
<anchor id="stopdaemononexit"/> |
| 783 |
<guilabel>Stop daemon on exit</guilabel>: Setting this option will cause the |
| 784 |
daemon to exit when you quit &kpilot;, leaving the device port free for other |
| 785 |
&PalmPilot;-synchronization tools such as <application>malsync</application> |
| 786 |
</para> |
| 787 |
</listitem> |
| 788 |
</itemizedlist> |
| 789 |
</para> |
| 790 |
</listitem> |
| 791 |
</varlistentry> |
| 792 |
|
| 793 |
</variablelist> |
| 794 |
|
| 795 |
</sect2> |
| 796 |
</sect1> |
| 797 |
|
| 798 |
<sect1 id="config-conduits"> |
| 799 |
<title>Conduits Setup</title> |
| 800 |
|
| 801 |
<para> |
| 802 |
Conduits are programs that interface your &handheld; data with |
| 803 |
<acronym>PC</acronym> applications or sync your &handheld; data with files |
| 804 |
that can be used by <acronym>PC</acronym> applications. They can be |
| 805 |
written by third parties, to interface your &PalmPilot; to any application |
| 806 |
imaginable. |
| 807 |
</para> |
| 808 |
|
| 809 |
<para> |
| 810 |
&kpilot;'s configuration dialog allows you to select which conduits |
| 811 |
to run during a &HotSync; and to configure those conduits. |
| 812 |
A window similar to the following will be displayed: |
| 813 |
</para> |
| 814 |
<screenshot> |
| 815 |
<screeninfo>The Conduit Setup Dialog</screeninfo> |
| 816 |
<mediaobject> |
| 817 |
<imageobject><imagedata fileref="setup-conduit.png" format="PNG"/></imageobject> |
| 818 |
<textobject> |
| 819 |
<phrase>The Conduit Setup Dialog</phrase> |
| 820 |
</textobject> |
| 821 |
<caption> |
| 822 |
<para>The Conduit Setup Dialog</para> |
| 823 |
</caption> |
| 824 |
</mediaobject> |
| 825 |
</screenshot> |
| 826 |
<para> |
| 827 |
Check the box to the left of the conduit name to make it active, uncheck to make |
| 828 |
it inactive or click on the conduit name to configure it. |
| 829 |
</para> |
| 830 |
|
| 831 |
<variablelist> |
| 832 |
|
| 833 |
<varlistentry> |
| 834 |
<term><guilabel>KNotes / Memos</guilabel></term> |
| 835 |
<listitem> |
| 836 |
<para> |
| 837 |
Synchronizes the Memo Pad application with &knotes;. |
| 838 |
</para> |
| 839 |
</listitem> |
| 840 |
</varlistentry> |
| 841 |
|
| 842 |
<varlistentry> |
| 843 |
<term><guilabel>Notepad</guilabel></term> |
| 844 |
<listitem> |
| 845 |
<para> |
| 846 |
Exports the free hand notes of the &handheld;'s Notepad application as pictures |
| 847 |
to the PC. |
| 848 |
</para> |
| 849 |
</listitem> |
| 850 |
</varlistentry> |
| 851 |
|
| 852 |
|
| 853 |
<varlistentry> |
| 854 |
<term><guilabel>Time Synchronization</guilabel></term> |
| 855 |
<listitem> |
| 856 |
<para> |
| 857 |
Sets the &handheld;'s time to that of the desktop machine. |
| 858 |
Useful for keeping the clock of the &handheld; accurate. |
| 859 |
</para> |
| 860 |
</listitem> |
| 861 |
</varlistentry> |
| 862 |
|
| 863 |
<varlistentry> |
| 864 |
<term><guilabel>Calendar (KOrganizer)</guilabel></term> |
| 865 |
<listitem> |
| 866 |
<para> |
| 867 |
Synchronizes the Datebook application with &korganizer; or with an |
| 868 |
iCalendar file of |
| 869 |
your choice. |
| 870 |
</para> |
| 871 |
</listitem> |
| 872 |
</varlistentry> |
| 873 |
|
| 874 |
<varlistentry> |
| 875 |
<term><guilabel>Palm DOC</guilabel></term> |
| 876 |
<listitem> |
| 877 |
<para> |
| 878 |
Automatically converts and installs text files in the &PalmPilot; |
| 879 |
DOC format, so you can read the text files with most DOC-capable |
| 880 |
applications on the &handheld;. |
| 881 |
</para> |
| 882 |
</listitem> |
| 883 |
</varlistentry> |
| 884 |
|
| 885 |
<varlistentry> |
| 886 |
<term><guilabel>Addressbook</guilabel></term> |
| 887 |
<listitem> |
| 888 |
<para> |
| 889 |
Synchronizes the Address application with &kaddressbook; or with a vCard file of |
| 890 |
your choice. |
| 891 |
</para> |
| 892 |
</listitem> |
| 893 |
</varlistentry> |
| 894 |
|
| 895 |
<varlistentry> |
| 896 |
<term><guilabel>System Information</guilabel></term> |
| 897 |
<listitem> |
| 898 |
<para> |
| 899 |
Writes information about your &handheld;, (such as OS version, |
| 900 |
RAM available, and the list of databases) to a file. Useful mostly for |
| 901 |
debugging purposes. |
| 902 |
</para> |
| 903 |
</listitem> |
| 904 |
</varlistentry> |
| 905 |
|
| 906 |
<varlistentry> |
| 907 |
<term><guilabel>ToDo's (KOrganizer)</guilabel></term> |
| 908 |
<listitem> |
| 909 |
<para> |
| 910 |
Synchronizes the Todo list application with &korganizer; or with a iCalendar |
| 911 |
file of |
| 912 |
your choice. |
| 913 |
</para> |
| 914 |
</listitem> |
| 915 |
</varlistentry> |
| 916 |
|
| 917 |
<varlistentry> |
| 918 |
<term><guilabel>MAL (AvantGo) Conduit</guilabel></term> |
| 919 |
<listitem> |
| 920 |
<para> |
| 921 |
Synchronizes your &handheld; with the &AvantGo; server. The &AvantGo; server |
| 922 |
offers general content (news, guides, stock quotes, &etc;) in a format that is |
| 923 |
suitable for reading in a &handheld;. To use this conduit, you need to register, |
| 924 |
subscribe |
| 925 |
the channels you select and install the &AvantGo; software on your &handheld;. |
| 926 |
</para></listitem> |
| 927 |
</varlistentry> |
| 928 |
|
| 929 |
<varlistentry> |
| 930 |
<term><guilabel>Mail</guilabel></term> |
| 931 |
<listitem> |
| 932 |
<para> |
| 933 |
Sends mail written on the &handheld; through &kmail;. |
| 934 |
There is no provision for receiving mail, however. |
| 935 |
</para> |
| 936 |
</listitem> |
| 937 |
</varlistentry> |
| 938 |
|
| 939 |
</variablelist> |
| 940 |
|
| 941 |
|
| 942 |
<sect2 id="conduit-knotes"> |
| 943 |
<title>&knotes; Conduit Setup</title> |
| 944 |
|
| 945 |
<para> |
| 946 |
The &knotes; Conduit is a partial replacement for the built-in <link |
| 947 |
linkend="builtin">memo application</link>. It keeps the notes you write |
| 948 |
with &knotes; synchronized with the memos you write on your &PalmPilot;. |
| 949 |
</para> |
| 950 |
|
| 951 |
<para> |
| 952 |
Setting up the &knotes; conduit is very simple. |
| 953 |
</para> |
| 954 |
|
| 955 |
<screenshot> |
| 956 |
<screeninfo>&knotes; Conduit Setup</screeninfo> |
| 957 |
<mediaobject> |
| 958 |
<imageobject> |
| 959 |
<imagedata fileref="conduit-knotes.png" format="PNG"/> |
| 960 |
</imageobject> |
| 961 |
<textobject> |
| 962 |
<phrase>&knotes; Conduit Setup</phrase> |
| 963 |
</textobject> |
| 964 |
<caption> |
| 965 |
<para>&knotes; Conduit Setup</para> |
| 966 |
</caption> |
| 967 |
</mediaobject> |
| 968 |
</screenshot> |
| 969 |
|
| 970 |
<para> |
| 971 |
In the <guilabel>General</guilabel> Tab there are two configuration options: |
| 972 |
|
| 973 |
<variablelist> |
| 974 |
|
| 975 |
<varlistentry> |
| 976 |
<term><guilabel>Delete KNote when Pilot memo is deleted</guilabel></term> |
| 977 |
<listitem> |
| 978 |
<para> |
| 979 |
Uncheck this box if you wish to maintain the note on &knotes; even if the |
| 980 |
correspondent memo was deleted on the &handheld; memo application. |
| 981 |
</para> |
| 982 |
</listitem> |
| 983 |
</varlistentry> |
| 984 |
|
| 985 |
<varlistentry> |
| 986 |
<term><guilabel>Suppress delete-confirmation in KNotes</guilabel></term> |
| 987 |
<listitem> |
| 988 |
<para> |
| 989 |
If the <guilabel>Delete KNote when Pilot memo is deleted</guilabel> box is |
| 990 |
checked, you may check this box to automatically delete the notes that |
| 991 |
correspond to a deleted memo, without confirmation. |
| 992 |
</para> |
| 993 |
</listitem> |
| 994 |
</varlistentry> |
| 995 |
|
| 996 |
</variablelist> |
| 997 |
|
| 998 |
<note> |
| 999 |
<para> |
| 1000 |
By default, the options <quote>delete knote</quote> and <quote>suppress |
| 1001 |
delete-confirmation</quote> are turned <emphasis>off</emphasis>, so that notes |
| 1002 |
will accumulate on your PC. |
| 1003 |
</para> |
| 1004 |
</note> |
| 1005 |
|
| 1006 |
</para> |
| 1007 |
</sect2> |
| 1008 |
|
| 1009 |
<sect2 id="notepad-cond"> |
| 1010 |
<title>Notepad Conduit Setup</title> |
| 1011 |
|
| 1012 |
<para> |
| 1013 |
The Notepad Conduit exports the free hand notes of the &handheld;'s Notepad |
| 1014 |
application as pictures to the desktop. To set the folder to which the pictures |
| 1015 |
should be exported, either enter it in the <guilabel>Output</guilabel> edit |
| 1016 |
box or select it clicking the file picker button. |
| 1017 |
</para> |
| 1018 |
|
| 1019 |
</sect2> |
| 1020 |
|
| 1021 |
<sect2 id="time-cond"> |
| 1022 |
<title>Time Synchronization Conduit Setup</title> |
| 1023 |
|
| 1024 |
<para> |
| 1025 |
The Time Synchronization Conduit syncs the &handheld;'s time to that of the |
| 1026 |
desktop |
| 1027 |
machine. It is useful for keeping the clock of the &handheld; accurate. There |
| 1028 |
are really no configuration options other that enabling and disabling the |
| 1029 |
conduit, as currently only one direction for the synchronization is enabled, |
| 1030 |
you can only <guilabel>Set the handheld time from the time on the PC</guilabel>, |
| 1031 |
and not <guilabel>Set the PC time from the time on the handheld</guilabel>. |
| 1032 |
</para> |
| 1033 |
|
| 1034 |
|
| 1035 |
<note> |
| 1036 |
<para> |
| 1037 |
&PalmOS; Version 3.25 and 3.3 do not support setting the &handheld; system time. |
| 1038 |
For these systems, the conduit will be simply skipped. |
| 1039 |
</para> |
| 1040 |
</note> |
| 1041 |
|
| 1042 |
</sect2> |
| 1043 |
|
| 1044 |
<sect2 id="vcal-cond"> |
| 1045 |
<title>Calendar Conduit Setup</title> |
| 1046 |
|
| 1047 |
<para> |
| 1048 |
This conduit will synchronize your &PalmPilot; with &korganizer; and &kontact; |
| 1049 |
or to an iCalendar file of your choice. In the latter case, the conduit will |
| 1050 |
need the filename of the calendar file (this will usually be a file that ends in |
| 1051 |
<literal role="extension">.ics</literal>) to sync with, of if it uses the |
| 1052 |
standard &korganizer; iCalendar file, it will be under the <filename |
| 1053 |
class="directory">$TDEHOME/share/apps/korganizer/</filename> folder, where the |
| 1054 |
<filename class="directory">$TDEHOME</filename> environment variable (typically |
| 1055 |
<filename class="directory">/home/user/.trinity/</filename>) points to the folder |
| 1056 |
that contains your configuration and data for the &kde; applications. |
| 1057 |
</para> |
| 1058 |
|
| 1059 |
<screenshot> |
| 1060 |
<screeninfo>The Calendar Conduit Setup Dialog</screeninfo> |
| 1061 |
<mediaobject> |
| 1062 |
<imageobject> |
| 1063 |
<imagedata fileref="conduit-vcal.png" format="PNG"/> |
| 1064 |
</imageobject> |
| 1065 |
<textobject> |
| 1066 |
<phrase>Calendar Conduit Setup</phrase> |
| 1067 |
</textobject> |
| 1068 |
<caption> |
| 1069 |
<para>Calendar Conduit Setup</para> |
| 1070 |
</caption> |
| 1071 |
</mediaobject> |
| 1072 |
</screenshot> |
| 1073 |
|
| 1074 |
<para> |
| 1075 |
In the <guilabel>General</guilabel> page, you can set the calendar options. |
| 1076 |
</para> |
| 1077 |
|
| 1078 |
<variablelist> |
| 1079 |
|
| 1080 |
<varlistentry> |
| 1081 |
<term><guilabel>Calendar Destination</guilabel></term> |
| 1082 |
<listitem> |
| 1083 |
<para> |
| 1084 |
Choose between synchronizing with the <guilabel>Standard Calendar</guilabel>, |
| 1085 |
or in other words, the &korganizer; standard calendar or with a |
| 1086 |
<guilabel>Calendar file</guilabel> of your choice, that you must either |
| 1087 |
write in the <guilabel>Calendar file</guilabel> edit box or select using the |
| 1088 |
file picker. |
| 1089 |
</para> |
| 1090 |
|
| 1091 |
<warning> |
| 1092 |
<para> |
| 1093 |
You can use the calendar conduit with any application that accepts a file in |
| 1094 |
the iCalendar format as a resource. However, some applications, like Evolution, |
| 1095 |
do not handle the synchronization gracefully while they are open. As a rule of |
| 1096 |
thumb, quit these applications before synchronizing, otherwise you will lose |
| 1097 |
data. There is no need to take these precautions when syncing with &korganizer; |
| 1098 |
or &kontact;. |
| 1099 |
</para> |
| 1100 |
</warning> |
| 1101 |
</listitem> |
| 1102 |
</varlistentry> |
| 1103 |
|
| 1104 |
<varlistentry> |
| 1105 |
<term><guilabel>Store archived records in the KDE calendar</guilabel></term> |
| 1106 |
<listitem> |
| 1107 |
<para> |
| 1108 |
Check this box to save a copy of the archived records from your |
| 1109 |
&handheld; on the <acronym>PC</acronym>, in order to keep a history of |
| 1110 |
past appointments in you &kde; desktop as well. |
| 1111 |
</para> |
| 1112 |
</listitem> |
| 1113 |
</varlistentry> |
| 1114 |
|
| 1115 |
</variablelist> |
| 1116 |
|
| 1117 |
<para> |
| 1118 |
In the <guilabel>Conflicts</guilabel> page, you can set the calendar options, |
| 1119 |
overriding &kpilot;'s general settings for conflict resolution when you are |
| 1120 |
using this conduit. For a detailed description of the different conflict |
| 1121 |
resolution possibilities available, please refer to the <link |
| 1122 |
linkend="page-hotsync">HotSync Setup section</link> of this handbook. |
| 1123 |
</para> |
| 1124 |
|
| 1125 |
</sect2> |
| 1126 |
|
| 1127 |
|
| 1128 |
<sect2 id="conduit-palmdoc"> |
| 1129 |
<title>Palm DOC Conduit Setup</title> |
| 1130 |
|
| 1131 |
<para> |
| 1132 |
The Palm DOC conduit converts text files in your <acronym>PC</acronym> from and |
| 1133 |
to |
| 1134 |
databases in Palm DOC format in the &PalmPilot;. You can use any Palm DOC reader |
| 1135 |
to view these files on your &PalmPilot;. |
| 1136 |
</para> |
| 1137 |
|
| 1138 |
<screenshot> |
| 1139 |
<screeninfo>Palm DOC Conduit Setup</screeninfo> |
| 1140 |
<mediaobject> |
| 1141 |
<imageobject><imagedata fileref="conduit-palmdoc.png" |
| 1142 |
format="PNG"/></imageobject> |
| 1143 |
<textobject><phrase>Palm DOC Conduit Setup</phrase></textobject> |
| 1144 |
<caption><para>Palm DOC Conduit Setup</para></caption> |
| 1145 |
</mediaobject> |
| 1146 |
</screenshot> |
| 1147 |
|
| 1148 |
<important><para> |
| 1149 |
After changing the Palm DOC conduit configuration, you have to restart &kpilot; |
| 1150 |
to let the changes you made take effect. |
| 1151 |
</para></important> |
| 1152 |
|
| 1153 |
<para> |
| 1154 |
In the <guilabel>General</guilabel> page, you can set the location of the text |
| 1155 |
documents in your computer and the direction of the synchronization. |
| 1156 |
</para> |
| 1157 |
|
| 1158 |
<variablelist> |
| 1159 |
|
| 1160 |
<varlistentry> |
| 1161 |
<term><guilabel>Text files:</guilabel></term> |
| 1162 |
<listitem><para> |
| 1163 |
Type on the text box or use the file picker to select the location of the folder |
| 1164 |
that the Palm DOC conduit uses a as the place for the text files it will sync |
| 1165 |
with the &handheld;. There, you may place the text documents you want install or |
| 1166 |
synchronize to the <acronym>PDA</acronym>, and find the text documents created |
| 1167 |
from Palm DOC |
| 1168 |
databases in your &handheld;. |
| 1169 |
<important><para> |
| 1170 |
The file name has to end in <literal role="extension">.txt</literal> for the |
| 1171 |
conduit to recognize it as text. If the file is not recognized as text, it will |
| 1172 |
be ignored by the conduit. Also, the text has to be in an encoding that is |
| 1173 |
compatible with your &handheld; encoding. Therefore, if the text file has |
| 1174 |
characters that are not being correctly recognized by the Palm DOC reader in |
| 1175 |
your &handheld;, try opening the file a text editor, like &kwrite;, and saving |
| 1176 |
it in an compatible text encoding using the <guilabel>Save As..</guilabel> |
| 1177 |
dialog, or set the encoding in the <guilabel>PC -> Handheld</guilabel> tab. |
| 1178 |
</para></important> |
| 1179 |
</para> |
| 1180 |
</listitem> |
| 1181 |
</varlistentry> |
| 1182 |
|
| 1183 |
<varlistentry> |
| 1184 |
<term><guilabel>Local copy:</guilabel></term> |
| 1185 |
<listitem><para> |
| 1186 |
If you want to save a copy of the Palm DOC databases from your &handheld; in |
| 1187 |
your computer, check the <guilabel>Local copy:</guilabel> box and |
| 1188 |
type on the text box or use the file picker to select the location of the folder |
| 1189 |
where these databases will be saved. |
| 1190 |
</para></listitem> |
| 1191 |
</varlistentry> |
| 1192 |
|
| 1193 |
<varlistentry> |
| 1194 |
<term><guilabel>Synchronization Mode</guilabel></term> |
| 1195 |
<listitem><para> |
| 1196 |
The Palm DOC conduit has the ability to sync from and to the &handheld;, |
| 1197 |
automatically converting the text files to Palm DOC databases and vice versa. |
| 1198 |
The <guilabel>Sync only PC to PDA</guilabel> option will convert all text files |
| 1199 |
located in the folder you selected above to Palm DOC databases and install them |
| 1200 |
in your &handheld;. |
| 1201 |
The <guilabel>Sync only PDA to PC</guilabel> option will convert all Palm DOC |
| 1202 |
databases from your &handheld; to files and install them in the |
| 1203 |
folder you selected above. Finally, The <guilabel>Sync all</guilabel> option |
| 1204 |
allows the synchronization to work in both directions. |
| 1205 |
|
| 1206 |
<note><para> |
| 1207 |
When both the text file and the Palm DOC database are modified, you cannot merge |
| 1208 |
the modifications, you have to choose one of the versions, losing the changes |
| 1209 |
in one of them. |
| 1210 |
</para></note> |
| 1211 |
</para></listitem> |
| 1212 |
</varlistentry> |
| 1213 |
|
| 1214 |
</variablelist> |
| 1215 |
|
| 1216 |
<para> |
| 1217 |
In the <guilabel>PC -> Handheld</guilabel> page, you can configure the Palm DOC |
| 1218 |
compression and bookmarks settings to use when converting from text files to |
| 1219 |
Palm DOC databases. |
| 1220 |
</para> |
| 1221 |
|
| 1222 |
<variablelist> |
| 1223 |
|
| 1224 |
<varlistentry> |
| 1225 |
<term><guilabel>Compress</guilabel></term> |
| 1226 |
<listitem><para> |
| 1227 |
Palm DOC documents can be compressed, saving considerable amounts |
| 1228 |
of available memory in your &handheld;. Most Palm DOC readers support |
| 1229 |
compressed documents, but if you use a reader or editor that is not compatible |
| 1230 |
with compression (for instance, the Sied editor), you will not be able to read |
| 1231 |
or edit the compressed Palm DOC documents created by this conduit. |
| 1232 |
Therefore, check this box to save &handheld; memory, but uncheck it if you have |
| 1233 |
compatibility problems with compressed Palm DOC in your favorite editor or |
| 1234 |
reader. |
| 1235 |
</para></listitem> |
| 1236 |
</varlistentry> |
| 1237 |
|
| 1238 |
<varlistentry> |
| 1239 |
<term><guilabel>Convert bookmarks</guilabel></term> |
| 1240 |
<listitem><para> |
| 1241 |
The Palm DOC format has a provision for bookmark records. Bookmarks allow you to |
| 1242 |
easily jump to selected parts of the document, making browsing long documents |
| 1243 |
easier. Check this box to allow the Palm DOC conduit to create bookmark records. |
| 1244 |
To create them, the conduit has to know the location in the text and the name of |
| 1245 |
the bookmark. There are three supported ways to let the conduit know the |
| 1246 |
location and name of the bookmark: from inline tags in the text, from tags at |
| 1247 |
the end of the text and from a <literal role="extension">.bmk</literal> bookmark |
| 1248 |
file. To make the creation of bookmarks effective, you have to check at least |
| 1249 |
one of these boxes below. |
| 1250 |
</para></listitem> |
| 1251 |
</varlistentry> |
| 1252 |
|
| 1253 |
<varlistentry> |
| 1254 |
<term><guilabel>Inline tags in text</guilabel></term> |
| 1255 |
<listitem><para> |
| 1256 |
Convert tags in the format <* <replaceable>BookmarkName</replaceable> *> |
| 1257 |
located inside the text to Palm DOC bookmarks, where the location of the |
| 1258 |
tag in the text will be converted to the bookmark location and the |
| 1259 |
<replaceable>BookmarkName</replaceable> text inside the tag will be converted to |
| 1260 |
the name of the bookmark in the Palm DOC format. The tag will be removed from |
| 1261 |
the resulting Palm DOC document, leaving the text clean. |
| 1262 |
This is a very easy and intuitive way to create bookmarks |
| 1263 |
in your Palm DOC documents. |
| 1264 |
</para></listitem> |
| 1265 |
</varlistentry> |
| 1266 |
|
| 1267 |
<varlistentry> |
| 1268 |
<term><guilabel>Tags at end of text</guilabel></term> |
| 1269 |
<listitem><para> |
| 1270 |
Convert tags in the format <<replaceable>BookmarkName</replaceable>> |
| 1271 |
located in the end of the text to Palm DOC bookmarks. Whenever the |
| 1272 |
<replaceable>BookmarkName</replaceable> text appears in the text, the conduit |
| 1273 |
will generate a the bookmark in the resulting Palm DOC document pointing to it. |
| 1274 |
The tag will then be removed from the resulting Palm DOC document, leaving the |
| 1275 |
text clean. This is a simple way to create repetitive bookmarks, like one for |
| 1276 |
each <quote>Chapter</quote> in your Palm DOC documents. |
| 1277 |
</para></listitem> |
| 1278 |
</varlistentry> |
| 1279 |
|
| 1280 |
<varlistentry> |
| 1281 |
<term><guilabel>Regular expressions in .bmk file</guilabel></term> |
| 1282 |
<listitem><para> |
| 1283 |
This is the most complex but the most powerful way to create bookmarks. |
| 1284 |
The method involves using regular expressions (QRegExp) in a file |
| 1285 |
<filename>TextName.bmk</filename>, where <filename>TextName.txt</filename> is |
| 1286 |
the filename of the text, to search the text for bookmarks. See the |
| 1287 |
<ulink |
| 1288 |
url="http://reinhold.kainhofer.com/Linux/KPilot/bmkSpecification.txt"> |
| 1289 |
documentation</ulink> |
| 1290 |
for an in-depth description of the bmk file format. |
| 1291 |
</para></listitem> |
| 1292 |
</varlistentry> |
| 1293 |
|
| 1294 |
<varlistentry> |
| 1295 |
<term><guilabel>Encoding</guilabel></term> |
| 1296 |
<listitem><para> |
| 1297 |
Set here the encoding of your &handheld;. &kpilot; will convert the text |
| 1298 |
document to this encoding when exporting the file to the &handheld;. |
| 1299 |
</para></listitem> |
| 1300 |
</varlistentry> |
| 1301 |
|
| 1302 |
</variablelist> |
| 1303 |
|
| 1304 |
<para> |
| 1305 |
In the <guilabel>Handheld -> PC</guilabel> page, you can configure bookmarks |
| 1306 |
settings to use when converting from Palm DOC databases to text files. |
| 1307 |
</para> |
| 1308 |
|
| 1309 |
<variablelist> |
| 1310 |
|
| 1311 |
<varlistentry> |
| 1312 |
<term><guilabel>Convert Bookmarks</guilabel></term> |
| 1313 |
<listitem> |
| 1314 |
<para> |
| 1315 |
The Palm DOC format has a provision for bookmark records. Bookmarks allow you to |
| 1316 |
easily jump to selected parts of the document, making browsing long documents |
| 1317 |
easier. The Palm DOC conduit can convert Palm DOC |
| 1318 |
bookmark records to a format that is readable in your computer, either as |
| 1319 |
a separate file or as tags in the middle of the text file. Select |
| 1320 |
<guilabel>Do not convert bookmarks</guilabel> if you want to ignore the Palm DOC |
| 1321 |
bookmarks, resulting in a text that is clean from bookmark tags.</para> |
| 1322 |
|
| 1323 |
<para> |
| 1324 |
The <guilabel>Convert into .bm file</guilabel> options also result in a clean |
| 1325 |
text file, as the bookmarks are converted to a separate file in the bmk format, |
| 1326 |
as described <ulink |
| 1327 |
url="http://reinhold.kainhofer.com/Linux/KPilot/bmkSpecification.txt">here</ulink>. The file is saved with a <literal role="extension">.bm</literal> |
| 1328 |
extension to avoid conflicts with <literal role="extension">.bmk</literal> files |
| 1329 |
created previously.</para> |
| 1330 |
|
| 1331 |
<para>Finally, the <guilabel>Convert as inline tags</guilabel> option creates |
| 1332 |
inline tags inside the resulting text file form <* |
| 1333 |
<replaceable>BookmarkName</replaceable> *> placing each tag in the place that |
| 1334 |
was previously referenced by the bookmark, and using the bookmark name as the |
| 1335 |
<replaceable>BookmarkName</replaceable> text inside the tag. Now you You can |
| 1336 |
edit the bookmark name, move it or delete it and convert back to Palm DOC, as |
| 1337 |
you wish. |
| 1338 |
</para> |
| 1339 |
</listitem> |
| 1340 |
</varlistentry> |
| 1341 |
|
| 1342 |
<varlistentry> |
| 1343 |
<term><guilabel>Do not convert, if text unchanged (only |
| 1344 |
bookmarks)</guilabel></term> |
| 1345 |
<listitem> |
| 1346 |
<para> |
| 1347 |
If you check this box, only changes in the text will trigger conversions from |
| 1348 |
Palm DOC to text files. In other words, changes in the bookmarks only will not |
| 1349 |
result in updates for the text files in your computer. |
| 1350 |
</para> |
| 1351 |
</listitem> |
| 1352 |
</varlistentry> |
| 1353 |
|
| 1354 |
</variablelist> |
| 1355 |
|
| 1356 |
<para> |
| 1357 |
In the <guilabel>Conflicts</guilabel> page, you can configure how the conduit |
| 1358 |
deals with files that changed both in the computer and the &handheld;. |
| 1359 |
</para> |
| 1360 |
|
| 1361 |
<variablelist> |
| 1362 |
|
| 1363 |
<varlistentry> |
| 1364 |
<term><guilabel>Conflict Resolution</guilabel></term> |
| 1365 |
<listitem><para> |
| 1366 |
The Palm DOC conduit does not feature merging the modifications when a text is |
| 1367 |
changed both in the &handheld; and in the computer. Therefore, the choice is |
| 1368 |
between working with the files out of sync, or discarding the changes in one of |
| 1369 |
them. The <guilabel>No resolution</guilabel> option will avoid synchronizing |
| 1370 |
texts with conflicts, the <guilabel>PDA overrides</guilabel> option will |
| 1371 |
overwrite the computer text file version in case of conflict, |
| 1372 |
the <guilabel>PC overrides</guilabel> will do the same, but the other way |
| 1373 |
around, |
| 1374 |
and the <guilabel>Ask the user</guilabel> option will bring a dialog to let the |
| 1375 |
user decide on a file by file, case by case basis. |
| 1376 |
</para></listitem> |
| 1377 |
</varlistentry> |
| 1378 |
|
| 1379 |
<varlistentry> |
| 1380 |
<term><guilabel>Always show resolution dialog, even when there are no |
| 1381 |
conflicts</guilabel></term> |
| 1382 |
<listitem><para> |
| 1383 |
This option will always bring the conflict resolution dialog, even if there is |
| 1384 |
no conflicts to solve. The advantage is that you can keep track of all the files |
| 1385 |
that are being covered by the conduit. |
| 1386 |
</para></listitem> |
| 1387 |
</varlistentry> |
| 1388 |
|
| 1389 |
</variablelist> |
| 1390 |
|
| 1391 |
|
| 1392 |
</sect2> |
| 1393 |
|
| 1394 |
|
| 1395 |
<sect2 id="conduit-kaddressbook"> |
| 1396 |
<title>&kaddressbook; Conduit Setup</title> |
| 1397 |
|
| 1398 |
<para> |
| 1399 |
This conduit will synchronize your &PalmPilot; with the &kde; address book or to |
| 1400 |
a vCard file of your choice. In the latter case, the conduit will need the |
| 1401 |
filename of the |
| 1402 |
vCard file (this will usually be a file that ends in <literal |
| 1403 |
role="extension">.vcf</literal>) to sync with, of if it uses the standard |
| 1404 |
&kde; address book file, it will be under the |
| 1405 |
<filename class="directory">$TDEHOME/share/apps/tdeabc/</filename> |
| 1406 |
folder, where the <filename class="directory">$TDEHOME</filename> environment |
| 1407 |
variable (typically <filename class="directory">/home/Login Name/.trinity/</filename>) |
| 1408 |
points to the folder that contains your configuration and data for the &kde; |
| 1409 |
applications. |
| 1410 |
</para> |
| 1411 |
|
| 1412 |
<screenshot> |
| 1413 |
<screeninfo>The &kaddressbook; Conduit Setup Dialog</screeninfo> |
| 1414 |
<mediaobject> |
| 1415 |
<imageobject><imagedata fileref="setup-address.png" format="PNG"/></imageobject> |
| 1416 |
<textobject><phrase>&kaddressbook; Conduit Setup</phrase></textobject> |
| 1417 |
<caption><para>&kaddressbook; Conduit Setup</para></caption> |
| 1418 |
</mediaobject> |
| 1419 |
</screenshot> |
| 1420 |
|
| 1421 |
<para> |
| 1422 |
In the <guilabel>General</guilabel> page, you can set the general address sync |
| 1423 |
options. |
| 1424 |
</para> |
| 1425 |
|
| 1426 |
<variablelist> |
| 1427 |
|
| 1428 |
<varlistentry> |
| 1429 |
<term><guilabel>Sync Destination</guilabel></term> |
| 1430 |
<listitem><para> |
| 1431 |
Choose between synchronizing with the <guilabel>Standard address book</guilabel>, |
| 1432 |
or in other words, the &kde; standard address book or with a |
| 1433 |
<guilabel>vCard file</guilabel> of your choice, that you must either |
| 1434 |
write in the <guilabel>vCard file</guilabel> edit box or select using the |
| 1435 |
file picker. |
| 1436 |
</para> |
| 1437 |
<warning><para> |
| 1438 |
You can use the address book conduit with any application that accepts a file in |
| 1439 |
the vCard format as a resource. However, some applications may not handle |
| 1440 |
the synchronization gracefully while they are open. As a rule of thumb, |
| 1441 |
quit these applications before synchronizing, otherwise you may lose data. |
| 1442 |
There is no need to take these precautions when syncing with the &kde; address |
| 1443 |
book. |
| 1444 |
</para></warning> |
| 1445 |
</listitem> |
| 1446 |
</varlistentry> |
| 1447 |
|
| 1448 |
<varlistentry> |
| 1449 |
<term><guilabel>Store archived records in the KDE address book</guilabel></term> |
| 1450 |
<listitem><para> |
| 1451 |
The &handheld; offers an option to archive deleted addresses in your desktop. |
| 1452 |
If that option is selected, check this box to keep the deleted addresses from |
| 1453 |
your &handheld; in your <acronym>PC</acronym> address book. These addresses will |
| 1454 |
be no longer synchronized with your handheld. |
| 1455 |
</para></listitem> |
| 1456 |
</varlistentry> |
| 1457 |
|
| 1458 |
</variablelist> |
| 1459 |
|
| 1460 |
<para> |
| 1461 |
In the <guilabel>Conflicts</guilabel> page, you can set the address book conduit |
| 1462 |
options, overriding &kpilot;'s general settings for conflict resolution when |
| 1463 |
you are using this conduit. For a detailed description of the different conflict |
| 1464 |
resolution possibilities available, please refer to the |
| 1465 |
<link linkend="page-hotsync">HotSync Setup section</link> of this handbook. |
| 1466 |
</para> |
| 1467 |
|
| 1468 |
<para> |
| 1469 |
In the <guilabel>Fields</guilabel> page, you can set the conduit options for |
| 1470 |
synchronizing the &handheld; address fields that do not have a direct |
| 1471 |
counterpart in the &kde; address book. |
| 1472 |
</para> |
| 1473 |
|
| 1474 |
<variablelist> |
| 1475 |
|
| 1476 |
<varlistentry> |
| 1477 |
<term><guilabel>Handheld other phone:</guilabel></term> |
| 1478 |
<listitem><para> |
| 1479 |
The <quote>Other</quote> field in the &handheld; address application can be |
| 1480 |
used for many things (for instance storing a secondary email address). It is |
| 1481 |
not clear how to classify this field in &kde;. Depending on your usage, select |
| 1482 |
in |
| 1483 |
the dropdown the field from the computer that will be synchronized with the |
| 1484 |
<quote>Other</quote> field from your &handheld;. |
| 1485 |
</para></listitem> |
| 1486 |
</varlistentry> |
| 1487 |
|
| 1488 |
<varlistentry> |
| 1489 |
<term><guilabel>Handheld street address:</guilabel></term> |
| 1490 |
<listitem><para> |
| 1491 |
While the <quote>Address</quote> field in the &handheld; address |
| 1492 |
application is the only default option for storing an street address, the &kde; |
| 1493 |
street address field can be a home address or a business address. The preferred |
| 1494 |
address will have precedence over other addresses, and the conduit will try to |
| 1495 |
set |
| 1496 |
this status by default. Either the home or business street address will be used |
| 1497 |
to |
| 1498 |
store the &handheld; street address. Select in the dropdown the option that |
| 1499 |
suits better your needs. For instance, if you use this field mainly for business |
| 1500 |
addresses, select <guilabel>Preferred, then Business Address</guilabel>. If not, |
| 1501 |
select <guilabel>Preferred, then Home Address</guilabel>. |
| 1502 |
</para></listitem> |
| 1503 |
</varlistentry> |
| 1504 |
|
| 1505 |
<varlistentry> |
| 1506 |
<term><guilabel>Handheld fax:</guilabel></term> |
| 1507 |
<listitem><para> |
| 1508 |
While the <quote>Fax</quote> field in the &handheld; address |
| 1509 |
application is the only default option for storing a fax number, the &kde; |
| 1510 |
address book can store a home fax or a business fax number. Select in the |
| 1511 |
dropdown the option that suits better your needs. For instance, if you use this |
| 1512 |
field mainly for business faxes, select <guilabel>Business Fax</guilabel>. If |
| 1513 |
not, |
| 1514 |
select <guilabel>Home Fax</guilabel>. |
| 1515 |
</para></listitem> |
| 1516 |
</varlistentry> |
| 1517 |
|
| 1518 |
</variablelist> |
| 1519 |
|
| 1520 |
<para> |
| 1521 |
In the <guilabel>Custom Fields</guilabel> page, you can set the conduit options |
| 1522 |
for |
| 1523 |
dealing with the <quote>Custom</quote> fields from your &handheld; address |
| 1524 |
application. Since there are no natural correspondence between these fields and |
| 1525 |
other &kde; address book fields, you can set them as you like. You can use them |
| 1526 |
to store a <guilabel>URL</guilabel>, a <guilabel>IM Address</guilabel>, |
| 1527 |
the <guilabel>Birthdate</guilabel> of your contact or the obvious: |
| 1528 |
<guilabel>Store as Costume Field</guilabel>. |
| 1529 |
</para> |
| 1530 |
|
| 1531 |
<para> |
| 1532 |
If you select to store birthdays, remember to use a date format that is |
| 1533 |
consistent with the settings in the <guilabel>Date format</guilabel> dropdown, |
| 1534 |
so that the conduit can correctly identify the date from the record and vice |
| 1535 |
versa. Possible placeholders are: %d for the day, %m for the month, %y for the |
| 1536 |
two-digit year, %Y for the four-digit year. For example, %d.%m.%Y would |
| 1537 |
generate a date like 27.3.1952, while %m/%d/%y would write the same date as |
| 1538 |
03/27/52. |
| 1539 |
</para> |
| 1540 |
|
| 1541 |
|
| 1542 |
</sect2> |
| 1543 |
|
| 1544 |
<sect2 id="sysinfo-cond"> |
| 1545 |
<title>System Information Conduit Setup</title> |
| 1546 |
|
| 1547 |
<para> |
| 1548 |
This conduit generates a page with your &handheld; information. Some info about |
| 1549 |
your &kde;, &kpilot; and Pilot-Link version is included as well. The available |
| 1550 |
output formats are &HTML;, text or custom template. The conduit |
| 1551 |
output and in special, the debug output section of the output may help the |
| 1552 |
developers track down bugs. |
| 1553 |
</para> |
| 1554 |
|
| 1555 |
|
| 1556 |
<screenshot> |
| 1557 |
<screeninfo>The System Information Conduit Setup Dialog</screeninfo> |
| 1558 |
<mediaobject> |
| 1559 |
<imageobject><imagedata fileref="conduit-sysinfo.png" |
| 1560 |
format="PNG"/></imageobject> |
| 1561 |
<textobject><phrase>System Information Conduit Setup</phrase></textobject> |
| 1562 |
<caption><para>System Information Conduit Setup</para></caption> |
| 1563 |
</mediaobject> |
| 1564 |
</screenshot> |
| 1565 |
|
| 1566 |
<para> |
| 1567 |
In the <guilabel>General</guilabel> page, you can set the output location and |
| 1568 |
format. |
| 1569 |
</para> |
| 1570 |
|
| 1571 |
<variablelist> |
| 1572 |
|
| 1573 |
<varlistentry> |
| 1574 |
<term><guilabel>Output File</guilabel></term> |
| 1575 |
<listitem><para> |
| 1576 |
Write in the edit box or use the file picker to select the location and file |
| 1577 |
name of the output file where the &handheld; system information will be written. |
| 1578 |
</para></listitem> |
| 1579 |
</varlistentry> |
| 1580 |
|
| 1581 |
<varlistentry> |
| 1582 |
<term><guilabel>Type of Output</guilabel></term> |
| 1583 |
<listitem><para> |
| 1584 |
Choose between <guilabel>HTML</guilabel>, <guilabel>Text file</guilabel> (plain |
| 1585 |
text), |
| 1586 |
or a selectable <guilabel>Custom template</guilabel>. To create a custom |
| 1587 |
template, you can |
| 1588 |
use the default template as a reference. |
| 1589 |
</para></listitem> |
| 1590 |
</varlistentry> |
| 1591 |
|
| 1592 |
</variablelist> |
| 1593 |
|
| 1594 |
<para> |
| 1595 |
In the <guilabel>Parts Included</guilabel> page, you can set which parts will be |
| 1596 |
included in the output, one by one, by checking or unchecking them in the |
| 1597 |
<guilabel>Output Type</guilabel> list. |
| 1598 |
</para> |
| 1599 |
|
| 1600 |
</sect2> |
| 1601 |
|
| 1602 |
|
| 1603 |
<sect2 id="todo-cond"> |
| 1604 |
<title>Todo Conduit Setup</title> |
| 1605 |
|
| 1606 |
<para> |
| 1607 |
This conduit will synchronize your &PalmPilot; To Do List application with |
| 1608 |
&korganizer; and &kontact;, or to an iCalendar file of your choice. |
| 1609 |
The configuration dialog looks and behaves exactly the same as the configuration |
| 1610 |
dialog for the <link linkend="vcal-cond">Calendar Conduit</link>. The only |
| 1611 |
difference is that instead of synchronizing the Calendar, you will be syncing |
| 1612 |
the To Do List. |
| 1613 |
</para> |
| 1614 |
|
| 1615 |
<screenshot> |
| 1616 |
<screeninfo>The Calendar Conduit Setup Dialog</screeninfo> |
| 1617 |
<mediaobject> |
| 1618 |
<imageobject><imagedata fileref="conduit-vcal.png" format="PNG"/></imageobject> |
| 1619 |
<textobject><phrase>Calendar Conduit Setup</phrase></textobject> |
| 1620 |
<caption><para>Calendar Conduit Setup</para></caption> |
| 1621 |
</mediaobject> |
| 1622 |
</screenshot> |
| 1623 |
|
| 1624 |
</sect2> |
| 1625 |
|
| 1626 |
<sect2 id="mal-cond"> |
| 1627 |
<title>MAL (AvantGo) Conduit Setup</title> |
| 1628 |
|
| 1629 |
<para> |
| 1630 |
The MAL (&AvantGo;) Conduit synchronizes your &handheld; with the &AvantGo; |
| 1631 |
server. |
| 1632 |
This conduit is based on |
| 1633 |
<ulink url="http://jasonday.home.att.net/code/libmal/libmal.html">Jason Day's |
| 1634 |
libmal</ulink>. |
| 1635 |
The &AvantGo; server offers general content (news, guides, stock quotes, &etc;) |
| 1636 |
in a format that is suitable for reading in a &handheld;. To use this conduit, |
| 1637 |
you need to register to a service provider, for instance, |
| 1638 |
<ulink url="http://www.avantgo.com">AvantGo.com</ulink>, subscribe |
| 1639 |
the channels you select and install the &AvantGo; software on your &handheld;, |
| 1640 |
and configure the software on your handheld to find the MAL server. |
| 1641 |
</para> |
| 1642 |
|
| 1643 |
<para> |
| 1644 |
The installation software for the &handheld; client is usually only available |
| 1645 |
for &Microsoft; &Windows;, if you |
| 1646 |
do not have access to a windows computer, you can try installing the databases |
| 1647 |
available in the <ulink url="http://www.tomw.org/malsync/">MalSync |
| 1648 |
Homepage</ulink>, |
| 1649 |
with different versions, one for <trademark>PalmOS</trademark> 5 and other for |
| 1650 |
older <trademark>PalmOS</trademark>s. |
| 1651 |
</para> |
| 1652 |
|
| 1653 |
<para> |
| 1654 |
To configure the software on your handheld to find the MAL server, open the |
| 1655 |
AGConnect application in your &handheld;, click <guilabel>Settings...</guilabel> |
| 1656 |
and enter your MAL server address, the <guilabel>User Name</guilabel> and |
| 1657 |
<guilabel>Password</guilabel> you got while registering. The |
| 1658 |
&AvantGo; server address is |
| 1659 |
<userinput>sync.avantgo.com</userinput>, and its port is |
| 1660 |
<userinput>80</userinput>. On some installations, you should use the MobileLink |
| 1661 |
instead of the AGConnect application on your &handheld;. |
| 1662 |
</para> |
| 1663 |
|
| 1664 |
<screenshot> |
| 1665 |
<screeninfo>The MAL (AvantGo) Conduit Setup Dialog</screeninfo> |
| 1666 |
<mediaobject> |
| 1667 |
<imageobject><imagedata fileref="conduit-mal.png" format="PNG"/></imageobject> |
| 1668 |
<textobject><phrase>MAL (AvantGo) Conduit Setup</phrase></textobject> |
| 1669 |
<caption><para>MAL (AvantGo) Conduit Setup</para></caption> |
| 1670 |
</mediaobject> |
| 1671 |
</screenshot> |
| 1672 |
|
| 1673 |
<para> |
| 1674 |
In the <guilabel>General</guilabel> page, you can set the synchronization |
| 1675 |
frequency options. It can be set for <guilabel>Every Sync</guilabel>, |
| 1676 |
<guilabel>Once per Hour</guilabel>, <guilabel>Once a Day</guilabel>, |
| 1677 |
<guilabel>Once a Week</guilabel> or <guilabel>Once a Month</guilabel>. |
| 1678 |
The conduit only runs when you hit &HotSync; on your &handheld;, so |
| 1679 |
<guilabel>Once per Hour</guilabel>, for instance, really means that |
| 1680 |
&kpilot; will only try to synchronize with the MAL servers if it is more than an |
| 1681 |
hour since the last MAL sync. |
| 1682 |
</para> |
| 1683 |
|
| 1684 |
<para> |
| 1685 |
The MAL conduit can work through a proxy server. In the |
| 1686 |
<guilabel>Proxy</guilabel> |
| 1687 |
page, you can set the proxy settings. |
| 1688 |
</para> |
| 1689 |
|
| 1690 |
<variablelist> |
| 1691 |
|
| 1692 |
<varlistentry> |
| 1693 |
<term><guilabel>Proxy Type</guilabel></term> |
| 1694 |
<listitem><para> |
| 1695 |
If you connect the Internet directly, select <guilabel>No proxy</guilabel>, |
| 1696 |
requiring no further configuration. But if you use a <guilabel>HTTP |
| 1697 |
proxy</guilabel> |
| 1698 |
or a <guilabel>SOCKS proxy</guilabel>, select it, to enable the rest of the |
| 1699 |
dialog and to make the conduit use it to connect the MAL server. |
| 1700 |
</para></listitem> |
| 1701 |
</varlistentry> |
| 1702 |
|
| 1703 |
<varlistentry> |
| 1704 |
<term><guilabel>Server Information</guilabel></term> |
| 1705 |
<listitem><para> |
| 1706 |
Write in the <guilabel>Server Name</guilabel> dropdown box the address of the |
| 1707 |
proxy server to use, in the form <userinput>foo.bar.com</userinput>, not |
| 1708 |
<userinput>http://foo.bar.com</userinput> or |
| 1709 |
<userinput>http://foo.bar.com:8080</userinput>. |
| 1710 |
</para> |
| 1711 |
<para> |
| 1712 |
Check the box <guilabel>Custom port:</guilabel> if your proxy uses a non |
| 1713 |
standard |
| 1714 |
port, and enter the correct port number. |
| 1715 |
</para> |
| 1716 |
<para> |
| 1717 |
In the <guilabel>No proxy for</guilabel> edit box, you may enter the list of MAL |
| 1718 |
servers that do not need the use of a proxy, separated by commas. For instance, |
| 1719 |
<userinput>localhost,lan</userinput>. |
| 1720 |
</para> |
| 1721 |
<para> |
| 1722 |
If your proxy require authentication, enter your <guilabel>User name</guilabel> |
| 1723 |
and <guilabel>Password</guilabel> in the respective edit boxes. |
| 1724 |
</para> |
| 1725 |
</listitem> |
| 1726 |
</varlistentry> |
| 1727 |
|
| 1728 |
</variablelist> |
| 1729 |
|
| 1730 |
<para>In the <guilabel>MAL Server</guilabel> page, you can set the MAL server |
| 1731 |
address and settings. Currently, you can only configure this settings using |
| 1732 |
the &handheld; MobileLink or AGConnect applications, so this page is |
| 1733 |
disabled.</para> |
| 1734 |
|
| 1735 |
</sect2> |
| 1736 |
|
| 1737 |
<sect2 id="popmail-cond"> |
| 1738 |
<title>Mail Conduit Setup</title> |
| 1739 |
|
| 1740 |
<para> |
| 1741 |
This conduit allows you to send mail using a transport. |
| 1742 |
The configuration of the Mail Conduit is fairly simple. |
| 1743 |
</para> |
| 1744 |
<screenshot> |
| 1745 |
<screeninfo>Setting up the Mail Conduit</screeninfo> |
| 1746 |
<mediaobject> |
| 1747 |
<imageobject><imagedata fileref="conduit-popmail-kmail.png" |
| 1748 |
format="PNG"/></imageobject> |
| 1749 |
<textobject><phrase>The Mail Conduit Setup Dialog</phrase></textobject> |
| 1750 |
<caption><para>The Mail Conduit Conduit Setup Dialog</para></caption> |
| 1751 |
</mediaobject> |
| 1752 |
</screenshot> |
| 1753 |
<para> |
| 1754 |
There are two tabs in the setup dialog for the Mail Conduit, |
| 1755 |
one for Sending mail and one for the credits of the mail conduit. |
| 1756 |
</para> |
| 1757 |
|
| 1758 |
<para> |
| 1759 |
Depending on which send method you choose, |
| 1760 |
different fields will be activated in the remainder of the |
| 1761 |
tab, allowing you to enter the necessary information. |
| 1762 |
Currently, the only method available is <guilabel>Using KMail</guilabel>, |
| 1763 |
which has a very simple configuration. |
| 1764 |
</para> |
| 1765 |
|
| 1766 |
<para> |
| 1767 |
Your email address can be entered in the <guilabel>Email |
| 1768 |
Address:</guilabel> field. This is the email address that goes in the |
| 1769 |
<quote>From:</quote> line in outgoing mail. If you enter a file name in |
| 1770 |
the <guilabel>Signature File</guilabel> field then that file will be |
| 1771 |
appended to each outgoing mail as a signature. |
| 1772 |
</para> |
| 1773 |
|
| 1774 |
<para> |
| 1775 |
When sending mail through &kmail;, &kpilot; automatically places it in |
| 1776 |
your &kmail; outbox. &kmail; saves mail in the outbox until you request |
| 1777 |
that those pieces of mail are <emphasis>really</emphasis> sent. |
| 1778 |
</para> |
| 1779 |
|
| 1780 |
</sect2> |
| 1781 |
</sect1> |
| 1782 |
|
| 1783 |
</chapter> |