[yast-devel] redesign of printer module redesign
Hi everybody, a quite wise CUPS expert once said "exchange dungeons by trees" and that was an inspiration for me to take your feedback and make another series of mock ups: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Release_Candidat... What do you think about it? The first feedbacks revealed a great sense of confusion about the amount and design of information presented in the overview. Thats why the space acquired by help was used for an overview. (Help as such will not be dropped it will move to a button within the navigation area :-)) One thought was to hide "print via network", "sharing" and "CUPS autoconfig" under a "Settings" category, but this idea was dropped as the word "Settings" as such is quite meaningless. We also exchange "Remote Access" with "Share Printers" as this might be easier to understand. I am looking forward to your comments, 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi Martin! Thanks a lot for the proposal. Looks much less confusing, at least for me ;-) I have just one small note: Add Driver dialog: http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard.png Whouldn't Local PPD vs. Download PPD vs. Shipped drivers. Should they be kind of mutually exclusive? Stano Dňa Wednesday 06 February 2008 15:52:10 Martin Schmidkunz ste napísal:
Hi everybody,
a quite wise CUPS expert once said "exchange dungeons by trees" and that was an inspiration for me to take your feedback and make another series of mock ups: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Release_Candida te_2
What do you think about it?
The first feedbacks revealed a great sense of confusion about the amount and design of information presented in the overview. Thats why the space acquired by help was used for an overview. (Help as such will not be dropped it will move to a button within the navigation area :-)) One thought was to hide "print via network", "sharing" and "CUPS autoconfig" under a "Settings" category, but this idea was dropped as the word "Settings" as such is quite meaningless.
We also exchange "Remote Access" with "Share Printers" as this might be easier to understand.
I am looking forward to your comments,
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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 6 16:18 Stanislav Visnovsky wrote (shortened):
Add Driver dialog: http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard.png
Whouldn't Local PPD vs. Download PPD vs. Shipped drivers. Should they be kind of mutually exclusive?
Yes, they are mutually exclusive. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Feb 6 16:18 Stanislav Visnovsky wrote (shortened):
Add Driver dialog: http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard.png Whouldn't Local PPD vs. Download PPD vs. Shipped drivers.
OK, I changed the name to shipped drivers. http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard.png BTW: when a user selects one of the shipped drivers: wouldn't that mean that they disappear from the box? Keep it green, 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 6 17:06 Martin Schmidkunz wrote (shortened):
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard.png
BTW: when a user selects one of the shipped drivers: wouldn't that mean that they disappear from the box?
Somehow it must be shown which of the driver packages is already installed and which one can be installed. I don't care how this is shown to the user: - Gray-out those which are already installed? - Have the check-box preselected '[X]' when the driver package is already installed? - Don't show already installed driver packages at all? - Use a table or selection box or combo box or whatever with more verbose entries like "cups-drivers: various standard drivers (already installed)" "gutenprint: Gimp-Print/Gutenprint driver (not installed)" By the way: There is one entry missing: "filters: makeshift drivers for some awkward printers" For background information regarding "GDI printers", see http://en.opensuse.org/SDB:GDI_Printers Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi,
BTW: when a user selects one of the shipped drivers: wouldn't that mean that they disappear from the box? Somehow it must be shown which of the driver packages is already installed and which one can be installed.
I would like to replace the check box with a check mark. If a user uninstalls the package (via software management) the check mark turn into a check box again. See: http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard_selected.p...
By the way:
There is one entry missing: "filters: makeshift drivers for some awkward printers"
Mhm. Awkward printers... I think we should use: "filters: makeshift drivers for printers from HP, Lexmark, Canon, Citizen, and Apple" :-) (Source: package description of "filters") See: http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_driverwizard.png
For background information regarding "GDI printers", see http://en.opensuse.org/SDB:GDI_Printers
Thanks! Best regards, 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 7 10:01 Martin Schmidkunz wrote (shortened):
There is one entry missing: "filters: makeshift drivers for some awkward printers"
Mhm. Awkward printers... I think we should use: "filters: makeshift drivers for printers from HP, Lexmark, Canon, Citizen, and Apple" :-) (Source: package description of "filters")
Perhaps "makeshift driver" is sufficient information so that it is clear for the user that those stuff is only a makeshift for a few crappy printers. "filters" is not a general driver package for printers from HP, Lexmark, Canon, Citizen, and Apple. In particular for HP printers the general driver package is "hplip". Furthermore the above "for a few crappy printers" does not mean that most printers out there are well suppported by free software. It means that a makeshift is only available for a few of those many crappy printer models out there. Most crappy printers are simply not supported at all by free software. I.e. aviod plain wrong user expectations and avoid user complaints and/or bugzilla reports like: "I have installed all your drivers for printers from HP, Lexmark, Canon, Citizen, and Apple, but my Lexmark inkjet doesn't work! FIX YOUR DRIVER IMMEDIATELY - I NEED MY PRINTER WORK NOW!!!" Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Wed, 6 Feb 2008, Martin Schmidkunz wrote:
a quite wise CUPS expert once said "exchange dungeons by trees" and that was an inspiration for me to take your feedback and make another series of mock ups: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Release_Candidat...
Looks great! I like it, if I could represent any kind of our users :) Thanks, Michal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi everyone! Thanks for all your comments, suggestions, criticism and acclamations! 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz
Hi everybody,
a quite wise CUPS expert once said "exchange dungeons by trees" and that was an inspiration for me to take your feedback and make another series of mock ups: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Release_Candidat...
What do you think about it?
Better, waaay better ;-) - I wonder about the menu on the left side. IIRC this was already discussed (and dismissed !) some time ago and a tab-style approach preferred. Other functions can be placed in an application menu bar placed horizontally at the top of the window. - How about combining the "Filter: Show All" label and the "Set Filter" combo-box into one ? - The small tool icon is nice but probably information overflow. The "Local"/"Remote" column should be sufficient (together with disabling the "Edit" button for remote queues. - "Test Page" should be named "Print Test Page" - The "Status" column in unclear. Which information does it show ? - The "Back"/"Abort"/"Next" button row should just have a single "Ok" (or "Done" or ...) button. There's no point in aborting the overview imho. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi Klaus and all,
Better, waaay better ;-)
Thanks :-)
- I wonder about the menu on the left side. IIRC this was already discussed (and dismissed !) some time ago and a tab-style approach preferred. Other functions can be placed in an application menu bar placed horizontally at the top of the window.
I tried the application bar approach first and to be honest: it looked so bad, that I didn't even dare to send it around :-(
- How about combining the "Filter: Show All" label and the "Set Filter" combo-box into one ?
This solution has the possibility to include short cuts into the filter options. This would not be possible when using a combo box: https://bugzilla.novell.com/show_bug.cgi?id=279959
- The small tool icon is nice but probably information overflow. The "Local"/"Remote" column should be sufficient (together with disabling the "Edit" button for remote queues.
Mhm. Especially because the meaning of the tool icon is not instantly clear (Is the queue configured? Can I configure it?). It also pronounces the other icons (default, status) better. OK, changed.
- "Test Page" should be named "Print Test Page"
OK, changed.
- The "Status" column in unclear. Which information does it show ?
It shows the status of the print queue: check mark means: accepting print jobs and printing enabled x means: either one of the two conditions or both are not in place. Text was also the first idea we had, but it was too long and it required horizontal scrolling which is really, really nasty. So we decided to use icons. http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_modify_status.png
- The "Back"/"Abort"/"Next" button row should just have a single "Ok" (or "Done" or ...) button. There's no point in aborting the overview imho.
Navigation buttons in YaST are a long and big chapter, which also needs a lot of work. So I would like to discuss them at another time. Delayed but not to be forgotten! Have a nice evening, 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi all! Dne Thursday 07 of February 2008 16:52:19 Martin Schmidkunz napsal(a):
- The "Status" column in unclear. Which information does it show ?
It shows the status of the print queue: check mark means: accepting print jobs and printing enabled x means: either one of the two conditions or both are not in place. Text was also the first idea we had, but it was too long and it required horizontal scrolling which is really, really nasty. So we decided to use icons.
Hmm, what about to show text only if the queue is either disabled or does not accept jobs (and icon if enabled + accepting)? If one sees an 'x' icon, he has really no clue what it means unless we have tool tips. Since in most of the cases all queues are enabled and accepting jobs, it would show nasty scrollbar only in rare cases. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
On Sunday 10 February 2008 11:33:56 am Jiri Srain wrote:
Hi all!
Dne Thursday 07 of February 2008 16:52:19 Martin Schmidkunz napsal(a):
- The "Status" column in unclear. Which information does it show ?
It shows the status of the print queue: check mark means: accepting print jobs and printing enabled x means: either one of the two conditions or both are not in place. Text was also the first idea we had, but it was too long and it required horizontal scrolling which is really, really nasty. So we decided to use icons.
Hmm, what about to show text only if the queue is either disabled or does not accept jobs (and icon if enabled + accepting)? If one sees an 'x' icon, he has really no clue what it means unless we have tool tips. Since in most of the cases all queues are enabled and accepting jobs, it would show nasty scrollbar only in rare cases.
Jiri
IMHO. The status of printer (queue) in the overview table, from administrator prospective can be - configured - it is already set up to print, - enabled - you can print using that printer (queue) or - not configured - it needs to be configured or automatic configuration has to be reviewed and approved - disabled - either because a printer device reports error, there is no network, or administrator disabled access for instance because printer is bad and will be replaced with a same model, but not right now. I guess that creating one printer module for layman and enterprise administrator will be extremely hard, if possible. -- Regards, Rajko. See http://en.opensuse.org/Portal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dňa Sunday 10 February 2008 18:33:56 Jiri Srain ste napísal:
Hi all!
Dne Thursday 07 of February 2008 16:52:19 Martin Schmidkunz napsal(a):
- The "Status" column in unclear. Which information does it show ?
It shows the status of the print queue: check mark means: accepting print jobs and printing enabled x means: either one of the two conditions or both are not in place. Text was also the first idea we had, but it was too long and it required horizontal scrolling which is really, really nasty. So we decided to use icons.
Hmm, what about to show text only if the queue is either disabled or does not accept jobs (and icon if enabled + accepting)? If one sees an 'x' icon, he has really no clue what it means unless we have tool tips. Since in most of the cases all queues are enabled and accepting jobs, it would show nasty scrollbar only in rare cases.
Just keep in mind that the new UI supports icons all over the place, so let's use this functionality! Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi Jiri, hi all,
Hmm, what about to show text only if the queue is either disabled or does not accept jobs (and icon if enabled + accepting)? If one sees an 'x' icon, he has really no clue what it means unless we have tool tips. Since in most of the cases all queues are enabled and accepting jobs, it would show nasty scrollbar only in rare cases.
OK, having wording only in cases when the queue is not perfectly operational makes sense. It is much more obvious to the user what's the matter with the queue then having just an icon. I changed that in: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Overview_3 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz
OK, having wording only in cases when the queue is not perfectly operational makes sense. It is much more obvious to the user what's the matter with the queue then having just an icon. I changed that in: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Overview_3
Please don't mix icons with text information. Better find proper icons for the different states. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
I changed that in: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Overview_3
Please don't mix icons with text information. Better find proper icons for the different states.
The designing problem is, that there are four different states: * enabled, rejecting * disabled, accepting * enabled, accepting * disabled, rejecting for which I can only think of one to have an easy to comprehend icon. And that is enabled, accepting, which means "hey, everything is just fine." For the other three states there is no easy to comprehend icon (or at least I can't think of any) which means that the three icons need to be explained to the user in a legend somewhere. I fear that this will lead into the same usability problems we are facing with the software management where the user needs to learn a whole set of icons to work with the module. On the other hand having a mix of icons and text shows the user at a quick glance if something is not OK. The text tells him exactly what the matter is. What do you think is so bad mixing up icons and 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz
The designing problem is, that there are four different states: * enabled, rejecting * disabled, accepting * enabled, accepting * disabled, rejecting
So you 'just' need either four different icons or split it into two different columns (one for requested state, one for actual state). Btw, I do not think that accepting or rejecting really matters for a disabled queue.
What do you think is so bad mixing up icons and text?
A picture says more than a thousand words. Once you start with translations, text really becomes nasty for this kind of information. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 11 12:34 Martin Schmidkunz wrote (shortened):
Klaus Kaempf wrote:
I changed that in: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Overview_3
Please don't mix icons with text information. Better find proper icons for the different states.
The designing problem is, that there are four different states: * enabled, rejecting * disabled, accepting * enabled, accepting * disabled, rejecting
Please have also a look at my "experimental YaST printer module". I change it continuously according to what is currently going on (which does not mean that I implement everything exactly as the last wishes are - it is still experimental ;-) What about this text-only style: http://en.opensuse.org/Image:Printer_jsmeix_overview_all.png A simple "Ready" if all is o.k. and meaningful text otherwise. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Johannes Meixner wrote:
What about this text-only style: http://en.opensuse.org/Image:Printer_jsmeix_overview_all.png
An icon is much quicker to process by the human mind and it is much more salient if a column of icons is separated by text. So, lets please stick to Jiris suggestion. 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz
- I wonder about the menu on the left side. IIRC this was already discussed (and dismissed !) some time ago and a tab-style approach preferred. Other functions can be placed in an application menu bar placed horizontally at the top of the window.
I tried the application bar approach first and to be honest: it looked so bad, that I didn't even dare to send it around :-(
I'm mostly concerned about consistency across YaST modules. If the printer module now starts with left-side trees for navigation, how does it look for other modules ? IIRC, we had this discussion about 2 or 3 years ago and dismissed the left-side tree approach. Please check back with other members from the usability team.
- The "Status" column in unclear. Which information does it show ?
It shows the status of the print queue: check mark means: accepting print jobs and printing enabled x means: either one of the two conditions or both are not in place. Text was also the first idea we had, but it was too long and it required horizontal scrolling which is really, really nasty. So we decided to use icons.
Icons are fine, but its not clear to me what a 'big red X' means. Lets look at other icons to make the state clearer. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
I'm mostly concerned about consistency across YaST modules. If the printer module now starts with left-side trees for navigation, how does it look for other modules ?
This is done as well in Firewall, autoyast module. The partitioner will use it after the redesign as well.
IIRC, we had this discussion about 2 or 3 years ago and dismissed the left-side tree approach.
Is there any book, where I can read what was every considered or dismissed regarding YaST? That would help a lot :-) I had a short to talk to Eva and Sigi about that. The only thing this talk revealed was, that we once decided not to use trees when those trees become too complex (lets say more than 3 layers or something) and when the user would be forced to scroll horizontally. But I think that neither of these situations is given at present.
Icons are fine, but its not clear to me what a 'big red X' means. Lets look at other icons to make the state clearer.
According to Jiris suggestion I changed the "x" into some 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz
Klaus Kaempf wrote:
I'm mostly concerned about consistency across YaST modules. If the printer module now starts with left-side trees for navigation, how does it look for other modules ?
This is done as well in Firewall, autoyast module. The partitioner will use it after the redesign as well.
If this is the generally accepted (and 'usability' blessed) way of navigation, I'm all for it.
IIRC, we had this discussion about 2 or 3 years ago and dismissed the left-side tree approach.
Is there any book, where I can read what was every considered or dismissed regarding YaST? That would help a lot :-)
The book is called 'Sigi' ;-) Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
The book is called 'Sigi' ;-) :-)
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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi, first of all - I like this RC2. It seems to be clear and understandable (but there are some issues). Here is my comment: http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_overview_printvianetwor... o Do all Your ... please add there "Lookup", "Test server" buttons, ... from current version o Use a Network ... Should this be really a radiobutton? I think this is only one more printer queue and can be used together with one from above. http://files.opensuse.org/opensuse/en/8/89/Printer_mschmidkunz_rc2_overview_... [] Publish printers It should be something like "Publish printers by default" because this is global value which can be overwritten by each one individually http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_overview_autoconfig.png Automatic configuration - some words are here : FaTE #120084 http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_addlocalqueue.png I don't like "Print Test Page" checkbox idea.This can be done manually in overview with "Test Page" button. http://files.opensuse.org/opensuse/en/3/38/Printer_mschmidkunz_rc2_modify_sh... [] Exclude From Publishing ... Show also current global value That's all from me for now Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi Michal, hi johannes,
first of all - I like this RC2. It seems to be clear and understandable
Cool!
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_overview_printvianetwor... o Do all Your ... please add there "Lookup", "Test server" buttons, ... from current version
OK, done.
o Use a Network ... Should this be really a radiobutton? I think this is only one more printer queue and can be used together with one from above.
Good point! Johannes and I realized that way there are some button problems in "Share Printers", "Add Drivers", "Print Via Network" dialog pages. I will come up with a redesign as soon as possible.
http://files.opensuse.org/opensuse/en/8/89/Printer_mschmidkunz_rc2_overview_... [] Publish printers It should be something like "Publish printers by default" because this is global value which can be overwritten by each one individually
OK, done (but not yet on opensuse, as the whole dialog needs some additional adjustments)
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_overview_autoconfig.png Automatic configuration - some words are here : FaTE #120084
Thanks for the information! Currently only values from etc/cups-autonconfig are shown. But maybe we can add something like: "[ ] Do not Configure PostScript Capable Printers Automatically" What do you think?
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_addlocalqueue.png I don't like "Print Test Page" checkbox idea.This can be done manually in overview with "Test Page" button.
OK, removed. The idea was that some users might like to print out something directly after adding a new queue, but I think that it is sufficient to provide this via the button in the overview.
http://files.opensuse.org/opensuse/en/3/38/Printer_mschmidkunz_rc2_modify_sh... [] Exclude From Publishing ... Show also current global value
It seems that this global value for publishing is quite a complex matter. Johannes said, that he need to think this through for himself. Thanks for your comments and have a nice weekend! 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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 8 16:11 Martin Schmidkunz wrote (shortened):
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_overview_autoconfig.png Automatic configuration - some words are here : FaTE #120084
Thanks for the information! Currently only values from etc/cups-autonconfig are shown. But maybe we can add something like: "[ ] Do not Configure PostScript Capable Printers Automatically"
What do you think?
Of course this is only possible if cups-autonconfig supports it.
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_addlocalqueue.png I don't like "Print Test Page" checkbox idea.This can be done manually in overview with "Test Page" button.
OK, removed. The idea was that some users might like to print out something directly after adding a new queue, but I think that it is sufficient to provide this via the button in the overview.
The crucial point why it must be removed is: When a wrong driver was selected (or automatically assigned), the printer may spit out zillions of sheets with meanigless characters. When the "Print Test Page" checkbox is enabled by default, the user may not notice it and become angry when his printer suddenly spits out sheet after sheet. Therefore to be on the safe side, the checkbox would have to be disabled by default but then it would be useless because it is same "effort" to do it in overview with "Test Page" button. Therefore I agree that the "Print Test Page" checkbox is bad.
http://files.opensuse.org/opensuse/en/3/38/Printer_mschmidkunz_rc2_modify_sh... [] Exclude From Publishing ... Show also current global value
It seems that this global value for publishing is quite a complex matter. Johannes said, that he need to think this through for himself.
Currently I don't know what happens if "DefaultShared no" in /etc/cups/cupsd.conf but "Shared yes" in /etc/cups/printers.conf. What a terrible wording: "Shared" actually means "Published" here. I would like to show to the user if a particular queue is actually published or not but currently I am confused what which settings in the CUPS config files actually results. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (8)
-
Jiri Srain -
Johannes Meixner -
Klaus Kaempf -
Martin Schmidkunz -
Michal Svec -
Michal Zugec -
Rajko M. -
Stanislav Visnovsky