Re: RFC: Deprecate GTK_{RESPONSE,STOCK}_{YES,NO}
- From: "Matthias Clasen" <matthias clasen gmail com>
- To: "Christian Dywan" <christian imendio com>
- Cc: gtk-devel-list gnome org, Murray Cumming <murrayc murrayc com>
- Subject: Re: RFC: Deprecate GTK_{RESPONSE,STOCK}_{YES,NO}
- Date: Mon, 25 Aug 2008 09:01:09 -0400
On Mon, Aug 25, 2008 at 8:22 AM, Christian Dywan <christian imendio com> wrote:
> Am Mon, 25 Aug 2008 14:12:38 +0200
> schrieb Murray Cumming <murrayc murrayc com>:
>
>> At the least, any Yes/No stuff in the API reference documentation
>> should have a note saying that they are generally a bad idea,
>> probably with a link to the GNOME HIG.
>
> If we want to keep people from doing stupid things I agree, the API
> reference should just point out very expressly that one shouldn't use
> these buttons deliberately.
>
> I wouldn't assert so strongly that Yes and No are "generally a bad
> idea", though. I think there are appropriate use cases.
I'd be ok with adding a paragraph somewhere in the api docs that
points out the benefit of following some interface guidelines, and
maybe pointing at the gnome HIG as an example. I don't think the docs
for YES/NO are the ideal place for that, though...
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]