lynx-dev
[Top][All Lists]
Advanced

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

Re: LYNX-DEV patch to make "=" page "live" (revised "patch 11")


From: Foteos Macrides
Subject: Re: LYNX-DEV patch to make "=" page "live" (revised "patch 11")
Date: Sat, 02 Nov 1996 21:25:39 -0500 (EST)

Bela Lubkin <address@hidden> wrote:
>This is a patch to make the Information Page (normally reached by
>hitting "=") have active links instead of just passively showing the
>URLs of the current page and link.
>
>This version is more careful about not presenting a POST URL in an
>unusable form.  It should only display POST URLs without making them
>"live".
>
>The same patch works against 2.6 and Rob's current developmental code
>(LYShowInfo.c hasn't been changed).
>
>Subir, please update this on your patches page.
>
>Foteos, please comment whether this version is still misguided...

        What you want to do is misguided.  My opinion will not
change, just as my opinion that a lynx.cfg should be required,
and that development code should not be distributed as de facto
production code on CD ROMs without adding an SCO instead of FM
or RP suffix to the version, will not change.  You need not ask
my opinion again if you persist in any of those matters, because
my opinions will not change.


>Rob, please incorporate.  ;-}

        I hope Rob doesn't.  A great many considerations must be
taken into account when a user reactivates or refreshes a previous
link, either by way of the left-arrow. RELOAD or RESUBMIT commands,
for via an ACTIVATE in the history list.  Even if you got the
LYShowInfo.c code fully debugged and SGML compliant, using that
instead of the history list is misguided, adds needless overhead,
and another layer of complications for regulating cache, now or
in conjunction with any future enhancements.

        If it were added, I'd remove it from our code set here.
        
        But I'm on vacation, and hoping that during this period
others will have an opportinity to become broadly familiar with
the Lynx code, and develop a clear vision of how it works, what's
worthwhile to add, and where it's going w.r.t development
priorities.  Hopefully, it won't regress into a hodge-podge
of contributed patches that makes it as incoherent and
"unmaintainable" as it was two years ago, but at the same
time, others do have to go through some trial and error before
they get good at maintaining/developing Lynx.

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================

        
;
; 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]