More suggestions...

[Andrew Burday]

As long as we're making suggestions...

When you click on a telnet or tn3270 anchor, OmniWeb opens a Terminal.app
window.  Unfortunately, it tends to open the window behind the OmniWeb
window.  Also, if you close the Terminal window or quit Terminal, then
later click on another telnet anchor, OW will not restart Terminal or open
a new window.  My users and I use telnet anchors a lot, because we have to
connect to libraries' catalogs; that is almost always done by telnet.  I
have three suggestions here: 

(1)  For myself, it would be nice if I could specify Stuart instead of 
Terminal.

(2)  For my wildly computer-phobic and -illiterate users (believe me, you 
have NO idea what a true computerphobe is until you've dealt with some 
academic philosophers), it would be nice if the Terminal window opened ON 
TOP of the OW window.  Having to click on the window to bring it to the 
top is the kind of thing that, sad to say, confuses computerphobes.

(3)  Similarly, if OW could check to see if it has a Terminal window, and 
restart the app/open a new window if not, that would help.  A lot of my 
users think the right way to end a telnet session is to close the window.
The problem is that once they do that, they can't use OW to start a new 
telnet session.

Best,

Andrew Burday
andy at philo.mcgill.ca