Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa superiority?
Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa superiority?
- Subject: Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa superiority?
- From: "e.sammer" <email@hidden>
- Date: Tue, 12 Jun 2001 19:44:13 -0400
Bill Bumgarner wrote:
<snip>
However, that does not mean EOF is an appropriate solution for every app
out there. Specifically, for applications targeted at the consumer
market, it very likely is not appropriate to use EOF as a solution for
persistency. I.e. EOF is not a good replacement for the traditional
multi-document UI that a product like, say, OmniGraffle,
GraphicConverter, or Create. Nor it is appropriate to apps that are
seemingly database centric like, say, iTunes or the Finder.
I would agree with Bill that EOF is not for the average consumer desktop
app,
but my focus (and problem with the lack of objc updates to EOF) is for
other kinds
of apps that would benefit greatly from EOF.
As a DBA (Oracle, mostly), I've written a number of management apps for Unix
systems including report writing utilities, database "shells" like
sqlplus and svrmgrl,
and health monitoring tools to help me when working with Oracle. The
thing is, I
would have loved to make these availble for X natively using objc - that
won't
happen now. I understand why Apple might switch all support for EOF to
Java, due
to the buzz around it and the like, but what I don't understand is the
association
between EOF and WebObjects. With that said, I understand that most
"web-based"
(for lack of a better term) apps probably use it the most, but it is
certainly a via
product on its own. Then again, I'm not really a business person and
care very little
for things like the "bottom line" and such, but I know it's still
important for a company's
survival.
I suppose the best summary I could offer about the whole EOF war is...
"I'm glad it wasn't my decision to make."
--
e.sammer
email@hidden