GUI to handle ID79
The GUI should also allow changing other settings in vsmserver.conf and vsmagent.conf.
Also, functions.sh should be handled. The problem with this bug is that, currently, vsmserver.conf and other config files are Python code. It's very hard to edit Python code programmatically, partly because one variable can span multiple lines. The ideal solution would be to design, implement and use a well-thoughout configuration API, but I'm not sure we can do that before 1.2. If not, we could make an interim solution: Add some minor restrictions to the config file format (like forbidding variables to span multiple lines).
The configuration API is in place: Hiveconf. We still need to implement a GUI, though.
Are there any difference between this bug and bug 976?
>Are there any difference between this bug and bug 976? Yes, bug 976 is about a generic Hiveconf too, pretty much regedit. The interface would be quite "crude" and not tailored for the a specific task. Again, pretty much like regedit. This bug, as I understand, is for a more customized GUI, specifically designed for configuring VSM.
This bug can be solved in many different ways depending on which ambition level we want. The lowest level is to simply implement bug 976 - a raw hiveconf interface. No documentation, no information about valid values etc - just a list of hiveconf parameters with input boxes without input validation. On the high end, the interface has descriptions, list of valid values, information on the type of the parameter, perhaps even dropdowns for some parameters that have a fixed set of permitted values. This variant, in my opinion, depends on bug 2433, as I don't want a *third* place for parameter documentation (.hconf files, TAG, and now this interface). In both variants, it should probably be possible to edit other configuration files - xstartup.default, et. al.
Going for the basic approach: bug 976 + the ability to edit plain text files in a simple interface.
*** Bug 976 has been marked as a duplicate of this bug. ***
