jezbo;259793 Wrote: > 1) So make it an option - everyone's happy. >
some, not everyone. for example: -QA who have to test every option -Support who have to keep track of every option and it's effects when helping customers diagnose an issue -Developers who have to continually track each option, and it's effects throughout the code any time some aspect of the feature changes, or have to replicate each option on the ever increasing interface paths (jive, cli, http, playerUI) and have to make each option act take effect immediately and completely. - Last but not least, Users - Those who are confused by the massive number of options and those who discover that their take on the option is that some other case is missing, or find that in fact the effect isn't immediate and they end up waiting for a scan. Also, the users who feel that the wrong option has been made the default. I'm not trying to enter a debate, or block the progress, but the idea that changes of this kind are simple doesn't properly address the reality of the issues. -kdf -- kdf ------------------------------------------------------------------------ kdf's Profile: http://forums.slimdevices.com/member.php?userid=7 View this thread: http://forums.slimdevices.com/showthread.php?t=42341 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
