http://defect.opensolaris.org/bz/show_bug.cgi?id=12593
--- Comment #14 from Lin Ma <lin.ma at sun.com> 2009-12-11 05:16:17 UTC --- (In reply to comment #13) > Created an attachment (id=3196) [details] > Possible ways to show nsswitch filename > > Okay, so it sounds like the GUI logic is: > > if only one service checked > > if nameservices-config-file = default for this service > show (None) in file selection button, and disable Default button > else > show config filename in file selection button, and enable Default button > > else > show config filename in file selection button, and disable Default button > > Re the label for the Default button name, yes, I'd thought about "Use Default" > too, but initially discounted it. After sleeping on it, I agree it might > actually be the best option. > > Have attached a mockup of how we might show the filename. I think it's > probably > more useful to show something slightly different for each of the three > scenarios: > > * One service, default config file in use: show full pathname to default > config > file > > * One service, custom config file in use: show full pathname to the default > file that will be selected if you click the Use Default button. (We could > perhaps show full pathname to custom file as well, but since you can also get > this by clicking the file selection button, I'm not sure if it would be more > confusing than helpful.) > > * Multiple services: Not sure we really need to show anything at all. (Again, > we could show full pathname to the custom file. If we do that for previous > case, should probably do it for this one too.) > > I have the feeling we could find some better wording for the first two > cases... > the 'in use/not in use' wording seems clunky. Looks great. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
