Re: Rich Clients and WO

2009-06-10 Thread James Cicenia
Ok - Next year I have to go. June is so bad for me, but, I will make it happen next year. But, since we are all waiting, I guess I don't feel so left out. James On Jun 10, 2009, at 11:03 AM, Kieran Kelleher wrote: James, you should have come to WOWODC! Gianduia has not yet been released..

Re: Rich Clients and WO

2009-06-10 Thread Kieran Kelleher
James, you should have come to WOWODC! Gianduia has not yet been released... we saw it, were blown away by it, but we don't have it, so all we can do is dream about having it as soon as it is released. :-) On Jun 10, 2009, at 7:59 AM, James Cicenia wrote: What is this Gianduia? And where

Re: Rich Clients and WO

2009-06-10 Thread Stamenkovic Florijan
A few things here need addressing. On Jun 09, 2009, at 11:08, John Huss wrote: I believe JavaClient uses the standard Java serialization, which is a binary format. Generating the format in Javascript is probably not feasible; if it was I'm sure the GWT folks would have used it, but they d

Re: Rich Clients and WO

2009-06-10 Thread James Cicenia
What is this Gianduia? And where do I get some? Is this a new chocolate bar or such from that famous SanFran chocolatier? -James On Jun 9, 2009, at 10:23 AM, David Avendasora wrote: On Jun 9, 2009, at 11:08 AM, John Huss wrote: I believe JavaClient uses the standard Java serialization,

Re: Rich Clients and WO

2009-06-09 Thread Joe Little
On Tue, Jun 9, 2009 at 11:40 AM, Joe Little wrote: > Much thanks on that last paragraph. I wouldn't have gathered that from > the presentation, but it now makes me smile just a little more now :) > sorry, this is in regards to using these technologies in basic web pages just as much as a full RIA

Re: Rich Clients and WO

2009-06-09 Thread Joe Little
Much thanks on that last paragraph. I wouldn't have gathered that from the presentation, but it now makes me smile just a little more now :) On Tue, Jun 9, 2009 at 10:11 AM, Mike Schrag wrote: >> No, I thought it wasn't really clear either - I thought it was local >> storage at first too, but it's

Re: Rich Clients and WO

2009-06-09 Thread David Avendasora
On Jun 9, 2009, at 1:15 PM, Mike Schrag wrote: Not sure what part of EOF ... btw, why can't you go back to asking EASY questions where I don't have to work so hard :) Can I have a pony? Dave ___ Do not post admin requests to the list. They will b

Re: Rich Clients and WO

2009-06-09 Thread Mike Schrag
Not sure what part of EOF ... btw, why can't you go back to asking EASY questions where I don't have to work so hard :) ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple

Re: Rich Clients and WO

2009-06-09 Thread Mike Schrag
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. Also, you would have to rewrite EOEditingContext and relat

Re: Rich Clients and WO

2009-06-09 Thread John Huss
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 wrote:

Re: Rich Clients and WO

2009-06-09 Thread David Avendasora
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 Sprou

Re: Rich Clients and WO

2009-06-09 Thread John Huss
> 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 ar

Re: Rich Clients and WO

2009-06-09 Thread Kieran Kelleher
Cannot wait for Gianduia ... hope Pierre Frisch & Co. release this soon. Gianduia, the new killer javascript technology for data-driven apps. On Jun 9, 2009, at 11:23 AM, David Avendasora wrote: On Jun 9, 2009, at 11:08 AM, John Huss wrote: I believe JavaClient uses the standard Java

Re: Rich Clients and WO

2009-06-09 Thread David Avendasora
On Jun 9, 2009, at 11:08 AM, John Huss wrote: I believe JavaClient uses the standard Java serialization, which is a binary format. Generating the format in Javascript is probably not feasible; if it was I'm sure the GWT folks would have used it, but they didn't. Hmmm. I wonder if it wou

Re: Rich Clients and WO

2009-06-09 Thread John Huss
I believe JavaClient uses the standard Java serialization, which is a binary format. Generating the format in Javascript is probably not feasible; if it was I'm sure the GWT folks would have used it, but they didn't. Also, JavaClient's serialization is HEAVY since the whole EC is transferred (I t

Re: Rich Clients and WO

2009-06-09 Thread David Avendasora
But you opened it. If I had written "Java Client does Client Side WO Best," you never would have. :-P Dave On Jun 9, 2009, at 11:04 AM, Hugi Thordarson wrote: Damn, that was a disappointment. I opened this thread and was hoping for a viable "get rich quick" scheme! - hugi On 9.6.2009,

Re: Rich Clients and WO

2009-06-09 Thread Hugi Thordarson
Damn, that was a disappointment. I opened this thread and was hoping for a viable "get rich quick" scheme! - hugi On 9.6.2009, at 14:57, David Avendasora wrote: Hi all, I have a question that I think I can finally put into words after an excellent WOWODC, especially the session on Javas

Rich Clients and WO

2009-06-09 Thread David Avendasora
Hi all, I have a question that I think I can finally put into words after an excellent WOWODC, especially the session on Javascript Clients. Why not use the already built-in com.webobjects.eodistribution classes as the interface for passing EOs and such back and forth instead of re- invent