Hi Frank, Many thanks your hard work!
I'm not quite sure about the F4 key pressing functionality. From my understanding, there are two main areas in the screen(area1,area2), when user stay in one of these two areas, some function key like key-up/key down will only work within this area. TAB key will be used for switch between these areas. what's the purpose for F4? Also for F5 functionality(F5-Repository), will this key pop-up a new dialog on this main window or just clear this window and display the Repository information in the same screen? Please correct me if I am missing something, Thanks! Zhongyuan ?2009?09?11??07:04?Frank Ludolph??? > As mentioned at yesterday's meeting there are three alternatives that > could be used for the text-based, install time DDU. > > * Single screen nCurses (attached) > o Advantage: Everything visible, like a GUI > o Disadvantage: Kind of ugly, function keys, more difficult to > implement > * A console-based wizard > o Advantage: More familiar to terminal users > o Disadvantage: Lots of reading up the screen > * A DDU CLI > o Advantage: A DDU that can be used from the command line at > any time, even after install. > o Disadvantage: Requires learning the commands > > The following are very rough designs to illustrate the above approaches, > not finished designs. > > *Single Screen nCurses* > > This operates pretty much like the GUI: (see attached > > * User selects a device, DDU DB info, if any, is filled into the > input fields below. > * If no DB info, the user types in file pathname or repo URL and > package name. > * F<key> installs, then the driver list is updated. > > * > Console-based wizard* > > The wizard might go something like this: > > (user enters the number of the DDU task in the installation task menu) > > The install-time Driver Update Utility is used to install drivers not > available on the > installation media. Drivers can also be installed following installation if > they are > not required by the installer. > > The following devices are missing drivers: > > 1. Audio Intel Corporation 82801DBBBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio > Controller > 2. Network Atheros Communications Inc. Atheros AR5001X+Wireless Network > Adapter > > Enter the number of the device to install its drivers, or 'q' to quit: *1* > > A driver is available from www.intel.com/drivers/ICH4. Install? [y, n, q]: *y* > > Installing...................Done > > The following devices are missing drivers: > > 1. Network Atheros Communications Inc. Atheros AR5001X+Wireless Network > Adapter > > Enter the number of the device to install its drivers, or 'q' to quit: *1* > > Install from a local file? [y, n, q]: n > Install from a repository? [y, n, q]: y > > Known repositories: > 1. opensolaris.org/release > 2. opensolaris.org/contrib > > Enter the number of a known repository or a repository URL: pkgs.atheros.com > Enter the name of the driver package: ar5001x > > Installing....................Done > > All devices have drivers installed. > > > * > > A DDU CLI* > > (user enters the number of the DDU task in the installation task menu) > > jack> dduadm > list > install -d devicenum [-f pathname]|[-r repositoryNumOrURL -p packageName] > repos > > > jack> dduadm list > 1. Audio Intel Corporation 82801DBBBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio > Controller > 2. Network Atheros Communications Inc. Atheros AR5001X+Wireless Network > Adapter > > jack> dduadm install -d 2 > no driver information available > > jack> ddu repos > Known repositories: > 1. opensolaris.org/release > 2. opensolaris.org/contrib > > jack> dduadm install -d 2 -r pkg.atheros.com -p ar5001x > Installing......................Done > > jack> dduadm list > 1. Audio Intel Corporation 82801DBBBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio > Controller > > jack> dduadm install -d 1 > Installing......................Done > > jack> exit > > (returns to the installation task menu) > > Comments? (I'll be out of the office tomorrow and will respond on Monday.) > > Frank > > * > > * -------------- next part -------------- A non-text attachment was scrubbed... Name: v1.png Type: image/png Size: 10259 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090911/6750b183/attachment.png>
