Hey,
I am working on an iPhone app to manage project files which consist of
names, equipment, and tasks. I want to use Core Data with SQLite as
the backing store.
Our prototype has a bunch of tableview pages that allow the user to
create, edit and delete projects and project elements.I have 6
different tableview controllers, each of which handles a different
part of the project records.
Modeling my app on the Locations tutorial app, I am thinking that my
app delegate itself should own the managed object model/context and
persistent store coordinator, as well as the working object array used
to populate the various tableviews. This would be slightly different
from Locations, which has its working array owned by its single
tableview controller.
It seems to me the data should be globally accessible from any one of
my tableviews, so each tableview could work on the part of the data it
is designed for, but I am unsure how to accomplish that. Is it as
simple as passing the appropriate pointer(s) to each tableview as it
is loaded, and operating on the project data via that pointer? If so,
should it just be the pointer to the working array, or the managed
object context, or both?
If there is a better way to accomplish this, I would be grateful for
any advice, and especially of any pointers to tutorials or sample code
that might be helpful. This is my first iPhone app, and my first shot
at Core Data, so I have a lot to learn.
Thanks,
Paul
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
