Re: [Usability] Re: RFE - API change from GtkMessageDialog to GtkAlert
- From: Gregory Merchan <merchan phys lsu edu>
- To: Maciej Stachowiak <mjs noisehavoc org>
- Cc: gtk-devel-list gnome org, usability gnome org
- Subject: Re: [Usability] Re: RFE - API change from GtkMessageDialog to GtkAlert
- Date: Tue, 27 Nov 2001 00:21:45 -0600
On Mon, Nov 26, 2001 at 06:55:33PM -0800, Maciej Stachowiak wrote:
<snipped first section - see Havoc's reply>
> >
> > Gregory Merchan <merchan baton phys lsu edu> writes:
> >
> > > I realize that this is too late for the freeze.
> > >
> > > I'd like to see a change from the GtkMessageDialog api to a GtkAlert api.
> > > There are three parts I see changing for this.
> > >
> > > The name:
> > > * GtkAlert is fewer letters and words so it requires less typing and
> > > the egtk minor mode for emacs will work correctly without
> > > modification.
> > > * The name is more suggestive of proper use. The essential difference
> > > between a dialog and an alert is that the user never requests an
> > > alert; an alert is an intrusion into the user's workflow.
> > >
> > > The construction:
> > > * Alerts may have a Cancel button, an equivalent of OK, and possibly an
> > > alternative action button.
> > > - Error notices and informative alerts would have just an OK button.
>
> If there's only one button, better to call it "Close", since the user
> is not agreeing to anything (and does not have the option to
> disagree). There may be other, better names in some situations.
The response from the user is "OK, I'm done reading."
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]