Why? Prefs. for different components intermingled (et al)

[newton]

For example, when I connect to a remote daemon through the gtkui, I either a) don't want to see any of the 'network' preferences, or b) want to see the 'network' preferences for the remote daemon.

While I'm at it, I thank the developers for choosing to put configuration information in .config rather than immediately in my home directory, but what is the deal with these config files? It's next to impossible to edit them by hand. Can't we strive for a deluged.conf, deluge-webui.conf, deluge-gtk.conf, etc and have a simple "Option Value" or "Option=Value" syntax?

Are the developers accepting improvements in this area?

[johnnyg]

When you're connected to a remote daemon the network preferences you see are for the remote daemon not for the client.
The config files are in JSON format which is easy to edit IMHO and I don't see how deluged.conf, deluge-webui.conf and deluge-gtk.conf are much better than core.conf, web.cong and gtkui.conf.

[newton]

I installed the webui but don't see a web.conf. Even after "deluge -u web." In any event I'm not really concerned about the file names. Looking through the configuration files I think it's really difficult to figure out what setting is what. And I thought the format of a json file would be { "option": "value", "option2": "value2 } it doesn't look like this to me...

And as far as not realizing that I was actually look at the remote daemon's config settings in the gtkui, I hope you can at least understand where the confusion might be coming from. Is every single category in the preferences window for the daemon?

[andar]

We switched to JSON in 1.2-dev (trunk), the current 1.1.x branch still uses pickle which isn't very readable.

[johnnyg]

ah yes my bad, forgot only trunk uses json.

everything besides interface and notification is for the daemon.

[newton]

Thanks for the clarification.