lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LYNX-DEV suggestion for post lynx 2.7 development


From: Larry W. Virden, x2487
Subject: LYNX-DEV suggestion for post lynx 2.7 development
Date: Tue, 28 Jan 1997 14:13:22 -0500

I would like to suggest to folk that they weigh carefully new features
that they choose to implement against the impact to the user interface.

Take for example two recent features that have been added; the handling
of post vs get form requests and cookies.

The potential benefits are quite important.  However, the amount of
interaction that the user is required now to provide is significantly
increased.  I have to expect that for naive users, this is going
to become increasingly difficult to determine how to respond.  Previously
users were confused about what to do when lynx mentioned the fact that
bad html was encountered.  However, it was a warning only.  Now users
are forced to respond to prompts, without an option to explain to
them what the ramifications with their choice.  If they refuse a cookie,
will they get into a site or not; and if they do, what do they lose
by having refused the cookie.  And of course, lynx itself cannot (I suspect
in most cases) tell what the ramifications are.  It seems a similar
situation exists for the post/get actions.

I hope that lynx doesn't evolve into a tool that requires so much
upfront training that it isn't usable any longer by the average joe on the
street.
-- 
Larry W. Virden                 INET: address@hidden
<URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]