With that stated, I believe that for new versions of app's, that
the app should give the user the option of installing (and
removing) the importer for it's files.
However for currently shipping apps that developers wish to
provide a simple Spotlight importer download for current users I
still think a Apple Script is the best way to go.
Of course Apple has stated that developers should provide an
install for this - I personally think an installer for a
Spotlight importer (or any plug-in for that matter) is overkill.
My vote is for an enhancement to Finder and/or LaunchServices so
that any newly-added app packages will be scanned for importers,
and if they're not already installed, a dialog will be presented
offering the User the option to install in / or ~/, index now,
etc. rdar://problems/4106966
Why would you want to install it outside of the application bundle?
If LaunchServices has found it inside the app bundle, why move it
anywhere else? That would only create problems later, for example,
if you delete the app, the MDImporter wouldn't automatically be
removed. I'm all for the self-contained approach. Good thing Apple
agrees with me... ;-)
perhaps you don't actually have an application wrapper to
install it in?
Third parties writing importers for common file formats that
Apple doesn't supply will encounter this.
Also, if you have a background daemon that runs, but you want to
support searching the data files..
there are situations where it might come up.
--
"William Cheeseman ... is said not to be a doofus in real life." -
Roger Ebert, Chicago Sun-Times Online
Scott Anguish
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
