• 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: Core Data OpenGL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data OpenGL


  • Subject: Re: Core Data OpenGL
  • From: Stefan Werner <email@hidden>
  • Date: Thu, 22 Feb 2007 15:29:58 +0100

This may seem a little simplistic, but what advantage
is there in using Core Data for something like a 3D
application?

My model is full of unsupported data types and BLOB's,
and it seems that one is going to spend an awful lot
of time converting things back and forth using NSData
and the like.

I ask this only to help decide where I should devote
the lion's share of my time and effort, and Core Data
seems quite involved.


What exactly to do you want to store in CoreData? If you want to store polygon meshes and millions of vertices, then you're probably better off using one of the classic 3d data structures. Core Data, at least in the 10.4 implementation is not the ideal tool here.

Stefan
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Core Data OpenGL
      • From: mark hill <email@hidden>
References: 
 >Core Data OpenGL (From: mark hill <email@hidden>)

  • Prev by Date: Re: How to access files in Cocoa application.
  • Next by Date: Re: Must remove submenu when dealloccing NSMenuItem?
  • Previous by thread: Core Data OpenGL
  • Next by thread: Re: Core Data OpenGL
  • Index(es):
    • Date
    • Thread