Re: [Bug-gnubg] Icon in the new GUI layout.

[Olivier Baur]

Le mardi, 12 aoû 2003, à 14:11 Europe/Paris, Øystein O Johansen a écrit 
:

> So, what about the Hide/Show Panel button? First of all should I call 
> the
> right hand widget, with the game record and annotation window for the
> "panel", is that a good term? What image should I use for the button to
> hide and show the panel? (I'm now using a image of a microphone. 
> Logic?)

I'd use either of the following two behaviors :
1. a "sticky" button with icon "window with panel": when pressed down, 
the panel is shown, when released, the panel is hidden;
2. or a standard button with either the "window with panel" or "window 
without panel" icons: when the button is clicked, the panel is either 
shown or hidden, and the icon of the button changes to the opposite 
state.

The two icons above would be:
- "window without panel": the frame of a simple window
- "window with panel": the frame of a window with the panel separator 
drawn inside


> Here's another opinion as well: I think the button tools in the 
> annotation
> window, with the text "Eval", "...", 0 1 2 3 4 and so, are to small*, 
> so I
> was thinking of using icon images on these buttons as well. Well.... 
> what
> should be the image for the eval button? What about the image for the
> rollout button? What should be the image for the MWC button? (I'm 
> designing
> a image for "Move") What should be the image for the Show button? (An 
> eye,
> maybe?)

As far as I'm concerned, on my portable's small 1024x768 screen, I 
think the size of these buttons is quite acceptable.

Anyway, can't the size of the buttons (or the text inside) be increased 
without requiring using icons?

What's more, I must say 'm not very fond of using too many icons; they 
can be useful when they provide shortcuts for menu items (in a toolbar) 
and/or when space is critical and text can't be used (in a tool 
palette), and when they are clearly understable (without requiring you 
to hover your mouse over the icon and wait a few secs before getting a 
helpful tooltip)

Here, in the Annotation or Hint window, these buttons are the main 
features -- they are the main tools we use to operate on the move list 
or cube decision; these buttons are no shortcuts in a toolbar. What's 
more, "eval", "rollout", "mwc", "show" and "move" are too abstract 
concepts to be clearly represented and instantly meaningful to all of 
us; I don't think we _need_ icons here (except for decorative 
purposes?); in my opinion, it would make the whole widget too cryptic.



-- Olivier