On Thu, 15 Jun 2000, Dekel Tsur wrote:
> To be more specific, lyxrc.C should contain a big array with entries for the
> lyxrc variables, each entry contains information like token name, default
> value, etc. Another field will be type (e.g. "printer", "screen fonts", etc.)
> which will be used for building the form automatically.
>
I'm thinking about writing this soon, unless someone else wants to do it.
Internally, the design might be a hash table mapping strings to entries,
and the extrnal interface should be something like:
string LyXRC::query_string (string & key)
bool LyXRC::query_boolean (string & key)
etc.
I think the entries should have a type in the regular sense (integer,
string, ...), while the above "type" is better termed a "family".
Keybindings can be handled by having the "bind" entry in the table be an
object which performs keybindings (rather than have an instance for each
keybind). The same should go for other bindings (e.g. reading a bind_file
or setting colors).
Lior.
