Re: Tree Data Structure in objc-C?
Re: Tree Data Structure in objc-C?
- Subject: Re: Tree Data Structure in objc-C?
- From: David Chan <email@hidden>
- Date: Fri, 2 Dec 2005 15:59:07 +0800
Hi all,
I have been reading on Core Data for a while ever since you advised me to
use that on my library application. It's new for me and it takes time for me
to grasp it. But so far I still couldn't figure out how Core Data approach
could help in the categorization part of my library.
As I described before, the user of the library can make category,. sub
category and sub sub sub category without any depth limit much like a folder
system. And the user can then move the books into a particular category.
The most confusing part for me is when it comes to handling the category
folder structure. And the Core Data structure doesn't seem to support this
kind of situation. How do I handle the parent and child relationship among
category nodes?
Thank you for taking time to reply my questions.
Regards
David
On 11/28/05, Uli Kusterer <email@hidden> wrote:
>
>
Am 28.11.2005 um 06:59 schrieb David Chan:
>
> The users are supposed to be able to include as many books as they
>
> want to.
>
> So I should consider a case where they have a huge number of books.
>
> I was
>
> thinking of NSDictionary too but does it has any problem when it
>
> comes to
>
> huge number of data?
>
>
NSDictionary is pretty efficient for what it does, but it does a lot,
>
so there are cases where you know you don't need all that flexibility
>
where you are better off with a custom class or CoreData.
>
>
Cheers,
>
-- M. Uli Kusterer
>
http://www.zathras.de
>
>
>
_______________________________________________
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