On Thursday 28 June 2007 15:23, Johannes Meixner wrote:
Screen space is often very limited and the permanent help uses screen space which I would like to have for the content.
If you find that help panel limiting for whatever your dialog should contain, it will very likely not fit in an NCurses dialog. And then there is the aspect of overloading the dialog and thus overwhelming the user. There are some few select places where we make exceptions from the rule. The package selection is such a place. But this is explicitly defined as an expert tool, and there is a separate NCurses implementation that doesn't have to cope with the problems that would arise if we tried to press so many widgets in an NCurses dialog. In general configuration dialogs, this is not the case. This is why we have the wizard that provides a consistent, uniform look. And that look includes a help panel. I'd like to invite all of you who feel the need to discuss whether or not we want the help panel in the next rounds of usability discussions (if you look up the meeting minutes of those previous rounds, you will find the topic dicussed in great detail). But frankly, discussing this kind of thing is high on the top of my list of things I really don't want to do during this Hack Week.
On the other hand the space for the permanent help is narrow so that the text (in particular a URL or whatever longer item) is often not convenient to read.
How many URLs do we usually have in help texts? How many other longer items? Is this a realistic aspect?
A wide help popup with usual line lenght would be more convenient.
And it would always be in the way during installation. You could either read the help text or see what the help text describes, but never both. Been there. Discussed that. Dozens of times. Always came to the same conclusion, albeit each time with (lots of) different people. CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org