On Jul 10, 2010, at 8:31 AM, Matt James wrote: > know that was the common way to generate those classes to begin with (as I > said, I'm completely new to the workings of Core Data).
I don't know how "common" precisely, but very handy in certain situations, especially for those who hate KVC syntax. > After using this technique, I did have one more question related to > automated class generation. Xcode automatically tried to add the class > files to the AppName.xcdatamodeld directory. My initial assumption was that > this was only because I had it selected in the source list when I attempted > to add the class files, so I selected a new destination of the Classes > folder where all other classes are stored. Your assumption is correct, and I will add that storing inside the xdatamodel bundle is a Bad Idea™. > After receiving some errors from Xcode when generating the files, I began > wondering if this was the right decision. Does everyone usually stick these > files in the xcdatamodeld folder? (I wish I had the errors to show you, but > I didn't think to write them down when they popped up. Needless to say, > they were errors from Xcode, not during compiling.) I think it was the right decision. Generally speaking, the location of source files within the project tree doesn't matter (much). Folder organization is largely a matter of style and convention. The build phases might specify "special" folders whose contents will be treated in certain ways (esp. "Resources"), but even that is fully up to you. HTH, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ 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
