Hi Michal,
On 2012-02-08 04:09, Michal Čihař wrote:
Hi
Dne Mon, 06 Feb 2012 18:15:46 -0500
Filipus Klutiero<[email protected]> napsal(a):
On 2012-02-06 03:57, Thijs Kinkhorst wrote:
I think it's a sane default as it is. Michal, only thing: could you
perhaps extend the description of that boolean option a bit to explain the
why and the consequences?
I've improved documentation to explain reason why this option is there.
Thanks!
That would be a nice start. It may not be useful in the end if the
option is eliminated (if the Show all button is perfected enough, I do
not see why keeping an option to disable it would be necessary). But
meanwhile, it would clarify what's needed to get there.
Note that this report is not saying the current default for the option
is insane. It may well be the best default given the way Show all works
currently. All I'm asking is get the Show all button to display by
default (which does not exclude displaying it unconditionally). The
button may require improvement for such a change to be reasonable to make.
I've also changed button to show for reasonably small tables (I've
deliberately chosen value of 5 × $cfg['MaxRows'] rows).
These changes will be part of 3.5 release.
Thanks. I find this heuristic interesting.
However, if I understand correctly what was done, I think this may have
a negative impact on usability. I am not a user interface expert, but
one important feature is consistency. Here are some excerpts from user
interface guides:
To give users a conceptual sense of stability, the interface provides
a clear, finite set of objects and a set of actions to perform on
those objects. For example, when a menu command doesn’t apply to a
selected object or to the object in its current state, the command is
dimmed rather than omitted.
https://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/HIPrinciples/HIPrinciples.html#//apple_ref/doc/uid/TP30000353-TP6
* *Reconsider disabled controls.* Disabled controls can be hard to
use because users literally have to deduce why they are disabled.
Disable a control when users expect it to apply and they can
easily deduce why the control is disabled. Remove the control when
there is no way for users to enable it or they don't expect it to
apply, or leave it enabled, but provide an error message when it
is used incorrectly.
o *Tip:* If you aren't sure whether you should disable a control
or provide an error message, start by composing the error
message that you might provide. If the error message contains
helpful information that target users aren't likely to quickly
deduce, leave the control enabled and provide the error.
Otherwise, disable the control.
http://msdn.microsoft.com/en-us/library/aa511331.aspx#controls
Previously, although the button could be displayed or not, it was
consistent in a single installation.
I think the ideal would clearly be to always offer the command, but
failing that, I recommend to always show the button and only *disable*
it when the table is larger than some threshold. A tooltip could explain:
"This table contains too many records to show all together."
