Re: lynx-dev lynx -lss option bad [BSDI-Support-Request #53069]

[Jason F. McBrayer]

>>>>> "PW" == Philip Webb <address@hidden> writes:

PW> 980721 Larry Virden wrote: 
>> I myself am torn over whether experimental code should be removed
>> if not currently being worked on.
>> If it's removed, then it is likely that it will never be worked on.
>> If it's present, then perhaps someone will pick up the banner.
 
PW> yes, that's a good point, but just leaving it forgotten in a
PW> Release is surely bad practice.  could we do a `reverse patch'
PW> operation: ie move extracted material to an archive directory like
PW> To Do, whence people could grab it & play with it when they felt
PW> inclined?  that might be a better stimulant for typical Lynx
PW> programmers, who tend to lack time rather than motivation.

IMHO, it's better to leave things like colour styles in (though
#ifdef'ed out by the default options to configure) so that they can be
readily played with in semi-working form.  That would make it easier
for anyone who wants to change them to get experience with them.  Just
my two cents.  I kinda like the color styles code, even though it
doesn't really have anything to do with CSS.

That reminds me.  I'm going to start reading the availible docs on XML
to try to get a user-level understanding of it, just so I can get a
picture in my head of what if anything needs to happen to Lynx to
support XML, and to what extent XML support is possible in a
character-cell browser (without page-author cooperation).  I'll report
back to the list, since it sometimes seems we have a lot of confusion
here about XML, CSS, and such things.


-- 
+----------------------------------------------------------------+
| Jason F. McBrayer              address@hidden |
| The scalloped tatters of the King in Yellow must hide Yhtill   |   
| forever.                    R.W. Chambers _The King in Yellow_ |