I'm wondering if anyone has addressed modeling recurring calendar
events with EOF in a nice way? None of the options seem particularly
attractive to me at the moment, but I was hoping someone might have
some clever insight into the problem. I think the proper impl is to
make "ghost" events appear in the results that don't become "real"
EO's until someone touches them to make a change from the original
pattern, but this seems like sort of a huge pain with EOF ... I don't
know what the overhead will be of constantly making and throwing away
unsaved EOs on every view. I was considering a non-EO cover object
for an event that can turn into an EO, but it means you have to "write
it twice" to support all the API of the EO version of the event.
Ack.
I've also considered an EOF adaptor on top of icalserver on Leopard,
but this has all sorts of its own undesirable complications.
Ideas welcome :)
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
