Re: Login item not hidden
Re: Login item not hidden
- Subject: Re: Login item not hidden
- From: Jens Alfke <email@hidden>
- Date: Wed, 08 Jun 2011 12:00:59 -0700
On Jun 8, 2011, at 10:55 AM, Leonardo wrote:
> Thanks Jens but I can't split the engine from the interface. It's a huge
> work.
That’s too bad. This kind of situation is an example of why it’s good to keep these things separable.
> Also, the app should still work as a normal app, so I would not create
> two projects, one for the app and one for the separate binary.
You don’t need two projects. Just add a new target to your project to build the binary, make it a dependency of your app, and add a build step that copies the binary into the app bundle. This is a really common design.
> I thought to create a small app e.g. FireApp and, as iTunesHelper, embed it
> within my app.
That’s pretty much the same as what I proposed above, just with a different type of target. But if you can’t separate the engine from the UI, what pieces go into the helper app? Is it going to have a copy of everything in the main app? (You could avoid duplicating code by building your shared functionality as a dynamic library or framework, then embedding that in the app bundle and having both targets link against it.)
Just remember to give the helper app a different bundle ID, or LaunchServices won’t allow both of them to be running at the same time.
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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