Settings redesign -> Global Settings/Session Settings

[Tang]

You know, I usually keep my suggestions about new features to myself because I think Arne is doing an amazing job... However, this is one that I think would be very useful for nearly everyone.

I know this has been discussed before (settings for each hub), but I think this is a more feasable way to impliment the idea than how the threads I've read before try to go about it.

My ftp app of choice can be found here:
hxxp://www.vandyke.com/products/securefx/index.html

Download it and take a look at how you can define global settings that effect all the ftp sessions, and then define session settings that over-ride some of the global settings.

Now that you understand the method that I'm talking about.. The way I picture this being implimented (as a developer), is by having the settings exactly the same as they are now but with the added option of saving settings as session settings (only if there's an active connection). When I'm connected to a hub I can access the "session settings" and change things that I would like changed.. I can either save them as "global settings" or alternativly I can save them as "session settings". If I save them as session settings dc++ should save them under that hubs address to an xml config file (the same one as used now, or a different one -- either way).. The next time I connect to that hubs address dc++ reads the "session settings" section in the xml cfg and if it finds the address I'm connecting to it over-rides my current settings to the session settings defined for that hub.

The nice thing about this way of implimenting it is that you can specify different shares for any of the hubs you like to visit (because it would save all of the settings to the session xml cfg file), but it will use your default share for any hubs that you connect to that you haven't specified a different set of session settings.

This is the easiest way I can picture implimenting the feature. There's a few drawbacks to this, but I don't think it would effect performance in any major way. The major drawback is that if a user saved session settings for every hub in the public list the cfg file would be very large.

NOTE: this is an idea, not a request.. I think it would be nice to have, and I don't think it would be that difficult to impliment. I would like to hear feedback from the developers.

[GargoyleMT]

Well, it all depends on what you want done. It sounds like mostly you want a per-hub-share, or the ability to override your default one. I think, as long as every time you needed to give someone a list, that if a User structure is available, you could pull the hub out of there, and use that to select which list to send them.

What other settings would you do per hub? Description is an easy one (Arne has a patch from me for that in his mailbox).

Now, what about the border cases, like when you're on two or more hubs with someone who is also on those same hubs. Do you want to download two or three file lists to see their whole collection? File lists will have to take a different name too, maybe with the hub in parenthesis. The ShareManager class will have to grow in complexity too, to translate all of the filenames from all possible lists to regular filenames, and to keep track of which lists to search for what search terms.

In short, it doesn't look impossible, but it's not something I'm interested in adding, it doesn't fit my needs as a DC++ user nor tickle my fancy as a developer.