• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: XCode Spotlight plugin improvements??
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode Spotlight plugin improvements??


  • Subject: Re: XCode Spotlight plugin improvements??
  • From: David Ewing <email@hidden>
  • Date: Tue, 17 May 2005 12:15:32 -0600


On May 17, 2005, at 10:20 AM, Jonathon Mah wrote:

On 2005-05-17, at 04:23, Chris Espinosa wrote:


The Xcode "Spotlight importer" doesn't actually do anything. It just says that certain files it cares about are text files. That's all. The standard text file importer takes it from there.


Woah woah woah. I definitely remember:


On 2005-05-03, at 11:29, Eric Peyton wrote ("Re: Three Spotlight importer questions"):



a crack at any give file. My test asserting some metadata for a PDF file. And it worked fine. But the PDF importer never got to run and that seems somehow inappropriate. Am I missing something or is that the way it is right now?



That is the way that it is supposed to be. One file == one importer. It would be a ridiculous situation performance wise if more than one importer had to run for each file. I believe (I could be wrong) that the intention is that the importers take "ownership" of the data of the file type. So a pdf importer would be the single place to go to find out information about pdf files. Your intention to use a pdf importer to just add "more" metadata is currently not supported in the system. Add your data and the rest of the necessary data. I don't know of any way to create a tree of importers for any single file.




So importers can call other importers? Or can importers only "re- direct" to another importer, unable to extract any metadata themselves? And in either case, how does Source Code.mdimporter do this? I took only a brief look at it, and it seems that a UUID in CFPlugInTypes is shared between Source Code and Rich Text (as well as Mail, Image, and Audio, so I'm probably off).

Our importer simply opens the file (recognizing UTF-8 and UTF-16) and uses the contents as the value for the kMDItemTextContent key. The SpotLight internals know how to index that content.


So we're not violating any rules here. We just don't have to do much.

Dave

_______________________________________________
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


References: 
 >XCode Spotlight plugin improvements?? (From: Richard Dunlap <email@hidden>)
 >Re: XCode Spotlight plugin improvements?? (From: Chris Espinosa <email@hidden>)
 >Re: XCode Spotlight plugin improvements?? (From: Jonathon Mah <email@hidden>)

  • Prev by Date: Re: cross development (10.3.9) and xcode 2.0 with qt7 issue
  • Next by Date: Custom build rule that outputs an object file does not get added to the link file list?
  • Previous by thread: Re: XCode Spotlight plugin improvements??
  • Next by thread: Can't set number of columns for NSOutlineView
  • Index(es):
    • Date
    • Thread