
  The "to do" items below are listed on a "current priority" basis, i.e.
 the one I'm most inclined to work on is the one listed first, while the
 rest further down will be addressed in the near future. If it is your
 feeling that some item should be "bumped" up to a higher priority,
 please do drop me a line :)  Also if you've come across some problem
 mentioned below, please do provide any type of feedback you think would
 help towards finding a solution.


 - Investigate manual dialing option with interrupt, hang-up etc.
   buttons.

 - Add "Skip" button for interactively skipping tel. numbers in a
   list being dialed by xispdial (Shiv Chadha <shiv@pacificpost.com>).

 - Investigate possibility of implementing a special "script-interrupt"
   specifier (e.g. %?) in user script lines. Upon detection of such an
   "interrupt", xispdial would "cut" the generated script at that point,
   pass it to chat, and when chat returns, pop-up a window for user
   input, read a string, then assemble the rest of the script using this
   string, and either finishing, or continuing with the next script
   "interrupt". Such a scheme would greatly enhance SecurID (and the
   like) logins.
   Alternatively merge Jim Shallman's simple code for a SecureID prompt.

 - Enable verbose chat execution when in debug mode, but only for pppd
   versions 2.[34].x and later. Enable selecting "-debug" from within the
   GUI ("-debug" turns on chat verbose mode also).

 - Support "collapsed" state, with maybe only a single button. Useful
   for fvwm2's button bar, or for small resolution displays (e.g. on
   a laptop). Also support auto-minimize upon connection.

 - Support "idle disconnect" by monitoring the packets flowing through
   the PPP interface, and/or use the "idle-disconnect" capabilities
   in pppd-2.[34].x

 - Add internationalization patches by Ricardo Stefani (these surely
   need updating).

 - Implement control for reseting logs.

 - Edit post-connect/post-disconnect commands from within xisp,
   for execution as user via strings passed to .xisp-up/-down.

 - Investigate memory bloat :)

 - Investigate implementing tx/rx blinkies and/or packet-traffic or even
   better byte-traffic indicators "a la" xload.

 - Support charging plans by ISPs that e.g. charge a fixed tariff for a
   maximum amount of connection time (e.g.) per month, and apply normal
   charges from that point on.

 - Implement feature for stopping dial attempts beyond a limit set by
   the ISP's "access plan". xisp should keep track of successful dials
   (or logins) and a) refrain from dialing when the limit is exceeded
   (possibly allowing an override), and b) notify the user through a
   number of ways (mail, console message, pop-up window etc.). The
   limit shall be defined as a number of maximum dials per fixed time
   periods (minutes, hours, days, months).

 - Implement something similar to the above, but for connection time.
   Here, xisp should disconnect if a fixed amount of connection time has
   been reached for the period under consideration.

 - Implement feature for not accepting connections below a certain
   speed "threshold". This can be used to pick a "good" phone line,
   or a higher speed modem if not all are of same speed. This is also
   implemented via init commands in some modems (e.g. US Robotics).

 - Investigate possibility of adding ISP cost on top of PTT cost.

 - Support two phases for .xisp-up: one immediately *before*
   connecting and one immediately after (i.e. call twice -- this
   is currently implemented only for .xisp-down).

 - Capability to use different speeds for dial-in and call-back
   connections.

 - Option for online display to flip between time and charge every 5
   seconds (when it updates - same for icon title). Or, maybe flipping
   between cost and a countdown to the next charge unit. Possibly add
   special sound(s) 10s (or so) before next unit and/or when changing
   charging rule.

 - Have "logical" modems instead of saving modem info with ISP info;
   every ISP entry could then use any one logical modem.

 - Investigate possibility of xisp working together with diald.

 - Automatic chat-script generation from one terminal-login.

 - A status bar showing the dialing progress.

