Re: actual proposal

[Federico Mena Quintero <federico nuclecu unam mx>]

>  A) Explain "minor modifications" .

Wording and removal of some things I think are irrelevant
(i.e. considering the lack of a window manager to be a reason to put a
close button everywhere -- a WM is one of the few things we can assume
people will be running).

>  B) Several people have pointed out that Tom's idea is fundementally
>     flawed (e.g. "close" being an ambiguous term which is better broken
>     down into discrete OK & Cancel choices).. Does the addition into
>     the guide reflect this?

I'll quote from Tom's mail:

> How:    Every window that requires no interaction (dialogs are treated in
> 	  chapter X, item Y)  has to have a  single button labeled "Close".

This is for windows that require no interaction -- maybe this should
be "no further information from the user" instead.  This would be
things like notification and information boxes.

Dialog boxes requiring user information ought to have OK/Cancel
button equivalents, anyway.

The point is that simple message or information windows should always
provide a way to close them, in the form of a Close button.

Since the GNOME libraries already provide convenience functions to pop
up such dialogs, the text in the UI Guidelines will have these things:

	- Explanation of why such dialogs need to have a Close button.

	- Examples on how to use the gnome_dialog convenience
          functions to pop up such informational dialogs.

Right now I am making some fixes to the UI Guidelines document, and I
am adding a new "components.sgml" file -- the chapter called "User
interface components" seems to have disappeared during the conversion
to SGML.

  Federico