Specs for an ideal public library web browser
Alejandro Garza Gonzalez
agarza at ci.mty.itesm.mx
Wed Sep 18 17:22:35 EDT 1996
What we have just come to use as a fornt-end to our library services, and
as a gateway to navigating the WWW, is a combination of several pieces of
software running in our library workstations. These include:
* Netscape Navigator 2.02, Kiosk mode
- recent enough to read most HTML code out there
- smaller than release 3.0
- kiosk mode eliminates menus and unwanted buttons
Cons: kiosk mode eliminates ALL menus, "Mail document..",
"Save as.." functions wanted but lost, CTRL-key shortcuts still
available
* JavaScript homepage w/frames
- Lets us program 'back', 'forward' and 'home' buttons onto Netscape,
in small frame on top of the screen.
- Lower frame looks exactly like browser main screen.
Cons: JavaScript functions not completely reliable, server push GIF
animations might block history.back() and forward() functions
* Flute Macro Language
- Eliminates unwanted user fiddling with Program Manager, etc, by
closing or hiding unwanted windows
- Automates startup process (launching WinQVT, Netscape,
Netware login...)
- Resets netscape to homepage after period of mouse inactivity
- Logs into Novell server on startup automatically
- Makes Shell or Telnet windows (or both) the topmost window so user
doesn't forget about them
- Keeps windows maximized or a certain size
- Disables Toolbar in Win95 DOS windows
Cons: No provision to monitor activity from keyboard strokes
* Misc. others:
- Using Program Manager shell in win95 instead of explorer
- Hiding Novell login startup window
* TODO:
- Double click on backdrop brings up the tasks window, from where the
user can still Explore and launch any program...
If you want to try out our Kiosk/Frames/JavaScript approach, you can
start up Netscape (in Win3.1 or 95) with
netscape.exe -k http://www-cib.mty.itesm.mx/estaciones/
(provided you are in the Netscape program directory).
Addressing some om Joseph's comments::
> A convenient way to lock patrons out of our hard drives.
For us, making the program manager itself disappear pretty much locks
users out... closing or hiding DOS windows that shouldn't be there
also does the trick. (Flute can check this every 5 secs or so...)
> .. [stuff about SurfWatch et al]...
I would rather let users surf freely, but provide privacy with a
Privacy Screen (3M).
> A feature that allows conspicuous notice to the patron about
> cached pages and allows him or her to flush them, to
> protect his or her privacy.
When the user hits our 'home' button, the history is erased...
> A feature that allows the library to set time-delimited
> sessions. (We're having serious difficulties with work-
> station hogging.) I'm thinking of a feature that would
> automatically shut the browser down after x minutes, with
> a notification that the time limit had expired.
I bet you could program this with Flute. (Make Netscape dissappear
after X minutes, bring up a requester to let the next user in... how
to check the next user is really the 'next' one... well...)
> Naturally these are just ideas to get everyone thinking.
> They may be naive or impractical. First question: Is it
> naive or impractical to develop a list of specs to take
> to a developer? (I am assuming that there is a large
> market -- in the form of tens of thousands of public
> libraries -- for an appropriately extended browser.)
I wouldn't think so, but with Netscape's and Microsoft's titanic
battlestorm taking place trying to outdo each other, I don't think
either would place much priority on such a project.
> Your thoughts will be most highly appreciated!
So will anybody else's! =)
> Thanks,
> Joe Schallan
> jschall at glenpub.lib.az.us
> Glendale (Arizona) Public Library
_ alejandro garza _________________ __ _ _ _ _
ITESM Centro de Informacion-Biblioteca Monterrey
agarza at campus.mty.itesm.mx
_ http://www-cib.mty.itesm.mx/ ____ __ _ _ _ _
More information about the Web4lib
mailing list