[lcdproc] XML discussion

[William W. Ferrell]

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Matt (madmatt@bits.bris.ac.uk)'s mailer blew these chunks:
> I've found a library on freshmeat for parsing .ini-style files, it's
> called parsecfg. I've not had chance to look at it, but if someone wants
> to see if it's any good...
>=20
> It seems we're going in circles a bit with regards to the config format.
> One person says "Yuck, Windows .ini files suck, XML is better", and
> everyone wants to use XML, then someone else says "Yuck, XML files suck,
> .ini files are better", and we go back to .ini files.
>
> Personally I'm not too bothered either way, as long as it works. But if we
> could just decide...

I think I'll stick with .ini for now. libxml annoyed me :)

> Something we should also try and work out is an interface for the driver
> code. If the driver is in a separate package, we need a good clear
> interface that every driver will be able to adhere to comfortably. What
> functions are we going to need in each driver?

Well, at a minimum, the driver just needs to be able to draw whatever
framebuffer is handed to it onto the device it's driving.

If the framebuffer contains more stuff, like contrast, custom
characters, etc., and the driver chooses to ignore or not support it,
fine.

> I can see that we might want a function to get the capabilities for the
> particular driver, which we could then use to work out what else we could
> do, functions allowing. Or, just write empty functions where that action
> is not supported...

So do we just silently ignore unsupported calls from the server in the
driver, or do we make drivers report their capabilities to the server
then tailor the server's behavior accordingly?

--
William W. Ferrell, System Administrator, Global Crossing Ltd.
950 17th St Ste 2200, Denver, CO 80202   1.303.223.0564

Anyone who goes to a psychiatrist ought to have his head examined.
		-- Samuel Goldwyn

--J2SCkAp4GZ/dPZZf
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

iEYEARECAAYFAjmnFLkACgkQgAeqhXR4/Hrm9ACguzMMbJ+qAvLkLQeM2NztKzaK
ozMAoLSTBFySfsZntyPZJlEPCLj7elAD
=Ofi5
-----END PGP SIGNATURE-----


--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=


-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net
--J2SCkAp4GZ/dPZZf--