Re: Rich Clients and WO
Re: Rich Clients and WO
- Subject: Re: Rich Clients and WO
- From: John Huss <email@hidden>
- Date: Tue, 9 Jun 2009 11:28:26 -0500
No, I thought it wasn't really clear either - I thought it was local storage at first too, but it's not - It's a _javascript_ CoreData implementation accessing an ERXRest backend on the server. If I'm wrong someone please correct me.
John
On Tue, Jun 9, 2009 at 11:23 AM, David Avendasora
<email@hidden> wrote:
On Jun 9, 2009, at 12:18 PM, John Huss wrote:
Also, you would have to rewrite EOEditingContext and related classes in _javascript_, which is a fairly large task.
But I thought that was part of what Gianduia did and what made it so much cooler than last years rich-client-of-the-moment Sprout Core.
Yes, but CoreData != EOF. They are similar, but not the same. I'm not sure why they chose CoreData instead of EOF; maybe since CoreData was newly designed it is actually better than EOF; I don't know, I haven't used it.
Okay. I must have misunderstood that part of the presentation. I thought that CoreData was there just for local persistence of things and that it _also_ had EOF-like ECs also.
Too much WOWODC content, too too few notes!
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden