Some additional comments on your comments below! Mike > > 5) I think this first page could use a title (e.g. "Select a > > language", or "select a locale"). > What language would you put it in? We could, of course, title the > window with something like "Language". We are removing the specific > concept of "locale" as it is confusing for many. Locale does make an implicit > appearance later when the user selects the primary language to be > used after rebooting - the language selection is paired with a country, > but this does not require the use to understand "locale".
SuSE and Ubuntu both put the title in English. http://www.zenstarstudio.com/install/ubuntu.htm http://www.zenstarstudio.com/install/index.htm I don't think there's a perfect solution here, but having a title would be more consistent, I think. > > 7) Why are the first two pages completed with "OK", but the next > > pages completed with "Next>"? It seems to me that it might be more > > consistent to use "Next>" throughout. > As mentioned in another reply, the user can't return to these > pages once they reach the Welcome page. Hmmm...why is that? > > 9) On the Disk page, the "type '=' into any partition size to adjust > > the available disk space" seems strange. What does it do? (I > > couldn't figure out how to type an equal sign into any Size field > > here). That would be a fairly non-standard thing to do -- what's the > > intent here? > Typing "=" into any partition size field adjusts that partition's > size by the "Available" size amount such that the available disk space > goes to zero - no remaining unused/over allocated disk space. Save the > user from having to do the mental arithmetic. There is a "bug" in the > current implementation - changes should occur on the keystroke, not when > the field looses focus. Hmmm... typing "=" into a numeric field is very non-intuitive to me. I don't recall any application ever doing this either. Perhaps it would be better to have buttons to do this? (BTW, I don't think it worked by losing focus either -- I tried that a couple of times, and it didn't do anything -- I could have missed this though?) > > 10) If I have one active partition, and I make it smaller, > should the available space show up in the "Unused" partition? Or maybe, I'm > not > > sure how the "unused" partition type works, because its size field is > > greyed out and set to zero when I select "Unused". Don't "Unused" > > partitions also have sizes? > No, the released disk space shows up in Available at the bottom. > We shouldn't presume the user is freeing up space for a new > partition. They may be freeing it up to increase the size of another > partition. > Unused partitions do not have sizes. Again, the keystroke entry "bug" in > Q9 is probably creating some confusion. Hmmm...why don't unused partitions have sizes? That's unexpected for me. When I ran through the demo, I was trying to reserve some partitions for later use by Linux (which Solaris should consider "unused"), so forcing it to zero size was quite unexpected for me. > > 13) It could probably also be localized as per the initial two > panels. (e.g. in Europe, the order is different from the US.) > We don't want to force the user to specify a locale in addition to > a language in the first panel. Then, YYYY-MM-DD doesn't show up, when non-English languages are in use, right? (Y/M/D are English-centric abbreviations). > > 14) Hmmm...the Hour field is 0 - 12. That doesn't seem right. Are 0 > > AM and 0 PM both valid times? There is no 0 pm, but there are both 0 and > > 12 am depending on > 12/24 hour time. So, what happens if I select 0 PM (which the GUI allows)? Since the numbers 13-23 are not in the list, I assumed that 24-hour time entry was not possible.... > > 16) Might want to consider making the hour field and the AM/PM > fields 24 hour in other locales (or maybe you already did this? I > didn't check... :-) > User selectable AM/PM/24. How do I get to the 24-hour time entry (from the English language installer)? > > > > 17) On the Users screen, if the passwords don't match for the user > > account, the error message is "User account error - must enter all or > > none of the user account information". This is fairly generic (and > > somewhat misleading). > > I think there's a much better way to handle errors: if the data > is invalid (e.g. passwords don't match), then don't enable the "Next>" > > button. (Of course, make sure that there's a visible error message > > somewhere in this case.) When the data is there, the Next> button > > should be the default when ENTER is pressed. > Again, the user may not realize why the Next is not enabled even > with a visible message. Users often don't look where we want them too. > Myself included. ;-) We are working with the Docs folks to improve the > message text. I think that disabling the NEXT> button is a fairly standard way of doing this...I'm essentially asserting that users wouldn't have this problem, because this already occurs frequently. This would be a testable assertion, of course! :-) > > 18) Same thing on the Install page -- if I haven't accepted the terms > > of the license agreement, don't enable the Install button for me. > Again, we don't want to make the user guess. More work for us to > add the extra error messages, but you'll note that we are allowing the > user to accept the license within the dialog, which then proceeds to the > next screen, rather than forcing the user to close the dialog, check > the box, and click Install again. Yep -- it's probably more work either way.
