Re: ADC Core Data article
Re: ADC Core Data article
- Subject: Re: ADC Core Data article
- From: Philippe Mougin <email@hidden>
- Date: Fri, 8 Apr 2005 20:37:18 +0200
Ralph Scheuer wrote:
> In WO (Java), I have a Customer entity that is an EOGenericRecord
> subclass. This class contains firstName and lastName iVars with
> appropriate accessor methods. Question: if you did not subclass here,
> where can the appropriate accessor
>
> setLastName(String newLastName) and lastName() come from?
Wouldn't it be nice for them to be to be automatically generated (in an
automatically generated subclass if needed)? EOModeler might do that
already at design time by generating code, I don't know. If this is the
case, chances are that we will also have it in Core Data. It would be
nice.
And let's look at the big picture. Do we really need something like
EOGenericRecord at all as far as providing a default implementation for
model objects is concerned ? Aren't the Objective-C or Java run-time
powerful enough? For instance, the Objective-C run-time allows to
generate new classes at run-time. Couldn't a framework like EOF or Core
Data use it to generate on the fly true classes with regular accessors,
instead of introducing a new layer like EOGenericRecord, with its own
rules, interface, limitations, bugs etc. ?
Just wondering...
Cheers,
Philippe Mougin
Open source scripting layer for Cocoa: http://www.fscript.org
_______________________________________________
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