Simplify local front-end mode: Let the user select the configuration file
(instant messenger conversation)
Just had an idea: in the local front-end mode, we basically don't need the XMLRPC connection details (password, port etc.), but only the location of the active configuration file. That's where LottaNZB can extract all necessary information to connect to the already running daemon
I added a file selection button to the mode selection window anyway, so that LottaNZB knows, where the download directory is in the local front-end mode. Are there usage scenarios where this approach won't work?
There would even be another advantage: If the user changes the password or the port the HellaNZB daemon listens to he/she doesn't need to tell this LottaNZB...
The hellanzb executable accepts the arguments "r", "s" and "p" which are used to overwrite the XMLRPC connection information in the config file but I don't see any reason to use this feature...
Blueprint information
Whiteboard
Work Items
Dependency tree
* Blueprints in grey have been implemented.