[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Renaissance]platform objects' awakening
From: |
Nicola Pero |
Subject: |
Re: [Renaissance]platform objects' awakening |
Date: |
Thu, 17 Jul 2003 16:15:20 +0100 (BST) |
> >EODisplayGroups have an property fetchesOnLoad which, when set to YES,
> >tells them to issue a fetch to their EODataSources after they have
> >loaded from a nib (resulting in a fetch from the database). In Mulle's
> >implementation of EOInterface, this is done in
> >-[EODisplayGroup awakeFromNib], I don't know where it's done in
> >Apple's version. To be able to use this feature, I suggest the
> >following patch to GSMarkupAwaker.m. That way, the platform object
> >can be a real EODisplayGroup and not a subclass which implements
> >-awakeFromGSMarkup. Yet I don't know if that would harm some other
> >platform objects.
> >
>
> How about adding a category to EODisplayGroup in the library to be that
> implements
> @implementation EODisplayGroup (Renaissance)
> - (void)awakeFromGSMarkup
> {
> [self awakeFromNib];
> }
> @end
>
> That way, if we ever need to fo something special for GSMarkup, we can
> just alter this implementation accordingly. I don't know what the side
> effects of allways falling back to awakeFromNib within GSMarkupAwaker
> may be, but it feels dangerous.
Excellent suggestion. I agree.