https://bugzilla.novell.com/show_bug.cgi?id=468046
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=468046#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsmeix@novell.com,
| |mzugec@novell.com
Platform|x86-64 |All
Component|YaST2 |Usability
AssignedTo|bnc-team-screening@forge.pr |mschmidkunz@novell.com
|ovo.novell.com |
QAContact|jsrain@novell.com |qa@suse.de
Summary|printer Kyocera FS-1020D is |Misleading Add/Modify
|detected, but not |dialog in yast2-printer
|automatically installed |when it initially finds no
|using yast2 |driver
Severity|Normal |Major
--- Comment #2 from Johannes Meixner 2009-01-22 02:23:34 MST ---
Your report in bug #467172 was misleading.
I thought it is about that you report
that there is no longer a driver which
is invalid because actually we provide
the same driver as before.
Regarding this new report:
It is the most often reported issue that
the dialog in attachment #266614
is misunderstood by the user when
YaST initially didn't find a matching driver.
It seems many users misunderstand the
"No matching driver found"
message in YaST as an ultimate final statement
that there exists no driver for this model
but actually the message means exactly what
it reads, i.e. that YaST did not find a driver
which matches to the directly above shown model string.
In attachment #467172 the upper table shows
in the "Modell" column the value what the printer
hardware itself reports via the USB.
Only this value can be used by YaST to find a matching driver.
When there is another model value used in the printer
description files (PPD files), YaST cannot find a matching
driver and all you can do is to manually search
for a matching driver.
YaST cannot fix such kind of non-matching values.
It could only be fixed by those who make the driver
with its associated PPDs which is here the printer
manufacturer Kyocera and I already explained in
https://bugzilla.novell.com/show_bug.cgi?id=467172#c3
how this mess was caused by Kyocera itself.
The dialog in attachment #467172 was designed together
with our usability experts and implemented accordingly.
For background information you may have a look at
http://en.opensuse.org/YaST/Development/Printer_Enhancement
and compare the final design
http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_addlocalqueue.png
with one of my experimental proposals
http://en.opensuse.org/Image:Printer_jsmeix_add.png
and even before this one I had a [More Drivers] button
in my experimental module so that it looked initially like
--------------------------------------------------------------------------
Assign Driver:
|ACME FunPrinter 1200| [Show matching Drivers] [More Drivers] [Add Driver]
__________________________________________________________
|No matching driver found
|
--------------------------------------------------------------------------
The [More Drivers] functionality was simply to remove the last
word of the model string so that after clicking [More Drivers]
it could look like
--------------------------------------------------------------------------
Assign Driver:
|ACME FunPrinter | [Show matching Drivers] [More Drivers] [Add Driver]
__________________________________________________________
|No matching driver found
|
--------------------------------------------------------------------------
After one more clicking [More Drivers]
it could look like
--------------------------------------------------------------------------
Assign Driver:
|ACME | [Show matching Drivers] [More Drivers] [Add Driver]
__________________________________________________________
|ACME Fancy Printer 1000
|ACME Funny Printer 2000
--------------------------------------------------------------------------
The last fallback (when nothing matches to the first word
which is usually the manufacturer name) is to show
the full list of all available drivers.
I.e. in any case clicking [More Drivers] several times
results eventually a list of drivers.
I re-assign the issue to our usability expert
because it is no bug in YaST (it is implemented
according to the current design) but a usability issue
if the current design provides good usability.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.