[lcdproc] LCDproc v0.5 development, here we go folks :)
William W. Ferrell
wwf@frontierdev.com
Wed, 23 Aug 2000 16:49:58 -0600
--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Everybody,
Okay, we've talked about LCDproc v0.5 quite a bit, and methinks it's
time to actually start something.
I've spent the past half hour or so dorking around on SourceForge
setting up a few things. First I added some basic, high-level, probably=20
totally-wrong(tm) "tasks" for us to accomplish. Also added some groups
and categories to the bug tracker, and I'm sorting out how to set up CVS
for this new version of LCDproc. May as well do it correctly from the
start, eh?
Anyways, the first piece I thought should get done is the configuration
handling stuff. Command line parsing, config file parsing, and
environment variable parsing. Lots of parsing. Too much parsing :)
Folks have suggested gengetopt for the command line parser piece, and
that sounds good, so that'll be the first thing I'll dig into (unless
you'd like to steer me in another direction).
I imagine the environment variable and config file stuff will be similar
to each other in implementation, so how do we go about all that?
My goal is to be able to do something like the following, just about at
random (or more accurately, whenever *any* (reasonable) piece of LCDproc
needs to), and get a decent response:
lcd_contrast(device, config("devices", device, "contrast"));
I.e. multiple sections for different stuff (I'm thinking this is a
representation of the config, inside LCDproc, not in the config file):
server
basic
screen duration
frames per second
security
order =3D deny,allow
deny =3D all
allow =3D localhost
authentication =3D group
group =3D lcdproc
devices
device 1
driver =3D crystal fontz
contrast =3D 200
high backlight =3D 255
low backlight =3D 0
device 2
driver =3D curses
device 3
driver =3D x
scale =3D 1
background color =3D #0000BB
dot color =3D #000000
I'm kinda flailing, I think, since I think hashes would make this faster
but I've got no idea where to start.
Input?
Anyways, this is as good a place as any to start, so let's get to it! :)
Have a look at the little bit of stuff I've done on Sourceforge too and
toss comments at the list. Ridicule me, I can take it :)
--
William W. Ferrell, System Administrator, Global Crossing Ltd.
950 17th St Ste 2200, Denver, CO 80202 1.303.223.0564
=2E.. A booming voice says, "Wrong, cretin!", and you notice that you
have turned into a pile of dust.
--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjmkVRYACgkQgAeqhXR4/HqIwwCgi1v3Y1f1QUHXc/QkrPHpORW8
6mMAnjyt3QKXPWQP8WHv3saEG6CcPeMj
=m+hG
-----END PGP SIGNATURE-----
--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=
-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net
--6TrnltStXW4iwmi0--