home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!news.uiowa.edu!ns-mx!tinyblue.cs.uiowa.edu!brintle
- From: brintle@tinyblue.cs.uiowa.edu (Lee Brintle)
- Newsgroups: alt.gopher
- Subject: Request: approval and support of read-only options
- Message-ID: <13326@ns-mx.uiowa.edu>
- Date: 30 Jul 92 01:47:59 GMT
- Sender: news@ns-mx.uiowa.edu
- Reply-To: brintle@tinyblue.cs.uiowa.edu (Lee Brintle)
- Organization: U of Iowa, Iowa City, IA, USA
- Lines: 21
-
-
- We've been using a read-only extension to the Gopher protocol for about
- six months at U Iowa. Basically, the server can send back information
- in a gopher menu that is for information about the menu only.
-
- They have been a vital and useful part of our menuing system; it's much
- nicer to see a few lines about what the menu is about rather than having
- the user choose the first option ("About...") to see what is going on.
-
- As an example of this idea in action, please telnet to panda.uiowa.edu
- and look at some of the main screens. They lend a great deal of clarity
- to what is going on...
-
- Graphical clients display read-only information in a "header" and a "footer"
- window above and below the options. Any text mixed in with other options is
- simple non-selectable. It works. It's easy.
-
- Currently, we use type "i" for this, but any letter will do.
-
- Lee Brintle | ``And so, I leave you with this final word:
- Project Panda | twang.''
-