Re: +[NSBundle bundleWithIdentifier:]
Re: +[NSBundle bundleWithIdentifier:]
- Subject: Re: +[NSBundle bundleWithIdentifier:]
- From: Lawrence Sanbourne <email@hidden>
- Date: Thu, 13 Oct 2005 22:34:51 -0500
On 10/13/05, Blake Seely <email@hidden> wrote:
> If all the resources you're trying to locate are inside the .app
> bundle, then it shouldn't matter where it's running for.
>
> Is there a reason that +[NSBundle mainBundle] won't work for you?
There are three separate bundles -- one containing the widget plugin,
one containing the main app, and one containing the agent app, which
in turn is contained in the main app bundle. And one can't load
frameworks at runtime with this sort of flexibility, I believe. At the
suggestion of someone who posted to me off-list, I'm now just copying
the .framework to each bundle. I wish I had a more attractive
solution, but this does work. Anyone have any alternatives?
Larry
> -Blake
>
> On Oct 10, 2005, at 10:22 PM, Lawrence Sanbourne wrote:
>
> > Hi,
> >
> > I have a Cocoa widget plugin that needs to access resources (a private
> > framework and a Sync Services schema) that is in the main
> > application's bundle. I could use +[NSBundle bundleWithIdentifier:] to
> > access this, but I'm worried that it will not work if the user moves
> > the application around frequently. Is there a way to solve this other
> > than putting the resources in a framework in /Library/Frameworks? I
> > really want to avoid having an Installer app.
> >
> > Thanks,
> > --
> > Larry Sanbourne
> > email@hidden
> > _______________________________________________
> > Do not post admin requests to the list. They will be ignored.
> > Cocoa-dev mailing list (email@hidden)
> > Help/Unsubscribe/Update your Subscription:
> > 40mac.com
> >
> > This email sent to email@hidden
> >
>
>
--
Larry Sanbourne
email@hidden
_______________________________________________
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