Re: WebObjects application without a browser?
Re: WebObjects application without a browser?
- Subject: Re: WebObjects application without a browser?
- From: Alan Ward <email@hidden>
- Date: Tue, 9 Sep 2003 09:47:36 -0700
you also have the possibility of developing a cocoa app that
communicates with
your WebObjects apps via a protocol that you define (rather than HTML).
Think of
iTunes and the iTunes Music Store ;-)
Alan
On Tuesday, September 9, 2003, at 09:31 AM, David Thorp wrote:
Hi Chris,
Thanks for the detailed explanation.
OK, so sounds like it's very powerful for cross platform apps where
you're limited to swing/etc and no cocoa, but for Cocoa apps, there's
no official Cocoa support at this stage, have i understood you
correctly?
When is WE 5.2.2 coming? Do we know yet?
The main reason I'm asking is because I have need for a networked
database app, and I'm looking at Obj-C, Java and WebObjects, but the
client wants a native cocoa interface, and as few problems to solve as
possible throughout development. By the sounds of it, WebObjects is
very solid and powerful, compared to whatever else we might write with
Java or Obj-C, but it's not going to work with cocoa too easily (or
supported by Apple) at this stage. Have I understood you correctly?
What are my alternatives for this?
Thanks!
David.
On Wednesday, September 10, 2003, at 12:01 AM, Chris Pavicich wrote:
David:
WebObjects was ~primarily~ developed to build robust databse driven
web applications. However, the browser is not the
only way to deliver a UI (if there is a UI at all). WO is best
thought of using Model View Controller.
Enterprise Objects Framework (EOF) provides the database modeling and
persistence mechanism. (MODEL)
WebObjects Frameworks (WOF) provides the necessary tools for writing
the application and business logic. (Controller)
WOF also provides the mechanism for generating an HTML UI. (View)
Direct2Web provides a mechanism for rapidly generating rules based
HTML UIs. This can be quite cool once you get the hang of it.
Direct2JavaClient is like Direct2Web, but the UI is a java
application; which is extensible and you get all the Swing you want
to use.
WebServices exposes your model and functionality as SOAP calls.
(IMHO) This ~will~ be the most flexible way to write
WO apps once 5.2.2 is released. Anything that can parse and send SOAP
messages will be able to interact with your
application. (This would be one solution to providing a UI in Cocoa,
and leveraging WO, another way would be to just use EOF in your Cocoa
application, but I don't think that this is officially supported)
HTH.
Chris
Group: Please correct / revise / flame as necessary.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.