[yast-devel] results of yast style guide meeting on 22th january 2008
Hi everybody, at the end of the e-mail you will find a summary of results from the YaST style guide meeting on 22th January. The only issue which was not discussed directly is the filter issue (last paragraph) within the overview dialog. AFAIK filters in overview dialogs are only used in the user/groups management dialog. Currently the filter and the filter selection are separated, but Jiri found a very nice way to get rid of this separation (see Bug 279959). If you have any comments on the results of our style guide meeting, please let me know. For the next meeting on Tuesday, 29th January, 16 CET, we can take a look at the other full-screen dialogs: # Progress Dialogs (initializing, reading and writing...) # Dialog with Tabs # Tree Widget Dialog # Summary Dialog # Installation Proposal I think we can handle them quite shortly as it is mostly about: does it make sense how it is written down in: http://en.opensuse.org/YaST/Style_Guide/Dialogs Thanks for the discussion and your comments last Tuesday! Cu, Martin Properties of a common dialog * Help text is displayed via a help push button aligned on the left side. A click on the button opens the help text in a new window. On the right side the module dialog is displayed. * All navigation buttons are located at the bottom line of the common dialog. * By clicking the "x" in the window decoration the dialog closes. If the user changed something a warning pop up is display and has to be confirmed. Technically this means: UI WM_CLOSE button must be handled as "cancel/abort/close" * YaST modules should use the wizard.ycp (framework) * Unnecessary buttons (e.g. next in a one screen dialog) should be disabled Properties of an overview dialog * The heading consist of module name + "Configuration" if the dialog is used for hardware and services configuration * The items should be displayed in a table * If detailed information is necessary it is provided by a rich text field at the bottom of the table. The conten of the rich text field changes when the user changes the item in the table. * To configure the items within the table a set of three push buttons with the labels "Add", "Edit", "Delete" is used. These three push buttons are aligned at the left bottom. * To provide "expert options" or other settings like "set default" align the corresponding push button on the right. Try to avoid menu buttons or combo boxes as they hide their content from the user. * An additional line of buttons between the buttons at the bottom of the table and the navigation buttons should be avoided * If filtering is needed use the space above the table. The current filter is displayed as a text label on the left side, the "Set Filter" combo box is aligned on the right. -- Martin Schmidkunz User Experience Specialist martin.schmidkunz@novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (1)
-
Martin Schmidkunz