Re: Best approach to adding a Spotlight importer
Re: Best approach to adding a Spotlight importer
- Subject: Re: Best approach to adding a Spotlight importer
- From: Chris Hanson <email@hidden>
- Date: Mon, 10 Apr 2006 07:21:42 -0700
On Apr 9, 2006, at 1:37 PM, David Dunham wrote:
I've got a document-creating application, and want to have its
documents indexable. I think the easiest approach will be to share
the document-reading code with the Spotlight importer.
But I'm less clear on how to set this up with Xcode. Do I add a
target to my existing project? Presumably a loadable bundle?
That would be a good way to do it, to add a target to generate your
Spotlight importer to the same project that generates your
application, and to have your build process embed it within your
application.
One issue I see is that both the app and the .mdimporter have an
Info.plist, so they're not going to be able to coexist in the same
folder.
That's actually not a problem. Your Spotlight importer target's
Info.plist can have (and will automatically get) a name like
"MyImporter-Info.plist" and it can be located pretty much anywhere.
There's a build setting -- "Info.plist File" (INFOPLIST_FILE) -- that
specifies the project-relative path to the Info.plist file that
should be used for a target that generates a bundle.
On the other hand, I guess I want to distribute the .mdimporter
inside the application bundle, like OmniOutliner.
You can do this easily with a Copy Files build phase.
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden