DDU team, Will Walker, our accessibility specialist, would like to talk with you about making the DDU GUI accessible. A considerable effort has been made to make the LiveCD and GNOME desktops accessible. DDU has a prominent position on the desktop and is intended as the primary means for an individual to determine how well OpenSolaris can work on the user's machine, so it is appropriate to insure the accessibility of the DDU.
Perhaps Will and Liyan can set an initial discussion. I realize that the team is under schedule pressure and Oct 1-8 is a China national holiday break, but it would be good to at least meet to get things started. Frank Jack Schwartz wrote: > Attendees: Frank. Bill, Zhongyuan, Liyan, Sundar, Tony > Host: Jack > > === Status and general technical discussion: > > GUI mode DDU > ------------ > > GUI mode DDU is code complete and is being tested internally. > - So far, testing is going well. A few bugs have been found and fixed. > - Their version has two windows; GUI was changed very recently. > - Current functionality is unchanged from the planned final > version. > - Will hand off the two window prototype version very soon. > - Will have final one-window version a few weeks later. > > A question about the look and feel of the GUI Hardware Compatibility > List submission window came up. Frank said he would check, but he > thought that window would be OK unchanged from before. He would, > however, like to see that window called out to the user more somehow > (e.g. the button to select it more prominently displayed). Frank will > follow up on email. > > DDU library > ----------- > > DDU library is code complete, and has undergone some unit testing. > - Library consists of a library module plus some scripts. > - It is awaiting a more complete test environment (e.g. ability to plug > into AI proper). > - Testing has been done with a simple test program (Python script) so > far. (Not a formal test suite.) > - Bill and Tony to forward the test program they have along with > the library. Jack to assess how complete the test program is > and how to make it more complete. > - Test program can serve as a start for the test suite Andre > will need for ON integration. > - Jack to get AI interfaces coded ASAP, so the China Team can do > more complete unit testing of DDU in a better context. Jack > cannot commit to next week, but will get it within a few > weeks. > - More thorough testing of different kinds of packages and DU images to > begin. > - Generate DU images with many packages, one package, multiple > OS versions of a package using /usr/bin/itu script. > - Try with wildcards: > - P5I, SVR4: wildcard applies to the files or packages > - DU image: wildcard applies to packages inside the > image (Jack verified this in the func spec - line 297 > of V6 spec) > - Tony and Zhongyuan to take care of this. > > Text mode DDU > ------------- > > Waiting for UI design discussion with Frank to settle before starting. > > === DDU library is needed in ON / Testing > > We discussed the DDU library going into an install gate (e.g. > slim_source) and then going back to ON with other installation modules. > > - DDU library bits would need to be code reviewed at caiman-discuss and > testing completed first. > - Automated testing for DDU library would be part of AI automated > testing. > - Jack to work out logistics of automated testing before putting back to > an install gate. > - China team will decide later how/where to putback UIs. > - Jack to look into splitting of existing DDU package into separate > packages with UIs in one package (delivered directly to the > OpenSolaris dock) and the DDU library delivered to ON. ON package > will need to have the database too. > - Liyan asked for time to investigate how to putback to ON. - Jack > to help bring DDU team up to speed on putbacks to ON for > future maintenance; provide contacts in China who have > putback, etc. (Can be done later.) > > === DDU and accessibility > > - Decided over email that GUI notification "balloon" would still appear > as had been previously decided. Our accessibility expert said that > even though it is currently ugly, the notification window is > accessible through the keyboard without the need of a mouse. Of > course, the DDU icon and menu dispatch are still available. > > === New agenda items > > The following applies to text mode. While it is not necessary to > explicitly mount or unmount devices plugged into the USB port, an eject > button in the menus is required for the CD. A browser window is needed > as well, for traversing directories and loading files, since there is no > way for the user to know the pathnames found in removable devices. > > The devices-without-drivers list needs a refresh each time a package is > added; a package seemingly associated with a device may load a > different driver than what the device needs. Verified with Bill that > thats how it will work. > > Frank to make a more complete GUI spec and send it to China team so that > can verify the GUI against it. > > === Next meeting > > Two weeks from now will be the last day of the China holiday. > Next meeting will be same time, but on 10/15 PRC time, 10/14 US time. >
