[as-devel] Configuration File Format (again)
Sasha_Vasko@osca.state.mo.us
Sun, 12 Sep 1999 16:48:50 -0500
>Hi everyone,
> I want to have a discussion about the configuration file format of
>AfterStep again. I have decided that I'll do the configuration
>handling as time permits, as soon as we decide on what we want.
> I think before we decide how we'll layout the configuration files,
>we have to set our priorities concerning GNUstep. Do we want to be
>GNUstep compatible? If yes, then we should use PropList for
>configuration, because that is compatbiel with GNUstep. If not, then
>our configuration files don't belong in GNUstep (~/.afterstep/
>anyone?).
> If we choose to go either with an XML- or PropList-based
>configuration, then I will get started right away. Otherwise, I may
>not have the time needed to write a parser for a brand new
>configuration file format.
Guys, I'll tell you - I'm tired to go through this over and over without
any visible result. For the last time I'm wasting my time explaining
*official* configuration parsing policy of AfterStep. I say official as
I'm the only one who's done any coding in that direction, and allanon
supports my opinion on that issue.
1. No matter what file format or files location we'll be using we will use
unifyed parser code that I wrote in lib/parser.c.
2. This code was implemented in two layers - low level, config format
dependent level, but module independent,
and
high level - format independent, but module dependent.
3. High level primarily consist of syntax description for particular module,
as well as processing of the settings in context of this module. This whole
thig is implemented as libAsConfig in src/Config.
4. Low level driver for plain text file format as it is right now is implemented
in lib/parser.c and ready to use and is used by some modules(Pager and
aseroot).
5. High Level interface is implemented only for this two modules,
plus partially for MyStyle parsing and base config parsing.
6. It does not make any sene at all to go implementing yet another low
level interface, untill we finish implementing high level interface for ALL
config reading
in AS.
7. AS soon as we done with high level interface we can go ahead and implement
any number of low level drivers (selectable from configure) to our liking.
Bottomline:
You can bet your hard earned 100 bucks and send them to me, that no low level
config parsing code will make it in the distribution, untill we are finished
with
high level interface implementation. If anyone desires to help on that - take
a look at the code and ask me some smart (not stupid) questions - I'll be
happy to elaborate.
I hate to dissapoint everyone, but there is some hard work that needs
to be done, before we can procede to all kinds of fun stuff.
>-Steven
Best Regards
Sasha
P.S. : please let's see some real help before we proceed to any further
discussion on what sort of new neat features we all want to see in AfterStep.
Or I'll get mad and slam my keyboard in the screen, effectively disabling
myself from further contribution to AS development.