Re: Core Data App vs. Core Data Doc-based App: which is appropriate?
Re: Core Data App vs. Core Data Doc-based App: which is appropriate?
- Subject: Re: Core Data App vs. Core Data Doc-based App: which is appropriate?
- From: Mark Slater <email@hidden>
- Date: Wed, 28 Sep 2005 11:31:04 -0700
Thank you for the links, but I've read through most of them before
and I haven't found the answer to the basic question:
If I want spotlight to show each item in the program catalog as a
separate entry in the search results, do I need to use a separate
core data store for each entry?
And the follow-up question:
If I'm creating an app that has many data stores, but the UI presents
a single interface with the data from all of them, which template is
more appropriate - Core Data Application or Core Data Document-based
application?
The reason for these questions is comments like the one found in this
blog entry (which is old and may not be valid any more, hence my
question here): http://daringfireball.net/2004/07/spotlight_on_spotlight
"One implication of Spotlight’s file-centricity is that its ability
to search “email” might not apply to clients other than Apple Mail —
it’s the fact that the new Tiger version of Mail stores each message
as a separate file that allows Spotlight to effectively return
individual mail messages as search results. No other major mail
client uses a one-message-per-file storage format."
Another blog with similar claims is here: http://keeto.net/item.html?
item_id=96
If I recall, this aspect of spotlight implementation is part of the
reason MS Entourage doesn't support spotlight yet - it saves all mail
messages in a single file.
Mark
On Sep 28, 2005, at 7:53 AM, mmalcolm crawford wrote:
<http://developer.apple.com/documentation/Cocoa/Conceptual/
AppArchitecture/index.html>
<http://developer.apple.com/documentation/Cocoa/Conceptual/Documents/
index.html>
<http://developer.apple.com/documentation/Carbon/Conceptual/
MetadataIntro/index.html>
<http://developer.apple.com/macosx/spotlight.html>
<http://developer.apple.com/documentation/Cocoa/Conceptual/
NSPersistentDocumentTutorial/07_Metadata/chapter_8_section_1.html#//
apple_ref/doc/uid/TP40001799-CH236-TP9>
mmalc
On Sep 28, 2005, at 2:31 AM, Mark Slater wrote:
I'm starting work on a program that will include... cataloging,
for want of a better term. The user will have binary files, and
additional metadata associated with these files. I'd like the
metadata to be searchable with spotlight, but I read (and this may
be out of date), that spotlight needs to have separate files for
separate data items. Basically, I'd like the user to be able to
search for "yogurt" and only the binary files that have "yogurt"
associated with them show up in the results. At the same time, for
the UI, I don't plan to have the user opening and closing a new
document for each file, but rather allow them to browse a list of
all the cataloged items.
So I'm trying to figure out if my project should use the Core Data
application template or the Core Data Document-based application
template (with or without spotlight importer). If my understanding
of spotlight is correct, that leads me to think I should have a
different document for each item in the catalog, but would it be
possible to merge all the documents into a cohesive (one window
UI) app with the Doc-based template? Or am I wrong about spotlight
and I should just use the Core Data template and end up with a
more complex spotlight importer (which is fine also)?
Thanks!
Mark
_______________________________________________
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