Sarah Jelinek wrote: > Frank Ludolph wrote: >> Jack Schwartz wrote: >>> Hi Sarah. >>> >>> On 07/31/09 10:33, Sarah Jelinek wrote: >>>> Hi Jack, >>>> >>>> I am a little late to this party, but I do have a question/comment >>>> which I believe have not been addressed in the current thread on this. >>>> >>>> -Use Case 2: >>>>> At boot time, user is presented with the "main menu": >>>>> 1. Run installer >>>>> 2. Install missing drivers >>>>> 3. Shell >>>>> 4. Reboot >>>>> >>>> So, in call cases is the user going to be presented with the >>>> 'install missing drivers' option? Or only if we have found drivers >>>> are missing at boot time? I am asking because having this option >>>> always there, implies to me anyway as a user, that I have missing >>>> drivers I need to install. Is there any way around having this >>>> option when there are not missing drivers? >>> When I talked about this with Frank, we decided to have this menu >>> look similar to the S10 install menu. >>> >>> I just booted S10 and see that it says "Apply driver updates", not >>> "Install missing drivers". I'll update my document with this >>> change. I think making this change will address your concerns about >>> implying (and not so subtly :) ) that drivers are missing when they >>> may not be. >>> >>> To answer your question, though, we could implement something to >>> show the "Apply Driver Updates" menu selection conditionally. We >>> could potentially implement the text-mode DDU with a silent mode >>> like we are planning for the GUI-based DDU. This would scan devices >>> like the DDU does today, but in the background. The text installer >>> could use this information to determine whether or not to display >>> the "Apply Driver Updates" menu item. Not sure if this will take >>> away needed functionality though; if someone hot-plugged a PCI >>> controller card while the system was up, a new device could >>> potentially show up after the scan determined not to show "Apply >>> Driver Updates". I suppose the user could just reboot... >>> >>> I think from a user-convenience standpoint, always showing the menu >>> item, but having it say "Apply Driver Updates" is the best choice. >>> What do you think? >>> >> The menu item might also be "Install additional drivers." Sarah was >> correct that the text should be as clear as possible, but it doesn't >> need to be finalized in this spec. > > Actually, it was more about having to offer it all the time, as > opposed to the specific wording of the item. I get Jack's concern > about having a loss of functionality: > > "if someone hot-plugged a PCI controller card while the system was up, > a new device could potentially show up after the scan determined not > to show "Apply Driver Updates". I suppose the user could just > reboot... " > > I don't want a loss of functionality. I am concerned about making this > always an option as it could be confusing to users. I am ok with > whatever Frank feels is the best user experience. I do have one > question though.. why are we not doing something similar for the GUI, > that is always having a menu option for this. What is the difference > in expected user experience? The ability to install drivers is currently an "aways there" option for current S10/Nevada users. And there is a menu option for this in the GUI - DDU is in the Applications>System menu as well as on the desktop.
The primary difference is that the GUI will automatically scan for missing drivers when the LiveCD starts up whereas the user will have to manually initiate the scan on the text-based media. I'm comfortable with that given the different target users and the notification facilities available (or lack thereof) on the two systems. Frank
