TO DO LIST for WAIStation.app
with many good suggestions from users (attributions deleted)...
----------------------------------------------

It would be nice if, when one double-clicks on a .src to obtain the database info, that the .sh icon to re-index appear there, rather than have to pile a slew of indexer shell files in /LocalApps.

When a new question or source window is opened, don't open it at the default location and then snap it to an offset location down and to the right: it looks kludgey.

openFile:"xxx.wais" when WAIStation is running gets both WAIStataion and Workspace hanging, waiting for each other.  No code to handle opening .wais files really.

I might suggest that documents be linked to the query that retreived them and deleted if the query is not saved.  This would make is easier to reduce the proliferation of 'meaningful garbage' as well as making it easier to (re-)establish the context of a prior query (i.e. by providing a view of only those documents retrieved by the query).  A flat view of all documents, such as is now provided, could be a switch on the window (like the cancel button).  I suppose that this would require some redundency for documents that happen to get retrieved by more than one WAIS Question; perhaps automatic re-retrieval (sort of a document persistance) would help this issue.

semantics of dragging: dragging from ref type lists (use sources, similar to docs) should (re)move, but dragging from value type lists (source and doc palettes) should copy.  Use 3.0's improved drag support to indicate these semantics via cursor

* In the source window what does "server" mean?  Since you have so much
space, you might want to have an example in your line or a help button that
will explain each slot.  This would be a poor man's help balloon system
that apple has put in to system7.  really very helpful.

* after I have finished indexing, the sources list is not updated.  I
imagine this is because you cache the list, but can you flush that after
you finish the indexing?

When WAIS does not return any answers, you put up a dialog box.  this might
be overkill.  It is nice to be able to move along quickly to find words
that it does have.

  * When it can not connect to a server, it gives me 3 different dialog
boxes: one for the host, one for the .src couldnot connect, and one for no
documents returned.
  * I suggest that when the ip-name does not work, it should try the
ip-address.  If this does not work, the trendiest idea is to go back to the
server that gave the .src file to you and re-retrieve it.  This would cure
the problem of people changing the .src files.

> It would be better if WAIS did not upsurp the focus from the 
> current application when displaying messages to the user.
Well, technically it doesn't.  It's only when you click the "OK" button on the alert panel bearing the message, that WAIStation becomes the current app (since you've clicked on a panel belonging to WAIStation).  Your point is good, though.

If you delete a source, then
any docs from it left in the Doc Palette will cause complaints because
the program keeps retrieval info on those docs (that's the .wais file).

SOURCES
	shift-select getting trashed by back-connection to browser---why?
		(this doesn't happen in doc browser)
	make BrowserPanes Services-aware
	set up Command-W service to search for selection in WAIS' current Q.
	deleting sources should delete all the name.* files if any
	grok DL indices
	"at" auto-retrieval/indexing? (NeXT's "at" is bogus!!!)

DOCS
	last ')' of :document struct doesn't get written to .wais files?
	
QUESTIONS
	hit return in browsers too?
	search in thread?
	question palette?
	
RETRIEVAL
?	don't copy files from local DBs?  (does this make sense?)
	
MISC
	error in -free crashes program when windows free on close

programming details...
decide when to commit to 3.0-only source code/NIBs
must use [pboard types] before reading from pboard!!!
null termination of pboard data!!!???
need [openpanel directory] when no dir spec'd in runmodal call?????