A few more notes .... What I sent in the last mail was without looking at the existing files, to show how clear it could be ..
It could use a scheme-like syntax and be just as clear. New points are: 1. External programs easily. 2. Small, easy to comprehend files, each with a dedicated purpose. Lots of programs have huge config files, and a GUI to manage them. The GUI is a cover for the hugeness of the file. If there is a GUI to manage the config, it is important that the files can be manually edited also, and remain compatible with the GUI. The generated files must be easily readable, so they can be used to teach the text file format. The generated files should be at least as readable as good manually created files. Actually, that "GUI" is not necessarily graphic. Anything that wraps the real files fits. As an example .. "autoconf" and "automake" wrap the Makefile like a GUI but without graphics. It has the same problems as a GUI, hiding what is really happening, without the advantages. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
