• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Why "Add" button for Cocoa Bindings?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why "Add" button for Cocoa Bindings?


  • Subject: Re: Why "Add" button for Cocoa Bindings?
  • From: Larry Gerndt <email@hidden>
  • Date: Wed, 10 Nov 2004 16:36:16 -0800

> I'm curious about why the button used to create a new table view entry is
> called "Add" instead of "New" in the context of Cocoa bindings and
> master-detail layouts. All the examples I've seen use "Add."
>
> This strikes me as inconsistent with Macintosh usage in other contexts. The
> disparity caused me to stumble a little when I first tried to use a
> master-detail layout.
>
> Normally, I expect to select something first, then to perform an operation
> like "Add" on the selection. For example, first fill out a form, then click an
> "Add" or "+" button to add it to a database. A common exception to this
> convention is when there isn't anything in existence yet to select, in which
> case the operation is called "New" -- New file, New window, etc.
>
> But in these Cocoa bindings master-detail layouts, I seem to have to click the
> Add button first, to create a new row in the master table and to enable the
> text fields in the detail area. Then I can start typing, either in the new row
> or in the form, and my edits show up in both areas. This strikes me as
> backwards -- but if that's the way it is, shouldn't the button be named "New"?
> Wouldn't that be less confusing to users confronting a master-detail layout
> for the first time?
>
> (I would really prefer to be able to just click in the content area of the
> table to enable a cell for editing, then start typing -- or, if necessary, to
> find the first text field in the form already enabled so that I can just start
> typing, then click an "Add" button when I'm satisfied that I've got it right.
> That's the way I've always written my user interfaces. But that's a question
> for another day.)

"Add" correlates well with the alternative, a wordless plus sign button,
which we see in the Finder and many Apple applications.   So in my opinion,
mmalc could/should leave it as "Add", or switch to the plus sign.
--
Larry Gerndt
AIM Handle: SonOfTheSonOfMan
Let the truth be told though the heavens fall -- James Garrison

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: auto InfoPlist.strings updating
  • Next by Date: Multiple Nibs
  • Previous by thread: Re: Why "Add" button for Cocoa Bindings?
  • Next by thread: auto InfoPlist.strings updating
  • Index(es):
    • Date
    • Thread