www.cendio.com
Bug 83 - GUI to change all configuration files
: GUI to change all configuration files
Status: NEW
: ThinLinc
Web Administration
: pre-1.0
: PC All
: P2 Enhancement
: MediumPrio
Assigned To:
:
:
: 79 976
:
  Show dependency treegraph
 
Reported: 2002-08-12 14:23 by
Modified: 2016-11-22 11:03 (History)
Acceptance Criteria:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From cendio 2002-08-12 14:23:01
GUI to handle ID79
------- Comment #1 From cendio 2002-11-07 11:04:56 -------
The GUI should also allow changing other settings in vsmserver.conf and
vsmagent.conf. 
------- Comment #2 From cendio 2003-05-07 11:07:22 -------
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). 
------- Comment #3 From cendio 2003-07-10 13:39:20 -------
The configuration API is in place: Hiveconf. We still need to implement a GUI,
though. 
------- Comment #4 From cendio 2005-10-25 15:48:00 -------
Are there any difference between this bug and bug 976?
------- Comment #5 From cendio 2005-10-25 15:52:42 -------
>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. 
------- Comment #7 From cendio 2007-03-27 16:10:02 -------
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.

------- Comment #8 From cendio 2007-03-30 15:04:07 -------
Going for the basic approach: bug 976 + the ability to edit plain text files in
a simple interface. 
------- Comment #9 From cendio 2016-11-22 11:03:55 -------
*** Bug 976 has been marked as a duplicate of this bug. ***