> I understand your point, but if you'd do all this, then you'd end up > with a debugging tab that is so overused that it has to be devided into > several sub-tabs, i.e. GnutellaNet, Bandwidth, Download and misc. > And voila, your almost exactly where you started :-)
The main thing users want to change (I think) is bandwidth allocation and upload/download locations. This isn't trivial in the current UI because of the jargon used and the cluttered options everywhere. If I want to assign for example 20KByte/s upload to gtk-gnutella I have to change settings in 3 different bandwidth sliders, and toggle a few buttons. And then I'm still not sure if it's right due to the complex wording if you're not into filesharing/gnutella jargon. What's an ultrapeer? What's gnutellanet traffic? What's a leaf? What's HTTP traffic? I'm not a web server, am I? > But there is already a checkbox in the preferences where you can toggle > expert mode. If this is off (which should be off by default), then some > of the many options are hidden. I agree that this should be more > heavily used, so that most of the options you named should be affected > by this switch. Indeed, many options can be folded in expert mode. Why should a casual user have to change the amount of legacy connections or amount of leaves? Why bother about overlapping bytes? Pick a sensible default, and twiddle in expert mode (or in the config file) if needed by experts. Hein-Jan ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
