Re: Proposed solution for Obj-C/EOF.
Re: Proposed solution for Obj-C/EOF.
- Subject: Re: Proposed solution for Obj-C/EOF.
- From: Scott Anguish <email@hidden>
- Date: Sun, 17 Jun 2001 01:38:49 -0400
On Saturday, June 16, 2001, at 07:25 PM, Aaron Tuller wrote:
At 3:52 PM -0700 6/16/01, Deirdre Saoirse Moen wrote:
well, the Apple Store is a WebObjects/EOF app I assume and not a
Cocoa/EOF app (at least to the end user) and as I understand it, WO
4.5.1 lets you deploy and develop pure ObjC WO apps on OS X (and
server?). Please correct me if i'm wrong, I'd like to get it clear.
is the only thing broken about ObjC EOF support on OS X the palette?
As of 5.0 it's a lot more broken than that!
yes, but what about 4.5.1?
all i'm saying is that for people who want to deploy web based EOF apps
in ObjC, there is a currently shipping and supported product to let
them do that, WebObjects 4.5.1.
4.5.1 is about as supported as OSXS 1.2v3 has been.
WOF 4.5.1 does NOT allow you to write new EOF/Obj-C/Cocoa apps.
This was promised, touted as a supported feature. This is no longer the
case.
For some stupid reason, Apple links all of Carbon into all WOF
4.5.1 on OS X apps now, and we have dozens of conflicts with third party
libraries now that can't be resolved.
4.5.1 on OS X uses the obsoleted ProjectBuilder WO tool.
EOModeller is badly broken and crashes often, it also won't read
some EOmodels that are from 4.5.