Re: Spotlight Plugins don't immediately work?
Re: Spotlight Plugins don't immediately work?
- Subject: Re: Spotlight Plugins don't immediately work?
- From: j o a r <email@hidden>
- Date: Wed, 4 May 2005 08:36:16 +0200
I'm not suggesting that there shouldn't be a supported directory in */
Library for MDImporters, but the context of this thread was about
MDImporters from app wrappers, and how to deal with MDImporters when
you update apps.
My point is that _besides_ the directory in */Library, there should
be a supported place inside the app wrapper for MDImporters, and that
you shouldn't have to move them from that directory to have them
working.
j o a r
On 4 maj 2005, at 08.28, Scott Anguish wrote:
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.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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