Re: Docs
Re: Docs
- Subject: Re: Docs
- From: Jonathan Hendry <email@hidden>
- Date: Sat, 25 Aug 2001 00:46:25 -0500
On Saturday, August 25, 2001, at 12:17 , Mike Beam wrote:
Maybe I'm stepping into an argument that9s not mine, but when I heard
whoever say that WO would help one learn Cocoa, I took it to mean not that
it would help learn Objective-C/C or whatever from a language standpoint,
but rather WO would give another example of a well constructed OO
framework
from which one could learn principles of OO design.
Well, you would be using Foundation, which ought to be common
between Cocoa and WebObjects. You'd be using Cocoa's memory
management system, retain/release, autorelease pools, etc.
In a sense, Cocoa's AppKit and WebObjects' HTML classes are just two
different ways of providing a UI, which both sit on top of
Foundation.
So any Java code that you write at the Foundation level,
that isn't dependent on the upper layers of WebObjects,
ought to be reusable in Cocoa, either directly with
Cocoa/Java, with ObjC through the bridge, or after
converting to Objective-C.
So, for instance, a WebObjects app for searching a cocoa-dev
archive might have a Message model class. That class could _also_
be used in a Cocoa/Java client-side app for administering such
collections of mail messages. (Assuming the Message class isn't
dependant upon any of the WebObjects-specific frameworks). If
you've got a bunch of model classes like this, it would
be a big advantage.
Likewise, if you've got a bunch of handy Foundation-based code
in a Cocoa/Java app, you could use it in a WebObjects app.
I'm pretty sure you can't reuse PHP code as-is in a Cocoa
app, either ObjC or Java.
| References: | |
| | >Re: Docs (From: Mike Beam <email@hidden>) |