• 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: setting corner view
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: setting corner view


  • Subject: Re: setting corner view
  • From: Stephane Sudre <email@hidden>
  • Date: Tue, 5 Jun 2007 10:57:49 +0200

Some examples of the top of my head:

- Move from an outlineview to a table view.

- Move from a stepper to a slider

- When you move from a class to its subclass, you have to change the nib again (unless you want a de-synchronization between the nib and source) whereas it's not needed with id.

Less important, "id" is shorter than any NSthing. And if you don't want to have an inspector with a huge width, "id" is "better".

And personally, I don't see the point in typing a widget when using Objective-C. Otherwise, why not use C?

On 5 juin 07, at 10:12, Yann Bizeul wrote:

IMHO, IBOutlet id is the best solution since you never know when you will be changing the class (or subclassing it). I've seen some source code and nibs using typed outlets and it proved a PITA to maintain.
Would you be able to provide specific example ? Because when specify the class, it is ok for IB to connect to such class *or* a subclass, which sounds ok to me.
Usually I connect to something clearly identified and all my calls to methods on that object will be related to this specific class.
I know your reasons are good, I'm just trying to understand :-)


See ya

Yann Bizeul - yann at tynsoe.org
Cocoa Developer

Tynsoe Projects
BuddyPop - GeekTool - SSH Tunnel Manager - ...
http://projects.tynsoe.org/


Le 5 juin 07 à 10:00, Stephane Sudre a écrit :


On 5 juin 07, at 08:04, Yann Bizeul wrote:

@interface NetworkOutlineController : NSObject
{
	IBOutlet id outlineView;
	IBOutlet id cornerView;

Just a side note about that, you should specify the class of outlets you are using to avoid confusion in some situation. If you set the class, IB will refuse to connect to something that is not of the right class or subclass. Just a good habit I think.

IMHO, IBOutlet id is the best solution since you never know when you will be changing the class (or subclassing it). I've seen some source code and nibs using typed outlets and it proved a PITA to maintain.


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: setting corner view
      • From: Jonathon Mah <email@hidden>
References: 
 >setting corner view (From: "William Zumwalt" <email@hidden>)
 >Re: setting corner view (From: Yann Bizeul <email@hidden>)
 >Re: setting corner view (From: Stephane Sudre <email@hidden>)
 >Re: setting corner view (From: Yann Bizeul <email@hidden>)

  • Prev by Date: Re: Converting uint16_t port to a NSString
  • Next by Date: Mac Disk burning API:s
  • Previous by thread: Re: setting corner view
  • Next by thread: Re: setting corner view
  • Index(es):
    • Date
    • Thread