; $Id: TODO,v 1.3 1998/12/31 15:55:30 mgb Exp $

Pri Description

1   Be more assertive about wanting incrTk at install
1   Decide on Man page or TexInfo documentation
2   Can it run other than as root?  (ioperm() is the problem)
2   Find a way to setuid w/o opening a security hole
2   Make code protect bits more obvious to user
3   Auto probe for pic programmer?
3   Change name of "Erase" when it means "Blank check"
3   Maybe abort automatically after threshold number of errors?
4   Make a preferences editor window
4   Report something other than "bytes" when loading?
5   Read other forms of input (8 and 16-bit IntelHex)
6   Expose memory map to user? (e.g., set location of EEPROM psect?)
7   Green light/Red light feedback?
7   Maybe abort after threshold of errors?

Changes from version 0.4

  * Use Debian autoconf, automake, ... to manage distribution

Changes from version 0.3

  * Initial documentation... (crude)
  * Added blank check to "erase" button
  * Add "abort" capability to core
  * Make GUI event-loop based to allow abort?
  * Store preferences to an RC file
  * Add "abort" button to Gui

Changes from version 0.2

  * Begin using RCS for revision control
  * Add progress indicator.
  * Finish populating menus...
  * Fix error feedback to GUI
  * Recode GUI in incrTk?  (for megawidgets, etc...)
  * Toggle lines and set pins based on programmer...

Changes from version 0.1
  * Use "dirty" bits to speed up programming?
  * PicCore and PicDriver should be merged...
