<snip scary plaintext example> > 1) Requires special parser which is too syntax sensitive > 2) Users editing the file could hose it rather easily compared to > existing formats. Ja I know I was teasing the "We want XML" crowd by going to the extreme in the opposite direction, trying to pull them back to the centre. > For a new config file, I personally think it makes the most sense > to use one of either: > > 1) XF86Config style file, and use libxf86config to parse it, > possibly extending the lib slightly as needed. I'd be perfectly happy with this.
> 2) One of the XML-is-my-favourite TLA ideas I'd be less than happy with this, XMHell is not my favourite thing. > Either one has a good arguement on both sides. You're trying to drive in the middle of the road, be careful. > Reinventing a new format though buys nothing. I'm of the faith > that good GUI/TUI config tools should be handling everything for > configuration. End user edited config files == bug reports out > the wazoo. I'd prefer to not ship some specialized config format > at all than to ship one that wasn't well thought out, and also > keeps the principle of least surprise. I couldn't care less whether there is or isn't a GUI / TUI configuration program. What I do care about is that the configuration files must be stored in a file which can be edited, run through a script, etc. All the configuration files on my box which I've ever had to edit / bothered to look, have never been in XML, and I don't see a good enough reason to start now. > KISS principle. Also, a bit of open source philosophy - reuse > what exists already, don't reinvent. Well I'd consider XML to not be simpler than XF86Config-4, besides which it is uneccessary, what happened to the "don't implement it if you don't need it" philosophy? cheers Liam ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
