Re: Spotlight Importer for files in "Project-Based" folder
Re: Spotlight Importer for files in "Project-Based" folder
- Subject: Re: Spotlight Importer for files in "Project-Based" folder
- From: SA Dev <email@hidden>
- Date: Tue, 14 Jun 2005 06:38:29 -0400
That's certainly a solution, but I thought it'd make more sense to
show the project containing the search term itself, rather than
several files that belong to it, which all end up opening the same
project file anyway. Though that *would* solve the next question -
how to tell my app to open up the project to the requested file,
though I have bookmarked several other threads on that topic.
So, fellow developers, which *is* better practice in this
scenario? Again, never mind the current clunkiness; it's going away
in the next major version, I'm just trying to make sure it 'just
works' for Spotlight in the current version. From a user standpoint,
would you rather see five different files belonging to the project
(which you can't really manipulate unless you open the main project
file) or just the main project file they belong to?
On Jun 13, 2005, at 11:03 PM, Fritz Anderson wrote:
On 13 Jun 2005, at 4:05 PM, SA Dev wrote:
So, what I want is to be able to locate text in a supporting
file, but have Spotlight return the main project file as the
result of the find. The logic to determine the main project file
isn't a problem (it's clunky, but not really a problem), but the
user cannot directly open the supporting files.
If it's so all-fired easy (if clunky) to determine the project file
from the constituent, why not have your application open the
project file when given a constituent file to open? That way,
Spotlight acts on the file that gets indexed, and there's no need
for tricks.
-- F
_______________________________________________
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