[Bf-taskforce25] Mockup note

[Joshua Leung]

Hi,

I agree with Matt's points and also the idea of keeping the labels on the
buttons.

Personally, I think that's one of the neat things that we do, since IMO it
makes it clearer what the label applies to (see the current WIP layout
engine's results in the Object buttons for example. I don't think it is
terribly clear that the labels for the combo boxes are related to those and
not as column/section headers instead). and also because it minimises the
effect of having too much 'wasted' space.

On Sat, Mar 14, 2009 at 2:14 PM, Matt Ebb <matt at mke3.net> wrote:

> On Sat, Mar 14, 2009 at 2:39 AM, Ton Roosendaal <ton at blender.org> wrote:
> > Hi William,
> >
> > http://wiki.blender.org/uploads/8/88/2_5_mockups_01.png
> >
> > For nice aligned layouts it would work better to more strictly separate
> > button values (numbers, menu options, settings) from their labels.
> >
>
> > They do this quite consistantly, only tool buttons get their entire
> > text inside, which makes sense.
>
> I disagree here. For things that are redundant like 'Location X' 'Location
> Y'
> 'Location Z' , it definitely makes sense to drop the 'Location' and
> leave it as a separate label. Repeating that text on every button
> overcrowds things, and makes it harder to skim-read down the left edge
> for the useful information (x/y/z).
>
> However for other buttons, I think it's better to keep the label on
> the number field. The space in the UI that the text occupies is going
> to be used anyway, and so putting it on the button itself keeps a very
> clear connection between the value and the property (which can
> potentially get messy and unclear in more complicated layouts), but
> also, keeping the button size large is a good thing.
>
> The speed of accessing a target on screen with the mouse is a function
> of distance to the target and the size of the target (Fitt's law), so
> the larger the button, the easier it is to hit it quickly. Having
> smaller buttons means you have to be much more exact with clicks,
> which is a bit of a waste if the space is already being used by the
> text, just not clickable. This is also the reason why the check-box
> toggle buttons are currently drawn with the button background and not
> just the checkbox - it's much easier to hit, and it's also apparent
> that the entire region is clickable.

Agreed. Seeing a checkbox with text beside it but no background suggests
that only the checkbox is clickable since the text may just be a label
slapped beside the checkbox (from prior experience with other widgets),
which makes it harder for some users to use (and troublesome for those in a
rush + rather sleep deprived).

Hmmm.... it seems I just repeated Matt's points again, but anyways, just
adding some weight to this end of the argument.

Aligorith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-taskforce25/attachments/20090314/2030e128/attachment.htm