Ltsp-Palm-Devices

Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2007-04-24 16:39:32
Size: 21
Editor: mail
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 1: Line 1:
#REFRESH 0 SpecSpec ##(see the SpecSpec for an explanation)

''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.''

## Register at https://launchpad.net/distros/ubuntu/+specs
 * '''Launchpad entry''': UbuntuSpec: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

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)