On (11/16/07 19:29), Garrett D'Amore wrote: > > I vote for #1. +1
However, like Jenya, I'm still biased to the current gui itself --Sowmini > Jenya Gestrin wrote: > > More on GUI feedback: > > some reviewers expressed their disappointment with Properties Setting > > tab (see > > http://www.opensolaris.org/os/project/brussels/Documentation/proto6/). > > "...having to select the various properties in turn, and not being > > able to see the values of the others, would be very tedious..." > > > > I designed two possible solutions for this problem. > > *1. Properties as a table with the value column being editable. * > > > > Advantage: having all the options for each property on display would > > be more helpful for the administrator to make the selection. > > Disadvantages: > > a. due to the dialog window size constrain no more than 6 properties > > could be displayed at a time (scrollbar is introduced). > > b. numerous dropdown controls in the column are hard to comprehend and > > add visual noise. > > > > *2. Properties as a table with non editable value column. User selects > > property and clicks edit button to bring up an Edit dialog box. > > * > > Advantage: having all the options for each property on display would > > be more helpful for the administrator to make the selection. > > Disadvantages: Advanced (extended) dialog window appears on top of the > > Network Configuration window. Property Edit dialog window becomes > > another yet "layer" of dialog window. Even if we make it module, user > > ends up with three dialog windows one on top of another which makes it > > easy to get lost... > > > > Please review these options and send me your feedback. Personally, I > > think that what we proposed initially is still the best UI approach. > > > > Thank you > > Jenya > > > > ------------------------------------------------------------------------
