Scott Dybiec said: > This is a tool that I prototyped to determine the feasibility of an > Apache module-based GUI, rather than one that is hard coded. Nothing > Apache-specific yet, though. There would need to be a corresponding > server side configuration tool that could have plug-ins for module, > scripts, etc. Thinking about XML for this. > > Looking for partners in this development. > > Your thoughts and comments are welcome. > > $cott
Hi Scott, It seems rather interesting. I am/have been working in something similar with Comanche. I will give you my (constructive :-) feedback I am working in a new (much improved) comanche version that will be presented at ApacheCon. I will be releasing some information later this week so you can have a feeling of how it is going to look like what Rich will present there Some of the objectives where: a) it should be extensible, so people can write their own modules for configuring , say, php or Apache SSL. People who do not use these modules will simply unset a check box somewhere and they will not appear b) The interface must be programatically designed. I already do something (primitive) with the current comanche version, with the .ccf files The interface changes acording to these files and to the version of Apache running (windows/unix). For the new comanche I take this much further: the layout is defined in something somewhat resembling XML (or your JML) which is loaded into a tree structure and from there the widgets are created. Basically I do the same that you do, but just in <> tags :-) So what you propose would turn into something like in comanche .ccf: <ComboBox> Name MyComboBox <ComboItem> Name Item1 Value Papaya </ComboItem> <ComboItem> Name Item1 Value Papaya2 </ComboItem> </ComboBox> With the difference that I will not be describing lists, comboboxes, etc but my widgets will be for example ServerName, which will be a widget with which you can change the servername in a configuration file People can rearrange the layout or build and new one just changing these new new .ccf files and extend the program declaring new widgets like ServerName2, etc Just one doubt: As I understand it, JML is used to describe the UI, How do you plan to add backend functionality to it? Finally, if you are interested in programatically implementing UI I would strongly recommend you to have a look at TCL/TK (www.scriptics.com) Best regards Daniel
