Hi there, > We should now probably consider shortening our help text and listing only > relevant information there, as in the above small popup window, it is rather > difficult to read (which it probably was even before and that's why hardly > anyone bothered to read the help text at all) > There is no reason why it has to be difficult to read. In your screenshots, there's plenty of room to enlarge the window. Just add some sensible size calculation function there like size = 80% * main_window->size if (size > 600) size = 600 if (size < 100) size = main_window->size With different values for width and height...
I think the side help made some sense for some kind of text: like "please wait...", and generic informative stuff like: "you have to select a package to configure", but this should be presented in a different way. I think generic informative text should be presented as a sub-header. You guys mentioned tooltips, and I'm not really sure it's a good idea. I don't think it's usable and developers tend to neglect them, which just makes the situation worse, because users never know what has some help and what hasn't. Better to focus on enriching help as it is, with information and navigability. Possibly, what we could do is to set a link from fields to some anchor in the documentation. When the user presses the tooltip button, we show part of the help from there, cut with a "More" button that takes the user to the help dialog. Seems like a simpler solution, and better for the user because it would be better integrated with the rest of the documentation. Important remarks about some field or the dialog in general should simply be visible in the interface, as a label (maybe with a icon to go with it). Cheers, Ricardo -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
