Ltsp-Palm-Devices

Differences between revisions 3 and 4
Revision 3 as of 2007-05-07 07:31:05
Size: 936
Editor: 195
Comment:
Revision 4 as of 2007-05-07 08:49:31
Size: 1941
Editor: 195
Comment: First cut
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
 * Clay, a lawyer, walks up to his thin client, and logs in, he launches gnome-pilot, and connects to his palm, and syncs to his calendar within Evolution.
 * Julia wants to back up her palm. She plugs in her palm to the thin client, and starts KOrganizer. Things work as expected.
  
Line 22: Line 24:
 * {{{ltsp-build-chroot}}} should also include {{{pilot-link}}}
 * {{{pilot-link}}} needs promotion to main.
Line 25: Line 29:
 * Install {{{pilot-link}}}
 * the {{{ltsp-client-setup}}} needs a section like:

{{{
if [ ${LTSP_PALMPILOT} == "true" ]; then
    pilot-nredir -n -p /dev/pilot
fi
}}}

 * User will need to set up their palm application to point to their thin client.
Line 28: Line 42:
 * It would be nice to automatically set the $PALMPORT environment variable on the client to point to what LTSP client they're on. For a first cut, the user can manually configure, and we'll sort out auto configure next cut.
Line 31: Line 46:
 * Auto background sync with Evolution when the "palm sync" button is pressed, without the need for user interaction?

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

  • Launchpad entry: ltsp-palm-devices

  • Packages affected: ltsp-client, ltsp-server, ltsp-localapps

Summary

Currently, thin clients in a business environment cannot use palm syncing, as there's no way to plumb a connection over the network. We need to install some extra bits in the LTSP chroot to make this happen.

Rationale

Palm devices are still in use in the business world, and this is a feature that the LTSP developers desire to get working.

Use cases

  • Clay, a lawyer, walks up to his thin client, and logs in, he launches gnome-pilot, and connects to his palm, and syncs to his calendar within Evolution.
  • Julia wants to back up her palm. She plugs in her palm to the thin client, and starts KOrganizer. Things work as expected.

Scope

  • ltsp-build-chroot should also include pilot-link

  • pilot-link needs promotion to main.

Design and Implementation

  • Install pilot-link

  • the ltsp-client-setup needs a section like:

if [ ${LTSP_PALMPILOT} == "true" ]; then
    pilot-nredir -n -p /dev/pilot
fi
  • User will need to set up their palm application to point to their thin client.

Unresolved issues

  • It would be nice to automatically set the $PALMPORT environment variable on the client to point to what LTSP client they're on. For a first cut, the user can manually configure, and we'll sort out auto configure next cut.

Future Plans

  • Auto background sync with Evolution when the "palm sync" button is pressed, without the need for user interaction?


CategorySpec

Ltsp-Palm-Devices (last edited 2008-08-06 16:16:52 by localhost)