pafcu/configobj-gui

GUI for configuring configobj configurations

ConfigObj-GUI provides a PyQt based mechanism to edit ConfigObj configurations. It is intended to be used as a library to help configure PyQt based applications using ConfigObj.

Note that the library is not very robust yet as it has not been tested very much.

The basic usage is as follows:

import sys
from PyQt4.QtGui import QApplication
import configobj
import configobj_gui

app = QApplication(sys.argv)

spec = configobj.ConfigObj('yourspecfile', list_values=False)
conf = configobj.ConfigObj('yourconffile', configspec=spec)

wnd = configobj_gui.ConfigWindow(conf, spec)
wnd.show()

app.exec_()
print conf

Support the developer if you like this software:

configobj-gui's Issues

Selecting an option from a dropdown box does not take

When you select an option from a dropdown box, it doesn't trigger the usual routines. The GUI accepts it but the config does not change or get saved. If you hit the restore defaults button on the dropdown, it triggers some routines but still does not update the config.

Support for file path options

It's common to store file paths in configuration files, so the GUI should support those. Since ConfigObj does not support paths directly there are a few options how to do it:

1. Make a list of supported custom types that users have to use in their specs
2. Make it possible for users to specify a type->widget mapping, and let them create the widget class themself.

Support for multiple sections on one page

When there are only a few options in a section it does not make sense to make a completely new settings page. Instead settings should be grouped on the same page (e.g. with QGroupBox).

Support for tabs

If there are no nested sections it would be better to use a tab bar instead of a tree to view sections.

Support for file path options

It's common to store file paths in configuration files, so the GUI should support those. Since ConfigObj does not support paths directly there are a few options how to do it:

1. Make a list of supported custom types that users have to use in their specs
2. Make it possible for users to specify a type->widget mapping, and let them create the widget class themself.