Hi everybody, Johannes came up with some additional ideas how to redesign the add dialog and the printer module. I put the screenshots on: http://en.opensuse.org/YaST/Printer Please note, that they contain some experimental stuff like semantic buttons. Although I find this idea very interesting and cool (as it brings in the thoughts of hyperlinks) it will be most likely that they will not survive the whole design process :-) Cu, Martin -- 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: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
On 10/12/2007, Martin Schmidkunz <mschmidkunz@suse.de> wrote:
Hi everybody,
Johannes came up with some additional ideas how to redesign the add dialog and the printer module.
I put the screenshots on: http://en.opensuse.org/YaST/Printer
Did you also see the mockup someone did at http://en.opensuse.org/Yast_UI_Future#Hardware_Listing ? I think it would be nice to have a less busy dialogue like this, with drill-down to further detail. Have you also considered the terminology to be used? e.g how many users understand or want to/need to the concept of a print queue, vs "I send it to the printer, and it is printed eventually"
Please note, that they contain some experimental stuff like semantic buttons.
Any reference on what a "semantic button" is? It isn't immediately obvious from the screenshots. Do you mean buttons like modify/delete in the example? -- Benjamin Weber -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Hi Benji,
Did you also see the mockup someone did at http://en.opensuse.org/Yast_UI_Future#Hardware_Listing ?
Looks quite tiny :-) But seriously: the mock up is copies exactly the design we want to get rid of. That is that CUPS settings are hidden behind an "Other" button.
I think it would be nice to have a less busy dialogue like this, with drill-down to further detail.
Have you also considered the terminology to be used? e.g how many users understand or want to/need to the concept of a print queue, vs "I send it to the printer, and it is printed eventually"
Not yet. The point is that this needs to/should be decided by involving others (e.g. docu, product management,...) So at first we want to make a nice design and then we can discuss the wording.
Any reference on what a "semantic button" is? It isn't immediately obvious from the screenshots. Do you mean buttons like modify/delete in the example?
If means that there is a sentence which explains possible actions to the user. The possible actions are highlighted by buttons. In fact it is a mesh up of buttons and help text :-) Cu, Martin -- 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: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Hello, On Dec 10 17:51 Benji Weber wrote (shortened):
Did you also see the mockup someone did at http://en.opensuse.org/Yast_UI_Future#Hardware_Listing ?
A printer management tool cannot exist because there is no printer in the printing system. See http://lists.opensuse.org/opensuse-ux/2007-11/msg00005.html and http://lists.opensuse.org/opensuse-ux/2007-11/msg00025.html and http://www.cups.org/newsgroups.php?s1+gcups.general+Q%22Keep+printer+device+... and http://www.cups.org/str.php?L2531
... e.g how many users understand or want to/need to the concept of a print queue, vs "I send it to the printer, and it is printed eventually"
See http://lists.opensuse.org/opensuse-ux/2007-11/msg00005.html
Any reference on what a "semantic button" is?
See http://lists.opensuse.org/opensuse-ux/2007-11/msg00025.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Hello, On Dec 10 18:15 Martin Schmidkunz wrote (shortened):
Johannes came up with some additional ideas how to redesign the add dialog and the printer module.
I put the screenshots on: http://en.opensuse.org/YaST/Printer
The content was moved to http://en.opensuse.org/YaST/Development/Printer_Enhancement where it is under "Suggestion 2". The "Modify existing queue" is currently under implementation. The current screenshot comes from an inconsistent work-in-progress stage on the particular workstation where I implement it. Note, that I feel free to use any experimental stuff I like, e.g. any wording I like most (e.g. "modify" instead of "edit") and/or any button placement I like most (e.g. "Add" at the right where also "Next" is) and so on and so on.
Please note, that they contain some experimental stuff like semantic buttons.
I.e. No longer plain buttons like [More Drives] [All Drivers] [Driver Wizard] but now enriched with some text: If no suitable driver is shown, try [More Drives] or [All Drivers] or use the [Driver Wizard]
Although I find this idea very interesting and cool (as it brings in the thoughts of hyperlinks) it will be most likely that they will not survive the whole design process :-)
One problem is translation. But I think there is a solution: 1. Make sure that there is a text before and after each button (even if such a text might be empty for the English language) so that the translator should be able to compose a correct text line for any arbitrary language (e.g. a language which reads from the right to the left). 2. Provide the translation strings for each "semantic buttons line" in one continuous source code block with a descriptive comment so that the translator understands which strings and buttons compose which "semantic buttons line". Another problem is broken display of long "semantic buttons" lines in a too small ncurses window. The above example looks on a 80x25 ncurses window like this: If no suitable driver is sho[More][All D] or use[Driver W] I think there is also a solution: Check if it runs in ncurses mode (e.g. via misuse of the function UI::HasSpecialWidget) and if it runs in ncurses mode, show only the plain buttons. I think it would be bad if "semantic buttons" would not survive the whole design process because we do need semantics, see http://lists.opensuse.org/opensuse-ux/2007-05/msg00087.html Of course any other design which supports semantics is also welcome - provided the usability experts find one ;-) Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Dňa Tuesday 11 December 2007 12:45:18 Johannes Meixner ste napísal:
One problem is translation.
But I think there is a solution:
1. Make sure that there is a text before and after each button (even if such a text might be empty for the English language) so that the translator should be able to compose a correct text line for any arbitrary language (e.g. a language which reads from the right to the left).
2. Provide the translation strings for each "semantic buttons line" in one continuous source code block with a descriptive comment so that the translator understands which strings and buttons compose which "semantic buttons line".
This is not enough. For example, some languages have rules what form can be the button text, e.g. infinitive only. In that case, your sentences might be almost completely untranslatable. Please, discuss this at opensuse-translation first, this is a showstopper for most of the translation teams. Never break sentences! Stano -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Hello, On Dec 11 12:59 Stanislav Visnovsky wrote (shortened):
Dna Tuesday 11 December 2007 12:45:18 Johannes Meixner ste napísal:
One problem is translation.
But I think there is a solution:
1. Make sure that there is a text before and after each button (even if such a text might be empty for the English language) so that the translator should be able to compose a correct text line for any arbitrary language (e.g. a language which reads from the right to the left).
2. Provide the translation strings for each "semantic buttons line" in one continuous source code block with a descriptive comment so that the translator understands which strings and buttons compose which "semantic buttons line".
This is not enough. For example, some languages have rules what form can be the button text, e.g. infinitive only. In that case, your sentences might be almost completely untranslatable.
Why? Of course the button text is also one of the strings. For example: string left_of_button1 = "This is"; string button1 "button 1"; string between button1_and_button2 = "and"; string button1 "button 2"; string right_of_button2 = "is the last button."; result this "semantic buttons line" This is [button 1] and [button 2] is the last button. What is the problem for the translator here? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
Dňa Tuesday 11 December 2007 14:04:02 Johannes Meixner ste napísal:
Hello,
On Dec 11 12:59 Stanislav Visnovsky wrote (shortened):
Dna Tuesday 11 December 2007 12:45:18 Johannes Meixner ste napísal:
One problem is translation.
But I think there is a solution:
1. Make sure that there is a text before and after each button (even if such a text might be empty for the English language) so that the translator should be able to compose a correct text line for any arbitrary language (e.g. a language which reads from the right to the left).
2. Provide the translation strings for each "semantic buttons line" in one continuous source code block with a descriptive comment so that the translator understands which strings and buttons compose which "semantic buttons line".
This is not enough. For example, some languages have rules what form can be the button text, e.g. infinitive only. In that case, your sentences might be almost completely untranslatable.
Why?
Of course the button text is also one of the strings.
For example: string left_of_button1 = "This is"; string button1 "button 1"; string between button1_and_button2 = "and"; string button1 "button 2"; string right_of_button2 = "is the last button."; result this "semantic buttons line" This is [button 1] and [button 2] is the last button.
What is the problem for the translator here?
Wrong list, use opensuse-translation, please. Stano -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
participants (4)
-
Benji Weber -
Johannes Meixner -
Martin Schmidkunz -
Stanislav Visnovsky