On Sep 30, 2009, at 1:11 PM, Alex Reynolds wrote:
Unfortunately, that simple solution means parting ways with the naming scheme of the source I'm pulling data from and changing the naming scheme for all my other entities/classes, too, which I was hoping to avoid. But thanks to all for the confirmation.
I hear you, but ... "them's the breaks" I'm afraid. Such a basic name is sure to collide. I doubt it's as complex a problem as you're making it out to be, though:
1 - Renaming a class is easy to do with the refactoring tool in Xcode and choosing another entity name can't be *that* earth-shattering. The hardest part is finding any places you've referenced the entity by name (-insertEntityForName:...) and replacing them with the new name.
2 - Just because it's not called "Object" in the object model doesn't mean you can't call it "Object" in the user interface ...
-- I.S. _______________________________________________ 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
