EdgeList Database Configuration is not saved

I would like to propose a patch I was working the last days while I am getting used with the environment.
Any suggestions about improving it are welcome!

Great, I tried your patch it works but I have maybe a suggestion?

The best wouldn't be to save the configuration automatically instead proposing it to the user ?

I explain: The user enters a configuration, with a configuration name (important) and all details. When he hits OK the configuration is saved. Then when the window is opened again the configuration has appeared in the configuration combo-box. If he changes the configuration name that creates a new configuration, or just save the details otherwise. Does that makes sense?

I think it provides better user experience than letting users manage configuration files.

I'm attaching a new patch with Mathieu's suggestions, and other improvements like better internationalization and exception handling.

Sorry, the last patch was incomplete. This one is complete.

Sorry, the last patch was incomplete. This one is complete.

Great it works nicely, thank you.

I committed in the trunk in rev 1405.

Before committing I made a small change on Remove Configuration button. It has now an icon and is enabled/disabled instead of visible/hidden. I think this is more logical for users.