**Grumpy Alert**
On Sep 5, 2008, at 3:43 PM, Chuck Hill wrote:
My uneducated, uninformed guess is that using this to replace
JavaClient would be a lot of work. It might be interesting to try.
Call me an old-fogey that can't see what all these up-start kids are
making all the noise about.
WebObjects' Java Client already gives you a rich client with:
1) All Java - no need to learn another language (or three) for the
client
2) EOF (including EditingContext synchronization, RMI, etc) on the
client-side, no need to mash together different frameworks
3) WebStart makes distributing and launching a real app as easy as
opening a web page.
4) Direct To Java Client can give you a full UI without writing any
code.
It's here _today_ and is easy to integrate with an existing WO project.
I guess I just don't see what the big deal is. Sure, you can build web
pages that can work without the web. Do we need that? I'm not so sure.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
