The design and implementation of an Open Source animation tool.

August 5, 2007

HUD Cues

To the extent that Moing has different modes in its UI, I'd like to make them very obvious. If we fail to do that, users are going to lose track of what mode they're in or even necessarily realize that they've entered a different mode when they click something in the interface. To that end, I think most mode changes should be reflected prominently in the editor pane as "HUD" information.

Two of the most significant modes are the recording and pose modes. Recording mode is indicated with a red border around the canvas (an idea taken from k-sketch), and pose mode is indicated with a yellow (or possibly blue, for the sake of colorblindness) border, as well as the name of the pose in largeish letters of the same color.

More minor information (use hints, etc.) that doesn't quite rate the HUD appears in the status bar instead, more or less the way we do it in Inkscape.

2 comments:

mgsloan said...

Sounds good. I've thought a bit about preferences, and I think that a config file is the way to go for things like this (the color choices, w.r.t colorblindness).

True, this might evolve into a fullblown preferences dialog, but configuration is truly unavoidable, and a config file is a good lightweight option.

MenTaLguY said...

Hm, I think we're best off picking color-blind-safe combinations and leaving it at that. Doing some research, red and yellow seem to be okay (the intensity looks very different), as would red and blue be.

My inclination is to go with red and yellow for now, but if colorblind people have problems then I'd just want to go red and blue rather than making it a preference. I don't think making decisions about color blindness issues in the application is a responsibility we should ever push onto end users, whether they are colorblind or not.