Hi Scott, > Sounds like you'll have one tag per directive. How will you accomodate new > directives that are part of new modules? Apache's ability to add new modules > dynamically (without recompile) seems really powerful, but accentuates the > need > for a very flexible/modular configuration program.
Well, yes and no :-) I was just simplifying Take for example directives that can accept on/off values. I just define a binary directive container (it will be a check box) and in the .ccf file I also define in which realm it can be found (inside <directory>, <location>, etc), which is the name of the directive (i.e cookie tracking ), a context help, etc Download the current version www.esi.us.es/~ridruejo/comanche and just have a look under ccf/ directory, you will see what I mean After this part I think I understand your point: > These ideas are work in progress, but here are my latest thoughts. The server > reads Module Description Files that contains the JML/GTKML description of the > GUI, module directives information (human readable description for help, > argument > types, valid directive contexts). Part of the one for mod_alias might look > like > this: > [A description (GTKML/JML) of the GUI form for displaying/collecting the > above directive/arguments goes here] It is what in a less general way I did for comanche. I do not want to go further that way because what it would lead to a "fill-in the blanks" GUI like comanche is as now. But I agree it would be interesting for building any GUI would be to have all this information explicily stated. Steffano from java-apache came with some good ideas in that field and he is going to bring some of them at ApacheCon. he told me he will be writing a summary of his ideas as soon as he gets some free time (which i doubt :-) he is doing a great work with java-apache and I guess it sucks up all his time) Quoting from him: " My proposal is to write an XML-like configuration description language (Apache Configuration Markup Language - ACML) that will be generated at compile time by all Apache projects. Configuration tools will be ACML browsers that will read these "configuration blueprints", prompt the user for information and generate a .conf file." (Mine: he explained later that the ACML will be some kind of XML + DTD The ACML browsers would be the actual GUI) Best regards Daniel -- ----------------------------------------------------------------------------- Daniel Lopez Ridruejo "Audaces fortuna juvat" E-Mail: [EMAIL PROTECTED] -----------------------------------------------------------------------------
