Re: [Wonder-disc] SproutCore and WO?
Re: [Wonder-disc] SproutCore and WO?
- Subject: Re: [Wonder-disc] SproutCore and WO?
- From: "John Huss" <email@hidden>
- Date: Mon, 16 Jun 2008 11:27:37 -0700
I think GWT is pretty compelling in similiar ways to SpoutCore. And with GWT you get to write in Java and you can generate classes for client-side EOs that make it fairly easy to exchange data (but without a client-side editing context of course). If I was writing a Web 2.0 app from scratch with WO, that's what I would do.
John
On Mon, Jun 16, 2008 at 8:20 AM, David Avendasora <
email@hidden> wrote:
On Jun 16, 2008, at 10:29 AM, James Cicenia wrote:
Ah! Back to the Future of Client Server.
Besides, with all the new client options, you still don't have EOF _on_ the client. You have to still translate EOs into client-side objects and manage Editing Contexts manually. With Java Client, you get real Java EOs on the client and automatic client-server syncing of ECs with no code at all!
With Flor's JBND framework on top of Java Client, you get truly powerful rich clients with full update notifications as you'd expect from a true desktop application.
With that said, right now there are so many options for where to take a WO project it is truly amazing:
1) Standard Website
2) Java Client
3) Web Service
4) Wonder AJAX Website
5) SproutCore AJAX Website
5) JSON-RPC for
a) Mac Cocoa
b) iPhone Cocoa
c) Other native clients?
And it is perfectly possible to provide all these clients simultaneously from one WebObjects server! How's that for a flexible platform?
And now we have a nightly WO build server! Not only is WO not dead, it is quickly knocking down many of the barriers to adoption that have plagued it in the past.
It's a great time to be WOveloper! (yeah, kinda corny)
Dave
On Jun 16, 2008, at 10:29 AM, James Cicenia wrote:
_______________________________________________
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