• 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: Cocoa/Objective-C flat name space problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa/Objective-C flat name space problems


  • Subject: Re: Cocoa/Objective-C flat name space problems
  • From: Stephen Blinkhorn <email@hidden>
  • Date: Fri, 7 May 2010 11:07:28 -0600

On 7 May 2010, at 00:52, Jonathan Hess wrote:

On May 6, 2010, at 7:27 PM, Stephen Blinkhorn wrote:

Thanks Isaac,

On 6 May 2010, at 16:35, Isaac Wankerl wrote:

With #2, you might want to investigate using ibtool and the -- convert option to modify the nibs. Just from reading the man page, it looks like that might work if you come up with some build scripts to run it for each project.

I've never used ibtool before but this looks very promising although right now I can't seem to get ibtool to actually commit any changes to the xib file. Probably missing something simple. A simple search and replace in TextWrangler confirms this approach should work well though/

Hey Stephen -

Are you passing "--write pathToOutputFile.xib" to ibtool?

I am now! Thanks Jon, Stephen



Jon Hess


Thanks, Stephen



Isaac http://www.kerlmax.com/

On Thu, May 6, 2010 at 5:22 PM, Stephen Blinkhorn <email@hidden > wrote:
Hi all,


I write audio unit plugins and Cocoa's flat name space is causing some real problems. Essentially I have a static library of Cocoa user interface classes that I use in multiple plug-in projects. These plug-ins are often run side by side by the user so I can't guarantee that a previous version of a class (in an older plugin) hasn't already been loaded by the run time system.

I know of the following two solutions to this problem but neither are ideal:

1. Create a framework. This is quite a heavy weight solution and requires that all classes are backwards compatible.

2. Use the preprocessor the #define unique class names when the project is compiled. This is great but falls down because the original class names are still present in the nib/xib files.

Anyone have any other suggestions or tips for dealing with this situation? With the move towards Cocoa well under way this is starting to affect a lot of people.

Thanks,
Stephen

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please 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)

Please 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


References: 
 >Cocoa/Objective-C flat name space problems (From: Stephen Blinkhorn <email@hidden>)
 >Re: Cocoa/Objective-C flat name space problems (From: Isaac Wankerl <email@hidden>)
 >Re: Cocoa/Objective-C flat name space problems (From: Stephen Blinkhorn <email@hidden>)
 >Re: Cocoa/Objective-C flat name space problems (From: Jonathan Hess <email@hidden>)

  • Prev by Date: Re: How do you set the text in an NSTextView?
  • Next by Date: Re: NSPopupButtons work, but not in hierarchical mode, what am I missing here ?
  • Previous by thread: Re: Cocoa/Objective-C flat name space problems
  • Next by thread: QTMovieView binding
  • Index(es):
    • Date
    • Thread