Hi,
I made some thoughts about the printer module.
The results can be shown on the wiki page, which had to be moved to
another location (due to some reorganizational stuff which I do not have
many clues off :-)).
The printer module redesign stuff is now available on:
http://en.opensuse.org/YaST/Development/Printer_Enhancement
I tried to avoid the term "queue" as I got some feedback on the ux-list
and in personal discussions and benchmarking, that this term is not
familiar to many users.
For the sake of consistency with other modules I also sacrificed
Johannes' sentences with included buttons, which I personally like a lot.
The CUPS settings also became a more semantic description.
I used the settings and wording of the CUPS browser UI and gave the user
the possibility to make detailed settings for some entries.
Open questions:
* Did I understand this correctly:
I can either use default settings of the remote CUPS server (which means
the default queue of the remote computer) or do I choose another queue
Missing stuff:
* select default queue (maybe this will be covered by a button at the
right bottom side of the local queue list)
* firewall settings (which I would put into the check boxes of the local
CUPS settings
* CUPS USB device settings (big question mark for me: do we really need
that? In case we do, it can become another check box in the local CUPS
settings
Did I miss anything else?
What do you think about these mockups?
Enojy the rest of the day,
Martin
--
Martin Schmidkunz
User Experience Specialist
martin.schmidkunz(a)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: opensuse-ux+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ux+help(a)opensuse.org
Hi,
some of you suggested that the official yast channel is not appropriate
for discussing style guide issues in an undisturbed manner, so we will
meet in the "styleguide" channel on irc.freenode.org
The meeting is scheduled for Tuesday, 29th January 2008, 16:00 CET until
17:00 CET.
World times for this meeting:
http://www.timeanddate.com/worldclock/fixedtime.html?day=29&month=1&year=20…
The agenda will be 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
We are looking forward to you,
Martin und Eva
--
Martin Schmidkunz
User Experience Specialist
martin.schmidkunz(a)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: opensuse-ux+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ux+help(a)opensuse.org
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(a)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: opensuse-ux+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ux+help(a)opensuse.org
Hi,
in discussions with some developers and during our own work it turned
out that it would be nice to have a style guide for YaST modules.
In order to get one, Eva and I will prepare single pieces of it, which
will be discussed with all interested persons on IRC.
That is probably the best method to give as many people as possible the
chance to participate in this project.
The meeting will take place in the yast channel on irc.freenode.org and
it is scheduled for Tuesday, 22th January 2008, 16:00 CET until 17:00 CET.
World times for this meeting:
http://www.timeanddate.com/worldclock/fixedtime.html?day=22&month=1&year=20…
We are looking forward to you,
Martin und Eva
--
Martin Schmidkunz
User Experience Specialist
martin.schmidkunz(a)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: opensuse-ux+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-ux+help(a)opensuse.org
