---------- ---------- ---------- ---------- ---------- ---------- ----------
Simple Spreadsheet TODO list
---------- ---------- ---------- ---------- ---------- ---------- ----------

** toggle TBLSTYLE into MISC Menu!

** CHECK OVER THE DOC's -- ESPECIALLY RE: ANY CHANGES MADE
   (Note menu re-arrangement)

-> The <DEL> key deletes both Value and Label.  We need a way to delete
   just the one or the other.  If you edit a value and reduce it to null,
   there is a parse error.  (IF you edit a label and nullify, it works
   fine)

-> Let's start using those Function keys!?
	F1: Save,  F2: Save-As, (Edit Text, Edit Value)

-> lint everything?
-> make a patchfile.h?  Look into patch.

-> Reverse video on some of the prompts?

-> Convert smaller functions to macro's?

-> Clean up the code.  See if we can move some of those #IFDEF's
   into a header file and get them out of the code.  SEE the document
   on code style!

-> /RowColumn
    - Yank should (like Merge) automagically insert Rows or Columns 
    (either-or, not both) for the yanked text.

-> work up a cut & paste gizmo, instead of the current
   kludgey delete/yank/merge mess?  (Maybe someday.  Right now
   it's not worth the effort.)

-> Context (so-so) sensitive on-line help!  This has been started, but
   needs work.  Is it worth it?  Need to pipe program output
   to a pager, then we don't have to worry about screen sizes.

-> Tutorial Spreadsheet?

-> startup "rc" file for setting lots of things up
	-> ability to bind keys & Fkeys to actions 
	   (this'll probably require a lot of work in the
	   interpretation of command keys in the code, but
	   it'd really make the program MUCH better)

-> Trim the man page to a bare-bones quick-reference -> I think that's
   the best use for it -> then put together a LaTeX(?) tutorial/introduction
   manual full of verbiage & other stuff that most folks only need to see
   occaisionally.   

   (??? Is this a good idea ???)

-> Put an indicator in the top left corner of the spreadsheet
   display, an ``*'' to indicate when the spreadsheet has been changed.
   (This would go in the blank space left of the "A" and above
    the "0" labels)

   Flip the row/colum labels where the cursor is located into inverse
   video ???????  This should make it easier to visually locate the
   cursor?

-> clean up ss.h -> distribute files amongst proper *.h files ??  -> or
   leave all in one *.h file, but organize the file better.

-> Row/Column Menu -> "Show".  In 'sc' you could enter a range of 
   rows or columns to show.  Add this functionality back?

-> Bruce Momjian <root%candle.uucp@bts.com>
  "I want to make a suggestion.  Quick cell editing is very often needed. 
   I have remapped '+' and '"' to CellEditValue() and CellEditLabel(). 
   This allows my wife to quickly add values and strings to existing cells.
   Under sc, e and E where required, but ^XL and ^XV are too hard to use."

  -hmm, let's try using F-keys?  or is this just a can of worms that
   we don't want to open?  Worth some thought.  I don't want to use " or +,
   as those are useful.  I don't think that there are any available
   control-keys left that we could use, are there?

-> International Character sets?  ie: ISO Latin-1 character-set

-> '8.3' filenames to satisfy DOS users?  (bleah!)

-> Investigate using raw()/noraw() instead of cbreak()/nocbreak.
   (see keys.h)  This will enable us to use ^Q and ^S (and ^O on Suns).
   But it will also force us to deal with ^C and ^Z.   See "Bugs" file.

-> when Entering strings (via "<> ) you have to deal with that double
   quote -- to distinguish between strings and string functions.  Can
   we somehow move that behind the scenes so the user doesn't have to
   deal with it?  Or is that the best way?  It *does* help the user
   know what's going on, but I'm not fond of it.

-> See the man page (/-Edit-Copy) for a bug in copy.  Let's make some
   way (via ^G, probably) to abort copy operations in the middle.

-> Filters to convert ss (or sc) data files to/from other standard
   spreadsheet files, e.g. Lotus ".wks" format, or Microsoft SYLK
   format?  (The latter is ASCII, not all that different in principle
   from the sc format, and can be read/written by Excel on both PCs
   and Macs. It would be useful.)
	    suggested by: braner@uvm-gen.EMBA.UVM.EDU <Moshe Braner>
---------- ---------- ---------- ---------- ---------- ---------- ----------
