Re: lynx-dev pre.10 : Options Form/Menu

[Bela Lubkin]

Ismael Cordeiro wrote:

> > & we've run out of space on the 1st Menu screen already,
> 
> The what we need is a way of giving to the non-forms options menu more
> pages.

Indeed; and that will take some programmer effort, which will have to
come from a volunteer.  I can't speak for everyone, but it seems clear
to me that *most* of the active programmer-contributors prefer the new
forms-based option menu.

> > so there's a Lynx programming premium on eliminating the Menu
> 
> I don't see it.

The premium would come from eliminating future work (adding multi-page
support to the non-forms menu) and ongoing work (maintaining two
distinct options menus in synchrony).

> > if no-one speaks up to say they actually need it (not "might maybe").
> 
> I've already clearly stated that I want the non-forms options menu. It's a
> lot faster and easier to use than the forms options menu. However, I
> understand that many people may prefer the forms options menu, so give them
> the choice in lynx.cfg.

You're in the minority.  What you desire is going to come about only if
someone commits to indefinite future maintenance of the non-forms menu.
So far you're the only one requesting it, so you're the only potential
candidate to make that commitment.

=============================================================================

But I think there must be a better approach.  Instead of committing
someone to maintain obsolete code forever, and committing the Lynx
binary and source to lug around duplicate, obsolete code forever; why
don't we try to understand *why* you find the new menu harder to use?
Maybe it can be fixed so that everyone will prefer the new (or at least
be willing to accept it).

I have far too much experience with pieces of code that are kept around
to "parallel" something new.  They inevitably rot.  At first you would
see missing options (like the cookies stuff).  Later, changes elsewhere
in Lynx would make parts of the old menu fail completely -- they'd look
right on screen, but the underlying mechanisms would be different, they
would fail to configure what they're supposed to configure.  Eventually,
unless someone was actively maintaining it, we'd get to the point where
Lynx wouldn't even compile with the "include old options menu" option
enabled.

Please detail what you find so difficult about the forms-based menu.

>Bela<