lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev [PATCH 2.8.3.dev6] patch that allows user to define what


From: Vlad Harchev
Subject: Re: lynx-dev [PATCH 2.8.3.dev6] patch that allows user to define what charsets will appear in "assumed doc chset" and "display chset" popups
Date: Mon, 16 Aug 1999 01:44:15 +0500 (SAMST)

On Tue, 17 Aug 1999, Leonid Pauzner wrote:

> 14-Aug-99 17:34 Vlad Harchev wrote:
> > On Sat, 14 Aug 1999, Vlad Harchev wrote:
>[...] 
> Hmm... could this be implemented via lists
> like downloaders and printers in LYReadCFG.c ?
> 
> Also, how about unifying things a bit?
> No lynx code knows about two diffrent options menu
> except LYOptions.c and LYK_OPTION in mainloop).
> Since you want to only mask the output in options menu
> most of new code should belong to LYOptions.c, isn't it?
> Or you want disabling them completely e.g. when reading .lynxrc etc.?
> Do you change charset numbers (see forms-based options menu in '/' source)
> or just mask them?

 If chset name is saved in "display chset" setting in .lynxrc, then this chset
name will be automatically added to the list of possible "display chset" 
choices. 
 The code builds 2 arrays of possible chset names (one for "assumed doc
chset", other for "display chset") and uses the names in these arrays as
labels either in form-based options or in menu-based options. The index map is
computed, that aids translating indexes of new popups (in nmenu-based options)
to indexes of real chsets. Seems no nuisances will arise.

 Since array (that is used as mask) is used, there is no need in constructing
lists (anyway, these lists will be thrown away after that mask is build). 

 I consider implementation as "reasonable".

>[...] 

 Best regards,
  -Vlad


reply via email to

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