ShuttleClock v1.0e Help

Description -------------------------------------------------------------

   ShuttleClock is a personal shuttle schedule manager that uses
   the SpiraClock vizualisation technique for short-term events.
   This version contains the regular schedules of Schuttle-UM from monday to
   friday as displayed at http://www.umd.edu/shuttle

   Contact: Pierre.Dragicevic@emn.fr
   Web: http://www.cs.umd.edu/hcil/spiraclock

Requirements ------------------------------------------------------------

   Java 1.3 or higher

Usage -------------------------------------------------------------------

java -jar shuttleclock.jar [options] [schedule [schedule...]]

Where [options] are:

   -help             Displays this page.
   -file fileName    Loads schedules from a specific data file.
   If not specified, the data file will be downloaded from
   http://www.cs.umd.edu/hcil/spiraclock/shuttle.txt
   This helps to keep the data up-to-date on all clients. If ShuttleClock stays
   open a long time, it will evenly reload the file each 12 hours.

Where [schedule] are the shuttle hours you are interested into.

   A schedule relates to a specific stop in a shuttle service:

   schedule = service#stop[#stop2] [startOffset [endOffset]]

   For example, 'greenbelt#3' displays the schedule of the third stop of
   greenbelt service. This string must be a valid service/stop pair.
   Lauching ShuttleClock with no schedule argument will display the list
   of valid service/stops for the current data file.

   You can also use compound schedules: 'greenbelt#3#14' will display the
   time intervals from the third to the fourteenth stop. This is useful when
   you want to plan connections, or view your arrival time. However, it is
   more difficult to read.

   startOffset and endOffset are integers that affect how time intervals
   are displayed.
   For example, 'greenbelt#3 -6 2' will display time intervals of
   [h - 6mn, h + 2mn], h being the exact hour displayed on the schedule.
   Ideally, h + startOffset is the time when you can start to prepare
   yourself calmly, say bye to your colleagues and walk slowly to the shuttle
   stop being sure that everything will be OK. And h + endOffset is the
   time when you have to hastily take your things, slam your door and run
   like a mad to have some chance to catch the shuttle.
   You may also want to use these parameters to compensate for the
   difference between the displayed stop and the stop you are actually using,
   and time variation of the traffic.
   If you are using compound schedules, you may use endOffset to predict your
   arrival time.
   Default values are '-5 0' for simple schedules and '0 0' for compound
   schedules.