From: Robin S. <li...@re...> - 2003-09-27 18:19:44
|
On Saturday 27 September 2003 17:19, Markwayne wrote: > Robin Szemeti wrote: > > I'll still vote for a seperate .spec file with help links, variable > > types, minimum and maximum values etc seperate from the ini. this will > > allow it to be used against existig ini files and also allow it to be > > updated independently of the ini files as emc develops > And put all of that in XML right Robin? we could even call it a DTD and use somehting like OpenJade to validate the document agaisnt it ... however as XML seems to be a leap too far for some, lets re-invent that particular wheel I was actually going to suggest that we stick to something a little more basic ... Some time ago I became frustrated with the ini file, and used some Perl to parse out all the variables into a data structure I stored on disc, and then produced a web page that I began to update with the assistance of others .. until we discovered that most of the documentation was already done in the new handbook. I propose that the datastructure itself well make an ideal index/spec it already contains every variable and a (mostly blank) space for a 1 line description ... with the addition of a field for int/float min and maximum limits and link to the handbook entry, I'll happily write a bit of Perl to output that data in any form you like from C to Tcl, once the data is in a structure form its trivial to convert it to another form. I have not the enthusiasm for the tedious task of making all those entries, but if some kind soul wishes to do that part, I'll make a perl program that whisltles through an ini file and points out any out-of-limits or missing entries along wiht a description of what it does, type and limits ... any takers? I'll commit the data file to SF tonight and then anyone with the enhusiasm for it can update it. -- Redpoint Consulting Limited Real Solutions for a Virtual World http://www.redpoint.org.uk |